diff --git a/docs/monitoring.md b/docs/monitoring.md
index 90be9ba51b4..3b73d8f85b1 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -36,7 +36,7 @@ be used in any production deployment.
 
 The `otelcol_exporter_queue_capacity` indicates the capacity of the retry queue (in batches). The `otelcol_exporter_queue_size` indicates the current size of retry queue. So you can use these two metrics to check if the queue capacity is enough for your workload. 
 
-The `otelcol_exporter_enqueue_failed_spans`, `otelcol_exporter_enqueue_failed_metric_points` and `otelcol_exporter_enqueue_failed_log_records` indicate the number of span/metric points/log records failed to be added to the sending queue. This maybe cause by the queue is full of unsettled elements so you should decrease your sending rate or horizontally scale your collector.
+The `otelcol_exporter_enqueue_failed_spans`, `otelcol_exporter_enqueue_failed_metric_points` and `otelcol_exporter_enqueue_failed_log_records` indicate the number of span/metric points/log records failed to be added to the sending queue. This may be cause by a queue full of unsettled elements, so you may need to decrease your sending rate or horizontally scale collectors.
 
 The queue/retry mechanism also supports logging for monitoring. Check
 the logs for messages like `"Dropping data because sending_queue is full"`.