Update how-pipelines-work.mdx

Author: maheshwarip

src/content/docs/pipelines/concepts/how-pipelines-work.mdx

@@ -16,7 +16,7 @@ Pipelines supports ingestion via [HTTP](/pipelines/build-with-pipelines/http), o
 
 A pipeline can ingest JSON-serializable records.
 
-Finally, Pipelines supports writing data to [R2 Object Storage](/r2/). Ingested data is written to output files, compressed, and delivered to an R2 bucket. Output files are generated as newline delimited JSON files (`ndjson`). The filename of each output file is prefixed by the event date and time, to make querying the data more efficient. For example, an output fle might be named like this: `event_date=2025-04-03/hr=15/01JQY361X75TMYSQZGWC6ZDMR2.json.gz`. Each line in an output file maps to a single record ingested by a pipeline.
+Finally, Pipelines supports writing data to [R2 Object Storage](/r2/). Ingested data is written to output files. These files are optionally compressed, and then delivered to an R2 bucket. Output files are generated as newline delimited JSON files (`ndjson`). The filename of each output file is prefixed by the event date and time, to make querying the data more efficient. For example, an output fle might be named like this: `event_date=2025-04-03/hr=15/01JQY361X75TMYSQZGWC6ZDMR2.json.gz`. Each line in an output file maps to a single record ingested by a pipeline.
 
 We plan to support more sources, data formats, and sinks, in the future.
 
@@ -33,4 +33,4 @@ Finally, when a batch has reached its target size, it is written out to a file.
 Data delivery is guaranteed even while updating an existing pipeline. Updating an existing pipeline effectively creates a new deployment, including all your previously configured options. Requests are gracefully re-routed to the new pipeline. The old pipeline continues to write data into your destination. Once the old pipeline is fully drained, it is spun down.
 
 ## What if I send too much data? Do Pipelines communicate backpressure?
-If you send too much data, the pipeline will communicate backpressure by returning a 429 response to HTTP requests, or throwing an error if using the Workers API. Refer to the [limits](/pipelines/platform/limits) to learn how much volume a single pipeline can support.
+If you send too much data, the pipeline will communicate backpressure by returning a 429 response to HTTP requests, or throwing an error if using the Workers API. Refer to the [limits](/pipelines/platform/limits) to learn how much volume a single pipeline can support.