improved language

Author: maheshwarip

src/content/docs/pipelines/build-with-pipelines/sources/http.mdx

@@ -44,18 +44,6 @@ Send data to your pipeline's HTTP endpoint:
 curl "https://0e00c5ff09b34d018152af98d06f5a1xvc.pipelines.cloudflare.com/" -d '[{ ...JSON_DATA... }]'
 ```
 
-## Accepted data formats
-Pipelines accept arrays of valid JSON objects. You can send multiple objects in a single request, provided the total data volume is within the [documented limits](/pipelines/platform/limits). Sending data in a different format will result in an error.
-
-For example, you can send data to your pipeline using a curl command like this:
-```sh
-curl -X POST https://<PIPELINE-ID>.pipelines.cloudflare.com \
-  -H "Content-Type: application/json" \
-  -d '[{"foo":"bar"}, {"foo":"bar"}, {"foo":"bar"}]'
-
-{"success":true,"result":{"committed":3}}
-```
-
 ## Authentication
 You can secure your HTTP ingestion endpoint using Cloudflare API tokens. By default, authentication is turned off. To configure authentication, use the `--require-http-auth` flag while creating or updating a pipeline.
 

src/content/docs/pipelines/build-with-pipelines/sources/index.mdx

@@ -7,11 +7,13 @@ sidebar:
     hideIndex: false
 ---
 
-Pipelines supports the following sources:
+Pipelines let you ingest data from the following sources:
 * [HTTP Clients](/pipelines/build-with-pipelines/sources/http), with optional authentication and CORS settings
 * [Cloudflare Workers](/workers/), using the [Pipelines Workers API](/pipelines/build-with-pipelines/sources/workers-apis)
 
-Multiple sources can be active on a single pipeline simultaneously. For example, you can create a pipeline which accepts data from Workers and via HTTP. There is no limit to the number of source clients. Multiple workers can be configured to send data to the same pipeline.
+Multiple sources can be active on a single pipeline simultaneously. For example, you can create a pipeline which accepts data from Workers and via HTTP. There is no limit to the number of source clients. Multiple Workers can be configured to send data to the same pipeline.
+
+Each pipeline can ingest up to 100 MB/s of data, or accept up to 100,000 requests per second, across all sources.
 
 ## Configuring allowed sources
 By default, ingestion via HTTP and from Workers is turned on. You can configure the allowed sources by using the `--source` flag while creating or updating a pipeline.
@@ -21,6 +23,5 @@ For example, to create a pipeline which only accepts data via a Worker, you can
 $ npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME] --source worker
 ```
 
-:::note
-HTTP ingestion URLs are tied to your pipeline ID. Turning HTTP off, and then turning it back on, will not change the URL.
-:::
+## Accepted data formats
+Pipelines accept arrays of valid JSON objects. You can send multiple objects in a single request, provided the total data volume is within the [documented limits](/pipelines/platform/limits). Sending data in a different format will result in an error.

src/content/docs/pipelines/build-with-pipelines/sources/workers-apis.mdx

@@ -11,7 +11,7 @@ head:
 
 import { Render, PackageManagers, WranglerConfig } from "~/components";
 
-Pipelines exposes an API directly to your [Workers](/workers) scripts via the [bindings](/workers/runtime-apis/bindings/#what-is-a-binding) concept. Bindings allow you to securely send data to a Pipeline without having to manage API keys or clients. Sending data via a Worker is enabled by default.
+Pipelines exposes an API directly to your [Workers](/workers) scripts via the [bindings](/workers/runtime-apis/bindings/#what-is-a-binding) concept. Bindings allow you to securely send data to a pipeline without having to manage API keys or clients. Sending data via a Worker is enabled by default.
 
 ## Send data from a Worker
 ### Setup a binding
@@ -27,15 +27,15 @@ compatibility_date = "2025-04-01"
 
 [[pipelines]]
 pipeline = "<MY-PIPELINE-NAME>" # The name of your Pipeline
-binding = "MY_PIPELINE" # The binding name, accessed using env.MY_PIPELINE
+binding = "PIPELINE" # The binding name, accessed using env.MY_PIPELINE
 ```
 
 </WranglerConfig>
 
 You can bind multiple pipelines to a Worker.
 
 ### Send data
-The pipelines binding exposes a `send()` method. For example, to log inbound HTTP requests to your Worker:
+The Pipelines binding exposes a `send()` method. For example, to log inbound HTTP requests to your Worker:
 
 ```ts
 export default {
@@ -51,12 +51,9 @@ export default {
 } satisfies ExportedHandler<Env>;
 ```
 
-## Accepted data formats
-Pipelines accept arrays of valid JSON objects. You can send multiple objects in a single request, provided the total data volume is within the [documented limits](/pipelines/platform/limits). Sending data in a different format will result in an error.
-
 ## Workers API
 ### `Pipeline`
-A binding which allows a Worker to send messages to a Pipeline.
+A binding which allows a Worker to send messages to a pipeline.
 
 ```ts
 interface Pipeline<PipelineRecord> {
@@ -66,9 +63,9 @@ interface Pipeline<PipelineRecord> {
 
 * `send(records)`: `Promise<void>`
 
-  * Sends a record to the Pipeline. The body must be an array of objects which are JSON serializable.
-  * When the promise resolves, the message is confirmed to be stored by the pipeline.
+  * Sends records to the pipeline. The body must be an array of objects which are JSON serializable.
+  * When the promise resolves, the records are confirmed to be ingested.
 
 :::note
-When running your Worker locally, Pipelines are partially simulated. Worker code which sends data to a pipeline will execute successfully. However, the full pipeline, including batching & writing to R2, will not be executed locally.
+When running your Worker locally, pipelines are partially simulated. Worker code which sends data to a pipeline will execute successfully. However, the full pipeline, including batching & writing to R2, will not be executed locally.
 :::