Adding note on storing metadata when writing to

SQLite-backed DO.

Author: Oxyjun

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

@@ -44,7 +44,9 @@ For Durable Object classes with [SQLite storage backend](/durable-objects/best-p
 
 <Render file="limits_increase" product="workers" />
 
-## How much work can a single Durable Object do?
+## Frequently Asked Questions
+
+### How much work can a single Durable Object do?
 
 Durable Objects can scale horizontally across many Durable Objects. Each individual Object is inherently single-threaded.
 
@@ -54,7 +56,7 @@ Durable Objects can scale horizontally across many Durable Objects. Each individ
 
 A Durable Object that receives too many requests will, after attempting to queue them, return an [overloaded](/durable-objects/observability/troubleshooting/#durable-object-is-overloaded) error to the caller.
 
-## How many Durable Objects can I create?
+### How many Durable Objects can I create?
 
 Durable Objects are designed such that the number of individual objects in the system do not need to be limited, and can scale horizontally.
 

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

@@ -118,3 +118,9 @@ In this scenario, the estimated monthly cost would be calculated as:
 ## Storage API billing
 
 <Render file="storage_api_pricing" product="workers" />
+
+:::caution[Metadata when writing to SQLite-backed Durable Object]
+All writes to a SQLite-backed Durable Object records nominal amounts of metadata, which counts towards your billable storage.
+
+The metadata remains until you call [`deleteAll()`](/durable-objects/api/storage-api/#deleteall) on the Durable Object.
+:::