diff --git a/src/content/partials/durable-objects/do-faq-pricing.mdx b/src/content/partials/durable-objects/do-faq-pricing.mdx
index a3204638e7ffe4..be4a1b72770778 100644
--- a/src/content/partials/durable-objects/do-faq-pricing.mdx
+++ b/src/content/partials/durable-objects/do-faq-pricing.mdx
@@ -9,6 +9,7 @@ A Durable Object incurs duration charges as long as the JavaScript object has to
 Once an object has been evicted from memory, the next time it is needed, it will be recreated (calling the constructor again).
 
 There are several factors that contribute in keeping the Durable Object in memory and keeping it from hibernating or being inactive.
+
 Find more information in [Lifecycle of a Durable Object](/durable-objects/concepts/durable-object-lifecycle/).
 
 ### Does an empty table / SQLite database contribute to my storage?
diff --git a/src/content/partials/durable-objects/durable-objects-pricing.mdx b/src/content/partials/durable-objects/durable-objects-pricing.mdx
index 2e080b82a45873..587b797160c165 100644
--- a/src/content/partials/durable-objects/durable-objects-pricing.mdx
+++ b/src/content/partials/durable-objects/durable-objects-pricing.mdx
@@ -32,7 +32,7 @@ await durableObjectStub.cat(); // billed as a request
 
 <sup>3</sup> Application level auto-response messages handled by [`state.setWebSocketAutoResponse()`](/durable-objects/best-practices/websockets/) will not incur additional wall-clock time, and so they will not be charged.
 
-<sup>4</sup> Duration is billed in wall-clock time as long as the Object is active, but is shared across all requests active on an Object at once. Calling `accept()` on a WebSocket in an Object will incur duration charges for the entire time the WebSocket is connected. It is recommended to use the WebSocket Hibernation API to avoid incurring duration charges once all event handlers finish running. Note that the Durable Object will remain active for 10 seconds after the last client disconnects. For a complete explanation, refer to [When does a Durable Object incur duration charges?](/durable-objects/platform/pricing/#when-does-a-durable-object-incur-duration-charges).
+<sup>4</sup> Duration is billed in wall-clock time as long as the Object is active, but is shared across all requests active on an Object at once. Calling `accept()` on a WebSocket in an Object will incur duration charges for the entire time the WebSocket is connected. It is recommended to use the WebSocket Hibernation API to avoid incurring duration charges once all event handlers finish running. For a complete explanation, refer to [When does a Durable Object incur duration charges?](/durable-objects/platform/pricing/#when-does-a-durable-object-incur-duration-charges).
 
 <sup>5</sup> Duration billing charges for the 128 MB of memory your Durable Object is allocated, regardless of actual usage. If your account creates many instances of a single Durable Object class, Durable Objects may run in the same isolate on the same physical machine and share the 128 MB of memory. These Durable Objects are still billed as if they are allocated a full 128 MB of memory.