Moving build a counter into a separate example folder.

Author: Oxyjun

src/content/docs/durable-objects/examples/build-a-counter.mdx renamed to src/content/docs/durable-objects/examples/kv-storage-examples/build-a-counter.mdx

@@ -0,0 +1,14 @@
+---
+title: Key-value storage examples
+pcx_content_type: navigation
+sidebar:
+  order: 90
+  group:
+    hideIndex: true
+---
+
+import { ListExamples, GlossaryTooltip } from "~/components";
+
+Explore the following <GlossaryTooltip term="code example">examples</GlossaryTooltip> for Durable Objects.
+
+<ListExamples />

src/content/docs/durable-objects/examples/kv-storage-examples/index.mdx

@@ -25,7 +25,7 @@ With RPC, the `DurableObject` superclass defines `ctx` and `env` as class proper
 
 :::
 
-Refer to [Build a Counter](/durable-objects/examples/build-a-counter/) for a complete example.
+Refer to [Build a Counter](/durable-objects/examples/kv-storage-examples/build-a-counter/) for a complete example.
 
 ### Invoking the `fetch` handler
 

src/content/docs/durable-objects/features/create-durable-object-stubs-and-send-requests.mdx

@@ -39,7 +39,7 @@ In the example above, using a global variable `value` instead of the instance va
 
 :::note[Built-in caching]
 
-The Durable Object's storage has a built-in in-memory cache of its own. If you use `get()` to retrieve a value that was read or written recently, the result will be instantly returned from cache. Instead of writing initialization code like above, you could use `get("value")` whenever you need it, and rely on the built-in cache to make this fast. Refer to the [Build a counter example](/durable-objects/examples/build-a-counter/) to learn more about this approach.
+The Durable Object's storage has a built-in in-memory cache of its own. If you use `get()` to retrieve a value that was read or written recently, the result will be instantly returned from cache. Instead of writing initialization code like above, you could use `get("value")` whenever you need it, and rely on the built-in cache to make this fast. Refer to the [Build a counter example](/durable-objects/examples/kv-storage-examples/build-a-counter/) to learn more about this approach.
 
 However, in applications with more complex state, explicitly storing state in your Object may be easier than making Storage API calls on every access. Depending on the configuration of your project, write your code in the way that is easiest for you.