docs: update docs for sqs service

Author: Amir Blum

packages/plugin-aws-sdk/docs/sqs.md

@@ -5,17 +5,17 @@ SQS is amazon's managed message queue. Thus, it should follow the [Open Telemetr
 The following methods are automatically enhanced:
 
 ### sendMessage / sendMessageBatch
-- [Message Attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/semantic_conventions/messaging.md#messaging-attributes) are added by this plugin according to the spec.
-- TODO: Inject trace context as SQS MessageAttributes, so the service receiving the message can link cascading spans to the trace which created the message. 
+- [Messaging Attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/semantic_conventions/messaging.md#messaging-attributes) are added by this plugin according to the spec.
+- Open Telemetry trace context is injected as SQS MessageAttributes, so the service receiving the message can link cascading spans to the trace which created the message. 
 
 ### receiveMessage
-- [Message Attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/semantic_conventions/messaging.md#messaging-attributes) are added by this plugin according to the spec.
+- [Messaging Attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/semantic_conventions/messaging.md#messaging-attributes) are added by this plugin according to the spec.
 - Additional "processing spans" are created for each message received by the application.   
 If an application invoked `receiveMessage`, and received a 10 messages batch, a single `messaging.operation` = `receive` span will be created for the `receiveMessage` operation, and 10 `messaging.operation` = `process` spans will be created, one for each message.  
 Those processing spans are created by the library. This behavior is partially implemented, [See discussion below](#processing-spans).
 - Sets the inter process context correctly, so that additional spans created through the process will be linked to parent spans correctly.  
 This behavior is partially implemented, [See discussion below](#processing-spans).
-- TODO: Extract trace context from SQS MessageAttributes, and set span's `parent` and `links` correctly according to the spec.
+- Extract trace context from SQS MessageAttributes, and set span's `parent` and `links` correctly according to the spec.
 
 #### Processing Spans
 According to open telemetry specification (and to reasonable expectation for trace structure), user of this library would expect to see one span for the operation of receiving messages batch from SQS, and then, for each message, a span with it's own sub-tree for the processing of this specific message.