Accepting PCX Review part 2

Author: Oxyjun

src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx

@@ -15,7 +15,7 @@ A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/
 ## Access storage
 
 :::note[Recommended SQLite-backed Durable Objects]
-We recommend all new Durable Object classes use the [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class).
+Cloudflare recommends all new Durable Object classes use the [SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class).
 
 The [key-value storage backend](/durable-objects/reference/durable-objects-migrations/#create-durable-object-class-with-key-value-storage) remains for backwards compatibility, and a migration path from KV storage to SQLite storage for existing Durable Object classes will be available in the future.
 :::

src/content/docs/durable-objects/platform/pricing.mdx

@@ -20,7 +20,7 @@ These examples exclude the costs for the Workers calling the Durable Objects. Wh
 * Inactive objects receiving no requests do not incur any duration charges.
 * The [WebSocket Hibernation API](/durable-objects/best-practices/websockets#websocket-hibernation-api) can dramatically reduce duration-related charges for Durable Objects communicating with clients over the WebSocket protocol, especially if messages are only transmitted occasionally at sparse intervals.
 
-#### Example 1
+### Example 1
 
 This example represents a simple Durable Object used as a co-ordination service invoked via HTTP.
 
@@ -40,7 +40,7 @@ In this scenario, the estimated monthly cost would be calculated as:
 
 **Estimated total**: \~$0.075 (requests) + $0.00 (compute duration) + minimum $5/mo usage = $5.08 per month
 
-#### Example 2
+### Example 2
 
 This example represents a moderately trafficked Durable Objects based application using WebSockets to broadcast game, chat or real-time user state across connected clients:
 
@@ -64,7 +64,7 @@ In this scenario, the estimated monthly cost would be calculated as:
 
 **Estimated total**: $0.41 (requests) + $133.24 (compute duration) + minimum $5/mo usage = $138.65 per month.
 
-#### Example 3
+### Example 3
 
 This example represents a horizontally scaled Durable Objects based application using WebSockets to communicate user-specific state to a single client connected to each Durable Object.
 
@@ -88,7 +88,7 @@ In this scenario, the estimated monthly cost would be calculated as:
 
 **Estimated total**: $1.79 (requests) + $409.72 (compute duration) + minimum $5/mo usage = $416.51 per month
 
-#### Example 4
+### Example 4
 
 This example represents a moderately trafficked Durable Objects based application using WebSocket Hibernation to broadcast game, chat or real-time user state across connected clients:
 

src/content/glossary/durable-objects.yaml

@@ -74,5 +74,5 @@ entries:
 
   - term: "bookmark"
     general_definition: |-
-      A bookmark is a mostly alphanumeric string like 0000007b-0000b26e-00001538-0c3e87bb37b3db5cc52eedb93cd3b96b which represents a specific state of a SQLite database at a certain point in time. Bookmarks are designed to be lexically comparable: a bookmark representing an earlier point in time compares less than one representing a later point, using regular string comparison.
+      A bookmark is a mostly alphanumeric string like `0000007b-0000b26e-00001538-0c3e87bb37b3db5cc52eedb93cd3b96b` which represents a specific state of a SQLite database at a certain point in time. Bookmarks are designed to be lexically comparable: a bookmark representing an earlier point in time compares less than one representing a later point, using regular string comparison.
 

src/content/partials/durable-objects/durable-objects-pricing.mdx

@@ -1,5 +1,6 @@
 ---
-{}
+params:
+  - product
 ---
 
 import {Render, Markdown, GlossaryTooltip, Details, AnchorHeading } from "~/components";
@@ -66,7 +67,7 @@ The [Durable Objects Storage API](/durable-objects/api/storage-api) is only acce
 
 <sup>2</sup> Key-value methods like `get()`, `put()`, `delete()`, or `list()` store and query data in a hidden SQLite table and are billed as rows read and rows written.
 
-<sup>3</sup>  Each `setAlarm` is billed as a single row written.
+<sup>3</sup>  Each `setAlarm()` is billed as a single row written.
 
 <sup>4</sup>  Deletes are counted as rows_written.