Fixed broken links

Author: maheshwarip

src/content/docs/pipelines/build-with-pipelines/output-settings.mdx

@@ -34,7 +34,7 @@ By default, output files are compressed in the `gzip` format. Compression can be
 npx wrangler pipelines update [PIPELINE-NAME] --compression none
 ```
 
-Output files are named using a [UILD](/https://github.com/ulid/spec) slug, followed by an extension.
+Output files are named using a [UILD](https://github.com/ulid/spec) slug, followed by an extension.
 
 ## Customize batch behavior
 When configuring your pipeline, you can define how records are batched before they are delivered to R2. Batches of records are written out to a single output file.

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

@@ -23,9 +23,9 @@ We plan to support more sources, data formats, and sinks, in the future.
 ## Data durability, and the lifecycle of a request
 If you make a request to send data to a pipeline, and receive a successful response, we guarantee that the data will be delivered to your configured destination.
 
-Data sent to a pipeline is durably committed to storage. Pipelines use [SQLite backed Durable Objects](durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend) as a buffer for ingested records. A pipeline will only return a response after data has been successfully stored.
+Any data sent to a pipeline is durably committed to storage. Pipelines use [SQLite backed Durable Objects](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend) as a buffer for ingested records. A pipeline will only return a response after data has been successfully stored.
 
-Ingested data continues to be stored, until a sufficiently large batch of data has accumulated. Batching is useful to reduce the number of output files written out to R2. [Batch sizes are customizable](/pipelines/build-with-pipelines/output-settings/#customize-batch-behavior), in terms of data volume, rows, or time. 
+Ingested data continues to be stored, until a sufficiently large batch of data has accumulated. Batching is useful to reduce the number of output files written out to R2. [Batch sizes are customizable](/pipelines/build-with-pipelines/output-settings/#customize-batch-behavior), in terms of data volume, rows, or time.
 
 When a batch has reached its target size, the batch entire is written out to a file. The file is optionally compressed, and is delivered to an R2 bucket. Any transient failures, such as network failures, are automatically retried.
 

src/content/docs/pipelines/index.mdx

@@ -40,7 +40,7 @@ You can now send data to your pipeline with:
 Refer to the [getting started guide](/pipelines/getting-started) to start building with pipelines.
 
 :::note
-While in beta, you will not be billed for Pipelines usage. You will be billed only for [R2 operations](r2/pricing/).
+While in beta, you will not be billed for Pipelines usage. You will be billed only for [R2 operations](/r2/pricing/).
 :::
 
 ***