Apply suggestions from code review

Author: Oxyjun

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

@@ -14,10 +14,9 @@ Public buckets can be set up in either one of two ways:
 - Expose your bucket as a custom domain under your control.
 - Expose your bucket using a Cloudflare-managed `https://r2.dev` subdomain for non-production use cases.
 
-These options can be used independently or together, enabling custom domains does not require enabling `r2.dev` access.
+These options can be used independently. Enabling custom domains does not require enabling `r2.dev` access.
 
-To use features like WAF custom rules, caching, access controls, or bot management, you must configure your bucket behind a custom domain.
-These capabilities are not available when using the `r2.dev` development url.
+To use features like WAF custom rules, caching, access controls, or bot management, you must configure your bucket behind a custom domain. These capabilities are not available when using the `r2.dev` development url.
 
 :::note
 
@@ -36,6 +35,7 @@ Configure your cache to use [Smart Tiered Cache](/cache/how-to/tiered-cache/#sma
 :::note
 
 By default, only certain file types are cached. To cache all files in your bucket, you must set a Cache Everything page rule.
+
 For more information on default Cache behavior and how to customize it, refer to [Default Cache Behavior](/cache/concepts/default-cache-behavior/#default-cached-file-extensions)
 
 :::
@@ -62,7 +62,7 @@ To specify the minimum TLS version of a custom hostname of an R2 bucket, you can
 The domain being used must have been added as a [zone](/fundamentals/setup/accounts-and-zones/#zones) in the same account as the R2 bucket.
 
 - If your domain is already managed by Cloudflare, you can proceed to Connect a bucket to a custom domain.
-- If your domain is not managed by Cloudflare, you’ll need to set it up using a [partial (CNAME) setup](/dns/zone-setups/partial-setup/) to add it to your account.
+- If your domain is not managed by Cloudflare, you need to set it up using a [partial (CNAME) setup](/dns/zone-setups/partial-setup/) to add it to your account.
 
 Once the domain exists in your Cloudflare account (regardless of setup type), you can link it to your bucket.
 
@@ -75,6 +75,7 @@ To view the added DNS record, select **...** next to the connected domain and se
 :::note
 
 If the zone is on an Enterprise plan, make sure that you [release the zone hold](/fundamentals/setup/account/account-security/zone-holds/#release-zone-holds) before adding the custom domain.
+
 A zone hold would prevent the custom subdomain from activating.
 
 :::
@@ -93,29 +94,26 @@ To disable a domain:
 
 ## Remove domain
 
-Removing a custom domain will disconnect it from your bucket and delete its configuration from the dashboard.
-Your bucket will remain publicly accessible through any other enabled access method, but the domain will no longer appear in the connected domains list.
+Removing a custom domain will disconnect it from your bucket and delete its configuration from the dashboard. Your bucket will remain publicly accessible through any other enabled access method, but the domain will no longer appear in the connected domains list.
 
 To remove a domain:
 
 1. In **R2**, select the bucket you want to modify.
 2. On the bucket page, Select **Settings**, go to **Custom Domains**.
 3. Next to the domain you want to disable, select **...** and **Remove domain**.
-4. Select ‘Remove domain’ in the confirmation window. The CNAME record pointing to the domain will also be removed as part of this step. You can always add the domain again.
+4. Select ‘Remove domain’ in the confirmation window. This step also removes the CNAME record pointing to the domain. You can always add the domain again.
 
-## Public Development URL
+## Public development URL
 
-Expose the contents of this R2 bucket to the internet through a Cloudflare-managed r2.dev subdomain.
-This endpoint is intended for non-production traffic.
+Expose the contents of this R2 bucket to the internet through a Cloudflare-managed r2.dev subdomain. This endpoint is intended for non-production traffic.
 
 :::note
 
 Public access through `r2.dev` subdomains are rate limited and should only be used for development purposes.
 
 To enable access management, Cache and bot management features, you must set up a custom domain when enabling public access to your bucket.
 
-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.
+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.
 :::
 
 ### Enable public development url
@@ -134,9 +132,9 @@ To verify that your bucket is publicly accessible, check that **Public URL Acces
 
 ### Disable public development url
 
-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.
-If you’ve connected other domains, the bucket will remain accessible through those.
+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.
+
+If you have connected other domains, the bucket will remain accessible for those domains.
 
 To disable public access for your bucket: