Removing incorrect wording (#24065)

Oxyjun · thomasgauvin · commit 68908967784c · 2025-08-15T16:52:34.000-04:00
diff --git a/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx b/src/content/docs/durable-objects/concepts/durable-object-lifecycle.mdx
@@ -74,4 +74,4 @@ Objects in the **hibernated** state keep their Websocket clients connected, and
 
 The next incoming request or event starts the cycle again.
 
-As explained in [When does a Durable Object incur duration charges?](/durable-objects/platform/pricing/#when-does-a-durable-object-incur-duration-charges), a Durable Object incurs charges only when it is **actively running in-memory**, or when it is **idle in-memory and non-hibernateable**, the two states highlighted in red in the above diagram.
+As explained in [When does a Durable Object incur duration charges?](/durable-objects/platform/pricing/#when-does-a-durable-object-incur-duration-charges), a Durable Object incurs charges only when it is **actively running in-memory**, or when it is **idle in-memory and non-hibernateable**.

Original file line number	Diff line number	Diff line change
`@@ -74,4 +74,4 @@ Objects in the hibernated state keep their Websocket clients connected, and`
`74`	`74`
`75`	`75`	`The next incoming request or event starts the cycle again.`
`76`	`76`
`77`		`-As explained in [When does a Durable Object incur duration charges?](/durable-objects/platform/pricing/#when-does-a-durable-object-incur-duration-charges), a Durable Object incurs charges only when it is actively running in-memory, or when it is idle in-memory and non-hibernateable, the two states highlighted in red in the above diagram.`
	`77`	`+As explained in [When does a Durable Object incur duration charges?](/durable-objects/platform/pricing/#when-does-a-durable-object-incur-duration-charges), a Durable Object incurs charges only when it is actively running in-memory, or when it is idle in-memory and non-hibernateable.`