Improve clarity and consistency in documentation

src/content/docs/browser-rendering/rest-api/json-endpoint.mdx

@@ -91,7 +91,7 @@ curl --request POST 'https://api.cloudflare.com/client/v4/accounts/CF_ACCOUNT_ID
 ### With only a prompt
 
 In this example, only a prompt is provided. The endpoint will use the prompt to extract the data, but the response will not be structured according to a JSON schema.
-This is useful for simple extractions where you don't need a specific format.
+This is useful for simple extractions where you do not need a specific format.
 
 ```bash
 curl --request POST 'https://api.cloudflare.com/client/v4/accounts/CF_ACCOUNT_ID/browser-rendering/json' \

src/content/docs/browser-rendering/workers-binding-api/reuse-sessions.mdx

@@ -136,7 +136,7 @@ export default {
 };
 ```
 
-Besides `puppeteer.sessions()`, we've added other methods to facilitate [Session Management](/browser-rendering/platform/puppeteer/#session-management).
+Besides `puppeteer.sessions()`, we have added other methods to facilitate [Session Management](/browser-rendering/platform/puppeteer/#session-management).
 
 ## 5. Test
 

src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/static-assets.mdx

@@ -60,7 +60,7 @@ Before sending any file data, you need to tell Cloudflare which files you intend
 <Aside type="note" title="Asset Isolation Considerations">
 Static assets uploaded to Workers for Platforms are associated with the namespace rather than with individual User Worker. If multiple User Workers exist under the same namespace, assets with identical hashes may be shared across them. **JWTs should therefore only be shared with trusted platform services and should never be distributed to end-users.**
 
-If strict isolation of assets is required, we recommend either salting with a random value each time, or incorporating an end-user identifier (e.g. account ID or Worker script ID) within the hashing process, to ensure uniqueness. For example, `hash = slice(sha256(accountID + fileContents), 32)`.
+If strict isolation of assets is required, we recommend either salting with a random value each time, or incorporating an end-user identifier (for example, account ID or Worker script ID) within the hashing process, to ensure uniqueness. For example, `hash = slice(sha256(accountID + fileContents), 32)`.
 
 </Aside>
 
@@ -122,7 +122,7 @@ You can compute a SHA-256 digest of the file contents, then truncate or otherwis
 If all the files are already stored on Cloudflare, the response will only return the JWT token. If new or updated files are needed, the response will return:
 
 - `jwt`: An upload token (valid for 1 hour) which will be used in the API request to upload the file contents (Step 2).
-- `buckets`: An array of file-hash groups indicating which files to upload together. Files that have been recently uploaded won't appear in buckets, since Cloudflare already has them.
+- `buckets`: An array of file-hash groups indicating which files to upload together. Files that have been recently uploaded will not appear in buckets, since Cloudflare already has them.
 
 :::note
 This step alone does not store files on Cloudflare. You must upload the actual file data in the next step.
@@ -132,7 +132,7 @@ This step alone does not store files on Cloudflare. You must upload the actual f
 
 If the response to the Upload Session API returns `buckets`, that means you have new or changed files that need to be uploaded to Cloudflare.
 
-Use the [Workers Assets Upload API](https://developers.cloudflare.com/api/resources/workers/subresources/assets/subresources/upload/) to transmit the raw file bytes in base64-encoded format for any missing or changed files. Once uploaded, Cloudflare will store these files so they can then be attached to a User Worker.
+Use the [Workers Assets Upload API](/api/resources/workers/subresources/assets/subresources/upload/) to transmit the raw file bytes in base64-encoded format for any missing or changed files. Once uploaded, Cloudflare will store these files so they can then be attached to a User Worker.
 
 <Aside type="caution">
 	Asset uniqueness is determined by the provided hash and are associated globally to their namespace rather than with each specific User Worker. If an asset has already been uploaded for that namespace earlier, Cloudflare will automatically omit sending this asset hash back in the `buckets` response to save you from re-uploading the same thing twice. This means that an asset can be shared between multiple User Workers if it shares the same hash unless you **explicitly make the hash unique**. If you require full isolation between assets across User Workers, incorporate a unique identifier within your asset hashing process (either salting it with something entirely random each time, or by including the end-user account ID or their Worker name to retain per-customer re-use).
@@ -203,7 +203,7 @@ Once every file in the manifest has been uploaded, a status code of `201` will b
 
 ### 3. Deploy the User Worker with static assets
 
-Now that Cloudflare has all the files it needs (from the previous upload steps), you must attach them to the User Worker by making a PUT request to the [Upload User Worker API](https://developers.cloudflare.com/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/methods/update/). This final step links the static assets to the User Worker using the completion token you received after uploading file contents.
+Now that Cloudflare has all the files it needs (from the previous upload steps), you must attach them to the User Worker by making a PUT request to the [Upload User Worker API](/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/methods/update/). This final step links the static assets to the User Worker using the completion token you received after uploading file contents.
 
 You can also specify any optional settings under the `assets.config` field to customize how your files are served (for example, to handle trailing slashes in HTML paths).
 

src/content/docs/cloudflare-for-platforms/workers-for-platforms/platform/limits.mdx

@@ -14,7 +14,7 @@ Cloudflare provides an unlimited number of scripts for Workers for Platforms cus
 
 ## `cf` object
 
-The [`cf` object](/workers/runtime-apis/request/#the-cf-property-requestinitcfproperties) contains Cloudflare-specific properties of a request. This field is not accessible in [user Workers](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#user-workers) because some fields in this object are sensitive and can be used to manipulate Cloudflare features (eg.`cacheKey`, `resolveOverride`, `scrapeShield`.)
+The [`cf` object](/workers/runtime-apis/request/#the-cf-property-requestinitcfproperties) contains Cloudflare-specific properties of a request. This field is not accessible in [user Workers](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#user-workers) because some fields in this object are sensitive and can be used to manipulate Cloudflare features (for example, `cacheKey`, `resolveOverride`, `scrapeShield`.)
 
 ## Durable Object namespace limits
 

src/content/docs/cloudflare-one/applications/casb/casb-integrations/aws-s3.mdx

@@ -116,7 +116,7 @@ Identify AWS IAM-related security issues that could affect S3 Bucket and Object
 | Finding type                                                    | FindingTypeID                          | Severity |
 | --------------------------------------------------------------- | -------------------------------------- | -------- |
 | IAM Account Password Policy Does Not Exist                      | `e39ee4da-eed5-49d0-95f7-b423884b858c` | Critical |
-| IAM Account Password Policy Doesn't Require Lowercase Letters   | `9278444b-0c38-4ed0-8127-f3f25444811c` | High     |
+| IAM Account Password Policy Does Not Require Lowercase Letters   | `9278444b-0c38-4ed0-8127-f3f25444811c` | High     |
 | IAM Account Password Policy Doesn't Require Passwords to Expire | `5be79a96-4570-45cf-8ba3-1abe62802d16` | High     |
 | IAM Account Password Policy Doesn't Require Symbols             | `dd17afa3-4d4c-49e4-84c3-e829af9fff97` | High     |
 | IAM Account Password Policy Doesn't Require Uppercase Letters   | `e4976e53-bab5-4276-a1d3-1d85ebfd4d57` | High     |

src/content/docs/cloudflare-one/applications/casb/casb-integrations/bitbucket-cloud.mdx

@@ -8,7 +8,7 @@ import { Render } from "~/components";
 
 <Render
   file="casb/integration-description"
-  params={{ integrationName: "Bitbucket Cloud", integrationAccountType: "Bitbucket Cloud Cloud account" }}
+  params={{ integrationName: "Bitbucket", integrationAccountType: "Bitbucket Cloud account" }}
 />
 
 :::note

src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/docusign-access.mdx

@@ -25,7 +25,7 @@ This guide covers how to configure [Docusign](https://support.docusign.com/s/doc
 4. Use the following configuration:
 
    - Set the **Application** to _DocuSign_.
-   - Put placeholder values in **EntityID** and **Assertion Consumer Service URL** (e.g. `https://example.com`). We'll come back and update these.
+   - Put placeholder values in **EntityID** and **Assertion Consumer Service URL** (for example, `https://example.com`). We'll come back and update these.
    - Set **Name ID Format** to: _Unique ID_.
 
 5. DocuSign requires SAML attributes to do Just In Time user provisioning. Ensure you are collecting SAML attributes from your IdP:

src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/sparkpost-saas.mdx

@@ -44,7 +44,7 @@ This guide covers how to configure [SparkPost or SparkPost EU](https://support.s
 
 1. In SparkPost, select your profile picture > **Account Settings**.
 2. Under **Single Sign-On**, select **Provision SSO**.
-3. Under **Upload your Security Assertion Markup Language (SAML)**, select **select a file** and upload the `.xml` file you created in step [2. Download the metadata file](#2-download-the-metadata-file).
+3. Under **Upload your Security Assertion Markup Language (SAML)**, select **a file** and upload the `.xml` file you created in step [2. Download the metadata file](#2-download-the-metadata-file).
 4. Select **Provision SSO**.
 5. Select **Enable SSO**.
 

src/content/docs/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 6
 ---
 
-[Kubernetes](https://kubernetes.io/) is a container orchestration and management tool. Kubernetes is declarative, so you define the end state in a .yml file. A Kubernetes cluster has two components, the master, and the workers. The master is the control plane that the user interacts with to manage the containers. Worker nodes are where the containers are deployed and run. A Kubernetes cluster is connected internally through a private network. Cloudflare Tunnel can be used to expose services running inside the Kubernetes cluster to the public.
+A Kubernetes cluster has two components, the primary, and the workers. The primary is the control plane that the user interacts with to manage the containers.
 
 ## Creating the Kubernetes Cluster
 

src/content/docs/cloudflare-one/connections/connect-networks/deployment-guides/terraform.mdx

@@ -438,7 +438,7 @@ If you would prefer to manually install the tunnel, refer to [Install and run th
 
 <Render file="terraform/deploy-terraform" />
 
-It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel, Access application, and Access policy in [Zero Trust](https://one.dash.cloudflare.com). The new DNS records are available in the [Cloudflare dashboard](https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/).
+It may take several minutes for the GCP instance and tunnel to come online. You can view your new tunnel, Access application, and Access policy in [Zero Trust](https://one.dash.cloudflare.com). The new DNS records are available in the [Cloudflare dashboard](/dns/manage-dns-records/how-to/create-dns-records/).
 
 :::note[Remove Terraform resources]