Instrumenting AWS Lambda: Span name inconsistency

[zsrv]

The AWS Lambda semantic conventions page for SQS events here states the following:

For the SQS event span, if all the messages in the event have the same event source, the name of the span MUST be <event source> process. If there are multiple sources in the batch, the name MUST be multiple_sources process.

The same page states the following for SQS messages:

For the SQS message span, the name MUST be <event source> process.

These span names are inconsistent with the messaging span name guidelines here...

The span name SHOULD be {messaging.operation.name} {destination}

...and the examples at the bottom of the same page.