Style guide changes and replace CF's edge for global network

Author: RebeccaTamachiro

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

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: concept
-title: Static Assets
+title: Static assets
 ---
 Workers for Platforms lets you deploy front-end applications at scale. By hosting static assets on Cloudflare's global network, you can deliver faster load times worldwide and eliminate the need for external infrastructure. You can also combine these static assets with dynamic logic in Cloudflare Workers, providing a full-stack experience for your customers.
 
@@ -25,11 +25,11 @@ Deploy front-end assets alongside server-side logic, all within Cloudflare Worke
 
 ---
 
-## Deploying static assets to User Workers
+## Deploy static assets to User Workers
 
-It's common that as the Platform, you will be responsible for uploading static assets on behalf of your end users. This often looks like this:
+It is common that, as the Platform, you will be responsible for uploading static assets on behalf of your end users. This often looks like this:
 
-1. User uploads files (HTML, CSS, images) through your interface.
+1. Your user uploads files (HTML, CSS, images) through your interface.
 2. Your platform interacts with the Workers for Platforms APIs to attach the static assets to the User Worker script.
 
 Once you receive the static files from your users (for a new or updated site), complete the following steps to attach the files to the corresponding User Worker:
@@ -38,7 +38,7 @@ Once you receive the static files from your users (for a new or updated site), c
 2. Upload file contents
 3. Deploy/Update the Worker
 
-After these steps are completed, the User Worker's static assets will be live on Cloudflare's edge.
+After these steps are completed, the User Worker's static assets will be live on the Cloudflare's global network.
 
 ### 1. Create an Upload Session
 
@@ -63,7 +63,7 @@ Before sending any file data, you need to tell Cloudflare which files you intend
 }
 ```
 
-To start the upload process, send a POST request to the Create Assets Upload Session [API endpoint](/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/subresources/asset_upload/methods/create/)
+To start the upload process, send a POST request to the Create Assets Upload Session [API endpoint](/api/resources/workers_for_platforms/subresources/dispatch/subresources/namespaces/subresources/scripts/subresources/asset_upload/methods/create/).
 
 ```bash
 POST /accounts/{account_id}/workers/dispatch/namespaces/{namespace}/scripts/{script_name}/assets-upload-session
@@ -103,10 +103,13 @@ You can compute a SHA-256 digest of the file contents, then truncate or otherwis
 **API Response**
 
 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)
+
+* `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.
 
-**Note**: This step alone does not store files on Cloudflare. You must upload the actual file data in the next step.
+:::note
+This step alone does not store files on Cloudflare. You must upload the actual file data in the next step.
+:::
 
 ### 2. Upload File Contents
 
@@ -129,7 +132,7 @@ This token is valid for one hour and must be supplied for each upload request to
 **File fields (multipart/form-data)**
 You must send the files as multipart/form-data with base64-encoded content:
 
-* Field name: The file hash (for example, "36b8be012ee77df5f269b11b975611d3")
+* Field name: The file hash (for example, `36b8be012ee77df5f269b11b975611d3`)
 * Field value: A Base64-encoded string of the file's raw bytes
 
 **Example: Uploading multiple files within a single bucket**
@@ -161,7 +164,7 @@ curl -X POST \
 
 If you have multiple buckets (for example, `[["hashA"], ["hashB"], ["hashC"]]`), you might need to repeat this process for each bucket, making one request per bucket group.
 
-Once every file in the manifest has been uploaded, a status code of 201 will be returned, with the `jwt` field present. This JWT is a final "completion" token which can be used to create a deployment of a Worker with this set of assets. This completion token is valid for 1 hour.
+Once every file in the manifest has been uploaded, a status code of `201` will be returned, with the `jwt` field present. This JWT is a final "completion" token which can be used to create a deployment of a Worker with this set of assets. This completion token is valid for 1 hour.
 
 ```json
 {
@@ -176,11 +179,11 @@ Once every file in the manifest has been uploaded, a status code of 201 will be
 
 `<completion-token>` indicates that Cloudflare has successfully received and stored the file contents specified by your manifest. You will use this `<completion-token>` in Step 3 to finalize the attachment of these files to the Worker.
 
-### 3. Deploy the User Worker with Static Assets
+### 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.
 
-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).
+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).
 
 **API request example:**
 
@@ -204,7 +207,7 @@ curl -X PUT \
 
 * The `"jwt": "<completion-token>"` links the newly uploaded files to the Worker
 * Including "html_handling" (or other fields under "config") is optional and can customize how static files are served
-* If the user's Worker code hasn't changed, you can omit the code file or re-upload the same index.js
+* If the user's Worker code has not changed, you can omit the code file or re-upload the same index.js
 
 Once this PUT request succeeds, the files are served on the User Worker. Requests routed to that Worker will serve the new or updated static assets.
 
@@ -242,7 +245,7 @@ export default {
   },
 };
 ```
-### 2. Deploy the User Worker with the Static Assets
+### 2. Deploy the User Worker with the static assets
 
 Run Wrangler to publish both your Worker code and the static assets: