Skip to content

Commit f257f1e

Browse files
committed
Fixed typos
1 parent a203abc commit f257f1e

File tree

3 files changed

+7
-16
lines changed

3 files changed

+7
-16
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
pcx_content_type: concept
3-
title: How Pipelines Work
3+
title: How pipelines Work
44
sidebar:
55
order: 1
66
---
@@ -16,9 +16,9 @@ This guide explains how a pipeline works.
1616
### Sources
1717
Pipelines supports the following sources:
1818
* [HTTP Clients](/pipelines/build-with-pipelines/http), with optional authentication and CORS settings
19-
* [Cloudflare Worker](/workers/), using the [Pipelines Workers API](/pipelines/build-with-pipelines/workers-apis)
19+
* [Cloudflare Workers](/workers/), using the [Pipelines Workers API](/pipelines/build-with-pipelines/workers-apis)
2020

21-
Multiple sources can be active on a single pipeline simultaneously. For example, you can create a pipeline which accepts data from both a Worker, and via HTTP. Multiple workers can be configured to send data to the same pipeline. There is no limit to the number of source clients.
21+
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. Multiple workers can be configured to send data to the same pipeline. There is no limit to the number of source clients.
2222

2323
### Data format
2424
Pipelines can ingest JSON serializable records.
@@ -27,7 +27,7 @@ Pipelines can ingest JSON serializable records.
2727
Pipelines supports delivering data into [R2 Object Storage](/r2/). Ingested data is delivered as newline delimited JSON files (`ndjson`), with optional compression. Multiple pipelines can be configured to deliver data to the same R2 bucket.
2828

2929
## Data durability
30-
Pipelines are designed to be reliable. Data sent to a pipeline should be delivered successfully to the configured R2 bucket, provided that the [R2 API credentials associated with a pipeline](/r2/api/tokens/) remain valid.
30+
Pipelines are designed to be reliable. Any data which is successfully ingested will be delivered to the configured R2 bucket, provided that the [R2 API credentials associated with a pipeline](/r2/api/tokens/) remain valid.
3131

3232
Each pipeline maintains a storage buffer. Requests to send data to a pipeline receive a successful response only after the data is committed to this storage buffer.
3333

src/content/docs/pipelines/platform/limits.mdx

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,6 @@ sidebar:
77

88
import { Render } from "~/components"
99

10-
:::note
11-
12-
Many of these limits will increase during Pipelines' public beta period.
13-
14-
:::
1510

1611
| Feature | Limit |
1712
| --------------------------------------------- | ------------------------------------------------------------- |

src/content/docs/pipelines/platform/pricing.mdx

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,18 +10,14 @@ head:
1010
---
1111

1212
:::note
13-
While in beta, Pipelines will not charge for usage. However, you will be billed for [R2 operations](/r2/pricing).
14-
:::
15-
1613
Pipelines requires a [Workers paid](/workers/platform/pricing/#workers) plan to use.
14+
:::
1715

18-
## Future pricing
19-
During the first phase of the Pipelines open beta, there will be no charges beyond R2 operations for storage, and loading files.
16+
During the first phase of the Pipelines open beta, you will not be billed for pipelines usage. You will be billed only for [R2 usage](/r2/pricing).
2017

21-
In the future, we will introduce pricing based on the volume of data ingested into Pipelines, and delivered from Pipelines. We will provide at least 30 days notice before charging for usage. We expect to begin chargning for usage by September 15, 2025.
18+
In the future, we will introduce pricing based on the volume of data ingested into Pipelines, and delivered from Pipelines. We will provide at least 30 days notice before charging for usage. We expect to begin charging for usage by September 15, 2025.
2219

2320
| | Workers Paid Users
2421
| ---------------------------------- | ------------------------
2522
| Ingestion | 50 GB / month included + $0.02 / additional GB
2623
| Delivery to R2 | 50 GB / month included + $0.02 / additional GB
27-

0 commit comments

Comments
 (0)