Skip to content

Commit 718b3bf

Browse files
Update public-buckets.mdx (#30712)
* Update public-buckets.mdx * trigger ci and codeowner re-evaluation --------- Co-authored-by: helloimalastair <helloimalastair@users.noreply.github.com>
1 parent 0eea70e commit 718b3bf

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

src/content/docs/r2/buckets/public-buckets.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ import { Render } from "~/components";
1212

1313
Public Bucket is a feature that allows users to expose the contents of their R2 buckets directly to the Internet. By default, buckets are never publicly accessible and will always require explicit user permission to enable.
1414

15-
Public buckets can be set up in either one of two ways:
15+
Public buckets can be set up in either of two ways:
1616

1717
- Expose your bucket as a custom domain under your control.
1818
- Expose your bucket using a Cloudflare-managed `https://r2.dev` subdomain for non-production use cases.
@@ -33,7 +33,7 @@ Currently, public buckets do not let you list the bucket contents at the root of
3333

3434
Domain access through a custom domain allows you to use [Cloudflare Cache](/cache/) to accelerate access to your R2 bucket.
3535

36-
Configure your cache to use [Smart Tiered Cache](/cache/how-to/tiered-cache/#smart-tiered-cache) to have a single upper tier data center next to your R2 bucket.
36+
Configure your cache to use [Smart Tiered Cache](/cache/how-to/tiered-cache/#smart-tiered-cache) to have a single upper-tier data center next to your R2 bucket.
3737

3838
:::note
3939

@@ -112,14 +112,14 @@ Expose the contents of this R2 bucket to the internet through a Cloudflare-manag
112112

113113
:::note
114114

115-
Public access through `r2.dev` subdomains are rate limited and should only be used for development purposes.
115+
Public access through `r2.dev` subdomains is rate-limited and should only be used for development purposes.
116116

117-
To enable access management, Cache and bot management features, you must set up a custom domain when enabling public access to your bucket.
117+
To enable access management, cache, and bot management features, you must set up a custom domain when enabling public access to your bucket.
118118

119119
Avoid creating a CNAME record pointing to the `r2.dev` subdomain. This is an **unsupported access path**, and we cannot guarantee consistent reliability or performance. For production use, [add your domain to Cloudflare](#add-your-domain-to-cloudflare) instead.
120120
:::
121121

122-
### Enable public development url
122+
### Enable public development URL
123123

124124
When you enable public development URL access for your bucket, its contents become available on the internet through a Cloudflare-managed `r2.dev` subdomain.
125125

@@ -133,7 +133,7 @@ To enable access through `r2.dev` for your buckets:
133133

134134
To verify that your bucket is publicly accessible, check that **Public URL Access** shows **Allowed** in you bucket settings.
135135

136-
### Disable public development url
136+
### Disable public development URL
137137

138138
Disabling public development URL access removes your bucket's exposure through the `r2.dev` subdomain. The bucket and its objects will no longer be accessible via the Public Bucket URL.
139139

0 commit comments

Comments
 (0)