Improved getting started guide

Author: maheshwarip

src/content/docs/pipelines/getting-started.mdx

@@ -10,13 +10,13 @@ head:
 
 import { Render, PackageManagers } from "~/components";
 
-Cloudflare Pipelines allows you to ingest and load high volumes of real time streaming data into [R2 Object Storage](/r2/), without managing any infrastructure. This guide will show you how to setup a Pipeline which accepts data via HTTP.
+Cloudflare Pipelines allows you to ingest and load high volumes of real time streaming data into [R2 Object Storage](/r2/), without managing any infrastructure.
 
 By following this guide, you will:
-1. Create your first Pipeline.
-2. Connect it to your R2 bucket.
-3. Post data to it via HTTP.
-4. Verify the output file written to R2.
+1. Setup an R2 bucket
+2. Create a pipeline, with HTTP as a source, and an R2 bucket as a sink
+3. Send data to your pipeline's HTTP ingestion endpoint
+4. Verify the output delivered to R2
 
 :::note
 
@@ -34,50 +34,50 @@ To use Pipelines, you will need:
 
 ## 1. Set up an R2 bucket
 
-Pipelines let you ingest records in real time, and load them into an R2 bucket. Create a bucket by following the [get started guide for R2](/r2/get-started/), or by running the command below:
+Create a bucket by following the [get started guide for R2](/r2/get-started/), or by running the command below:
 
 ```sh
-npx wrangler r2 bucket create [R2-BUCKET-NAME]
+npx wrangler r2 bucket create clickstream-bucket
 ```
 
 Save the bucket name for the next step.
 
 ## 2. Create a Pipeline
 
-To create a Pipeline using Wrangler, run the following command in a terminal, and specify:
+To create a pipeline using Wrangler, run the following command in a terminal, and specify:
 
-- The name of your Pipeline
+- The name of your pipeline
 - The name of the R2 bucket you created in step 1
 
 ```sh
-npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME] --batch-max-seconds 5 --compression none
+npx wrangler pipelines create clickstream-pipeline --r2-bucket clickstream-bucket --batch-max-seconds 5 --compression none
 ```
 
-After running this command, you'll be prompted to authorize Cloudflare Workers Pipelines to create R2 API tokens on your behalf. These tokens are required by your Pipeline. Your Pipeline uses the tokens when loading data into your bucket. You can approve the request through the browser link which will open automatically.
+After running this command, you'll be prompted to authorize Cloudflare Workers Pipelines to create an R2 API token on your behalf. These tokens used by your pipeline when loading data into your bucket. You can approve the request through the browser link which will open automatically.
 
-If you prefer not to authenticate this way, you may pass your [R2 API Tokens](/r2/api/s3/tokens/) to Wrangler:
+If you prefer not to authenticate this way, you may pass your [R2 API Token](/r2/api/s3/tokens/) to Wrangler:
 ```sh
-npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME] --r2-access-key-id [ACCESS-KEY-ID] --r2-secret-access-key [SECRET-ACCESS-KEY]
+npx wrangler pipelines create clickstream-pipeline --r2-bucket clickstream-bucket --r2-access-key-id [ACCESS-KEY-ID] --r2-secret-access-key [SECRET-ACCESS-KEY] --batch-max-seconds 5 --compression none
 ```
 
-When choosing a name for your Pipeline:
+When choosing a name for your pipeline:
 
-1. Ensure it is descriptive and relevant to the type of events you intend to ingest. You cannot change the name of the Pipeline after creating it.
+1. Ensure it is descriptive and relevant to the type of events you intend to ingest. You cannot change the name of the pipeline after creating it.
 2. Pipeline names must be between 1 and 63 characters long.
 3. The name cannot contain special characters outside dashes (`-`).
 4. The name must start and end with a letter or a number.
 
-You'll notice that we have set two optional flags while creating the pipeline: `--batch-max-seconds` and `--compression`. We've added these flags to make it faster for you to see the output of your first Pipeline. For production use cases, we recommend keeping the default settings.
+You'll notice that we have set two optional flags while creating the pipeline: `--batch-max-seconds` and `--compression`. We've added these flags to make it faster for you to see the output of your first pipeline. For production use cases, we recommend keeping the default settings.
 
-Once you create your Pipeline, you will receive a HTTP endpoint which you can post data to. You should see output as shown below:
+Once you create your pipeline, you will receive a HTTP endpoint which you can post data to. You should see output as shown below:
 
 ```sh
-🌀 Authorizing R2 bucket "[R2-BUCKET-NAME]"
-🌀 Creating pipeline named "[PIPELINE-NAME]"
-✅ Successfully created pipeline [PIPELINE-NAME] with ID [PIPELINE-ID]
+🌀 Authorizing R2 bucket "clickstream-bucket"
+🌀 Creating pipeline named "clickstream-pipeline"
+✅ Successfully created pipeline clickstream-pipeline with ID 91f312b8ca484e5db404bd3e3ef256fn
 
 You can now send data to your pipeline with:
-  curl "https://<PIPELINE-ID>.pipelines.cloudflare.com/" -d '[{ "foo":"bar }]'
+curl "https://91f312b8ca484e5db404bd3e3ef256fn.pipelines.cloudflare.com/" -d '[{ "foo":"bar }]'
 ```
 
 ## 3. Post data to your pipeline
@@ -86,11 +86,11 @@ Use a curl command in your terminal to post an array of JSON objects to the endp
 
 ```sh
 curl -H "Content-Type:application/json" \
-    -d '[{"account_id":"test", "other_data": "test"},{"account_id":"test","other_data": "test2"}]' \
+    -d '[{"event":"viewedCart", "timestamp": "2025-04-03T15:42:30Z"},{"event":"cartAbandoned", "timestamp": "2025-04-03T15:42:37Z"}]' \
     <HTTP-endpoint>
 ```
 
-Once the Pipeline successfully accepts the data, you will receive a success message.
+Once the pipeline successfully accepts the data, you will receive a success message.
 
 Pipelines handle batching the data, so you can continue posting data to the Pipeline. Once a batch is filled up, the data will be partitioned by date, and written to your R2 bucket.