cleanup

open-telemetry · Oct 22, 2024 · 75116ec · 75116ec
1 parent 81f93c1
commit 75116ec
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/faas/aws-lambda.md b/docs/faas/aws-lambda.md
@@ -159,7 +159,7 @@ The span kind for both types of SQS spans SHOULD be `CONSUMER`.
 
 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 parent MUST be the `SERVER` span corresponding to the function invocation.
+`multiple_sources process`. The parent SHOULD be the `SERVER` span corresponding to the function invocation.
 
 For every message in the event, the [message system attributes][] (not message attributes, which are provided by
 the user) SHOULD be checked for the key `AWSTraceHeader`. If it is present, an OpenTelemetry `Context` SHOULD be

diff --git a/docs/rpc/rpc-spans.md b/docs/rpc/rpc-spans.md
@@ -55,7 +55,7 @@ This document defines how to describe remote procedure calls
 
 A remote procedure calls is described by two separate spans, one on the client-side and one on the server-side.
 
-For outgoing requests, the `SpanKind` SHOULD be set to `CLIENT` and for incoming requests to `SERVER`.
+For outgoing requests, the `SpanKind` MUST be set to `CLIENT` and for incoming requests to `SERVER`.
 
 Remote procedure calls can only be represented with these semantic conventions, when the names of the called service and method are known and available.