Jun/PCX edits part 1

Author: Oxyjun

src/content/docs/durable-objects/api/alarms.mdx

@@ -2,7 +2,7 @@
 title: Alarms
 pcx_content_type: concept
 sidebar:
-  order: 4
+  order: 6
 ---
 
 import { Type } from "~/components";
@@ -37,16 +37,13 @@ Alarms can be used to build distributed primitives, like queues or batching of w
 
 ### getAlarm
 
-- `getAlarm()`: <Type text ='number | null' />
+- <code>getAlarm()</code>: <Type text ='number | null' />
 
   - If there is an alarm set, then return the currently set alarm time in number of milliseconds elapsed since the UNIX epoch. Otherwise, return `null`.
 
 ### setAlarm
 
-- <code>
-  	setAlarm(scheduledTimeMs <Type text="number" />)
-  </code>
-  : <Type text="void" />
+- <code> setAlarm(scheduledTimeMs <Type text="number" />)</code>: <Type text="void" />
 
   - Set the time for the alarm to run at in number of milliseconds elapsed since the UNIX epoch.
 

src/content/docs/durable-objects/api/id.mdx

@@ -9,13 +9,13 @@ import { Tabs, TabItem } from "~/components";
 
 ## Description
 
-The `DurableObjectId` interface refers to a new or existing Durable Object instance. This interface is most frequently used to by [`DurableObjectNamespace::get`](./namespace.mdx) to obtain a stub for submitting requests to the Durable Object class.
+The `DurableObjectId` interface refers to a new or existing Durable Object instance. This interface is most frequently used by [`DurableObjectNamespace::get`](./namespace.mdx) to obtain a stub for submitting requests to the Durable Object class.
 
 Note that creating an ID for a Durable Object instance does not invoke the constructor of the Durable Object. This is done lazily when calling [`DurableObjectNamespace::get`](../namespace/#get) to create a [`DurableObjectStub`](../stub) from a `DurableObjectId`. This ensures that objects are not constructed unless their methods can be directly invoked.
 
 :::note[`DurableObjectId`]
 
-If you are experiencing an issue with a particular Durable Object instance the `DurableObjectId` corresponding to this particular instance is very helpful for obtaining a resolution through Cloudflare support. It is advisable to log a `DurableObjectId` from a Worker and include it in support requests where applicable.
+If you are experiencing an issue with a particular Durable Object instance, you may wish to log the `DurableObjectId` from your Worker and include it in your Cloudflare support request.
 
 :::
 

src/content/docs/durable-objects/api/namespace.mdx

@@ -9,9 +9,9 @@ import { Tabs, TabItem } from "~/components";
 
 ## Description
 
-The `DurableObjectNamespace` interface is used to obtain a reference to a new or existing Durable Object instance. The interface is accessible from the fetch handler on a Cloudflare Worker via the `env` parameter, which is the standard interface for reference bindings declared in `wrangler.toml`.
+The `DurableObjectNamespace` interface is used to obtain a reference to a new or existing Durable Object instance. The interface is accessible from the fetch handler on a Cloudflare Worker via the `env` parameter, which is the standard interface when referencing bindings declared in `wrangler.toml`.
 
-There are several functions of this interface that can be used to create an ID for a Durable Object instance. Note that creating an ID for a Durable Object instance does not invoke the constructor of the Durable Object. This is done lazily when calling [`DurableObjectNamespace::get`](../namespace/#get) to create a [`DurableObjectStub`](../stub) from a `DurableObjectId`. This ensures that objects are not constructed unless their methods can be directly invoked.
+This interface defines several [methods](../namespace/#methods) that can be used to create an ID for a Durable Object instance. Note that creating an ID for a Durable Object instance does not invoke the constructor of the Durable Object. This is done lazily when calling [`DurableObjectNamespace::get`](../namespace/#get) to create a [`DurableObjectStub`](../stub) from a `DurableObjectId`. This ensures that objects are not constructed unless their methods can be directly invoked.
 
 <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
 
@@ -84,14 +84,13 @@ The string to be used to generate a [`DurableObjectId`](../id) corresponding to
 
 #### Return value
 
-A [`DurableObjectId`](../id) refering to an instance of a Durable Object class.
+A [`DurableObjectId`](../id) referring to an instance of a Durable Object class.
 
 ### `newUniqueId`
 
 #### Description
 
-creates a `DurableObjectId` which refers to an individual instance of the
-Durable Object class.
+`newUniqueId` creates a `DurableObjectId` which refers to an individual instance of the Durable Object class.
 
 ```js
 const id = env.MY_DURABLE_OBJECT.newUniqueId();
@@ -110,7 +109,7 @@ An optional object with the key `jurisdiction` and value of a [jurisdiction](../
 
 #### Return value
 
-A [`DurableObjectId`](../id) refering to an instance of the Durable Object class.
+A [`DurableObjectId`](../id) referring to an instance of the Durable Object class.
 
 ### `idFromString`
 
@@ -133,7 +132,7 @@ The string corresponding to a [`DurableObjectId`](../id) previously generated ei
 
 #### Return value
 
-A [`DurableObjectId`](../id) refering to an instance of a Durable Object class.
+A [`DurableObjectId`](../id) referring to an instance of a Durable Object class.
 
 ### `get`
 
@@ -152,7 +151,7 @@ A required [`DurableObjectId`](../id) and an optional object with the key `locat
 
 #### Return value
 
-A [`DurableObjectStub`](../stub) refering to an instance of a Durable Object class.
+A [`DurableObjectStub`](../stub) referring to an instance of a Durable Object class.
 
 ### `jurisdiction`
 

src/content/docs/durable-objects/api/storage-api.mdx

@@ -2,7 +2,7 @@
 title: Storage API
 pcx_content_type: concept
 sidebar:
-  order: 2
+  order: 4
 
 ---
 
@@ -100,7 +100,7 @@ Each method is implicitly wrapped inside a transaction, such that its results ar
 
 * <code>deleteAll(options <Type text='Object' /> <MetaInfo text='optional' />)</code>: <Type text='Promise' />
 
-  * Deletes all stored data, effectively deallocating all storage used by the Durable Object. For Durable Objects with a key-value storage backend, `deleteAll()` removes all keys and associated values for an individual Durable Object. For Durable Objects with a [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend), `deleteAll()` removes the entire contents of a Durable Object's private SQLite database.  
+  * Deletes all stored data, effectively deallocating all storage used by the Durable Object. For Durable Objects with a key-value storage backend, `deleteAll()` removes all keys and associated values for an individual Durable Object. For Durable Objects with a [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend), `deleteAll()` removes the entire contents of a Durable Object's private SQLite database.
   * For Durable Objects with a key-value storage backend, an in-progress `deleteAll()` operation can fail, which may leave a subset of data undeleted. Durable Objects with a SQLite storage backend do not have a partial `deleteAll()` issue because `deleteAll()` operations are atomic (all or nothing).
   * `deleteAll()` does not proactively delete [Alarms](/durable-objects/api/alarms/). Use [`deleteAlarm()`](/durable-objects/api/alarms/#deletealarm) to delete an alarm.
 

src/content/docs/durable-objects/api/webgpu.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: configuration
 title: WebGPU
 sidebar:
-  order: 4
+  order: 7
 ---
 
 :::caution

src/content/docs/durable-objects/api/websockets.mdx

@@ -2,7 +2,7 @@
 title: WebSockets
 pcx_content_type: concept
 sidebar:
-  order: 3
+  order: 5
 
 ---
 

src/content/docs/durable-objects/api/workers-rs.mdx

@@ -3,6 +3,6 @@ pcx_content_type: navigation
 title: Rust API
 external_link: https://github.com/cloudflare/workers-rs?tab=readme-ov-file#durable-objects
 sidebar:
-  order: 5
+  order: 10
 
 ---

src/content/docs/durable-objects/reference/data-location.mdx

@@ -11,13 +11,13 @@ Jurisdictions are used to create Durable Object instances that only run and stor
 
 Workers may still access Durable Objects constrained to a jurisdiction from anywhere in the world. The jurisdiction constraint only controls where the Durable Object itself runs and persists data. Consider using [Regional Services](/data-localization/regional-services/) to control the regions from which Cloudflare responds to requests.
 
-:::note[logging]
+:::note[Logging]
 
 A [`DurableObjectId`](../../api/id) will be logged outside of the specified jurisdiction for billing and debugging purposes.
 
 :::
 
-Durable Object instances can be restricted to a specific jurisdiction either by creating a [`DurableObjectNamespace`](../../api/namespace/) restricted to a jurisdiction or by creating an individual [`DurableObjectId`](../../api/id) restricted to a jurisdiction:
+Durable Object instances can be restricted to a specific jurisdiction either by creating a [`DurableObjectNamespace`](../../api/namespace/) restricted to a jurisdiction, or by creating an individual [`DurableObjectId`](../../api/id) restricted to a jurisdiction:
 
 ```js
 const euSubnamespace = env.MY_DURABLE_OBJECT.jurisdiction("eu");
@@ -34,7 +34,7 @@ const euId2 = env.MY_DURABLE_OBJECT.jurisdiction("eu").idFromName("my-name");
 console.assert(!euId1.equal(euId2), "This should always be true");
 ```
 
-While methods on a [`DurableObjectNamespace`](../../api/namespace/) that take a [`DurableObjectId`](../../api/id) as a parameter will throw an exception if the parameter is associated with a different jurisdiction, these methods will not throw an exception if the [`DurableObjectNamespace`](../../api/namespace/) is not associated with a jurisdiction. The common case is that any valid [`DurableObjectId`](../../api/id) can be used in the top-level namespace's methods.
+Methods on a [`DurableObjectNamespace`](../../api/namespace/) that take a [`DurableObjectId`](../../api/id) as a parameter will throw an exception if the parameter is associated with a different jurisdiction. However, these methods will not throw an exception if the [`DurableObjectNamespace`](../../api/namespace/) is not associated with a jurisdiction. The common case is that any valid [`DurableObjectId`](../../api/id) can be used in the top-level namespace's methods.
 
 ```js
 const euSubnamespace = env.MY_DURABLE_OBJECT.jurisdiction("eu");