diff --git a/collector/README.md b/collector/README.md
index 0d8d0dd01e..83c7598637 100644
--- a/collector/README.md
+++ b/collector/README.md
@@ -93,7 +93,7 @@ Loading configuration from S3 will require that the IAM role attached to your fu
 # Improving Lambda responses times
 At the end of a lambda function's execution, the OpenTelemetry client libraries will flush any pending spans/metrics/logs
 to the collector before returning control to the Lambda environment. The collector's pipelines are synchronous and this 
-means that the response of the lambda function is delayed until the data has been exported has been completed. 
+means that the response of the lambda function is delayed until the data has been exported. 
 This delay can potentially be for hundreds of milliseconds.
 
 To overcome this problem the [decouple](./processor/decoupleprocessor/README.md) processor can be used to separate the 
@@ -126,7 +126,7 @@ service:
 
 ## Reducing Lambda runtime
 If your lambda function is invoked frequently it is also possible to pair the decouple processor with the batch 
-processor to reduce total lambda execution time at the expense of the export of OpenTelemetry data being delayed. 
+processor to reduce total lambda execution time at the expense of the delaying the export of OpenTelemetry data. 
 When used with the batch processor the decouple processor must be the last processor in the pipeline to ensure that data
 is successfully exported before the lambda environment is frozen.