diff --git a/.llms-snapshots/llms-full.txt b/.llms-snapshots/llms-full.txt
index 07ebb346..4bf2a1b2 100644
--- a/.llms-snapshots/llms-full.txt
+++ b/.llms-snapshots/llms-full.txt
@@ -10178,7 +10178,7 @@ The creation wizard for Satellites and Orbiters includes advanced provisioning o
 
 ---
 
-## Hosting Memory
+## Website vs Application
 
 When you initialize a satellite, you must decide how the frontend will be kept in memory and served on the web.
 
@@ -10202,6 +10202,26 @@ For more background on memory behavior and limits, see the [Memory](/docs/miscel
 
 ---
 
+### Summary
+
+The table below summaries the difference regarding the **hosting memory**.
+
+**Note:**
+
+This comparison relates strictly to where your frontend assets (JS, HTML, etc.) are stored and served from.
+
+|     | Website (heap) | Application (stable) |
+| --- | --- | --- |
+| **Best for** | Websites, blogs, content sites | SPAs, feature-rich applications |
+| **Speed** | Faster, more consistent | Slightly slower on average, spikier under load |
+| **Asset size limit** | ~1 GB (serialization on upgrade) | No practical limit |
+| **Upgrade cost** | Assets re-serialized on every upgrade | Assets survive upgrades without re-processing |
+| **SEO impact** | Better (lower TTFB, ~0.5 s faster LCP) | Minor overhead (~0.5 s added to CWV) |
+| **Default in Console** | ✅ Website | ✅ Application |
+| **Can be changed later?** | ✅ Yes — in Hosting › Settings (requires no active files) | ✅ Yes — in Hosting › Settings (requires no active files) |
+
+---
+
 ## Selecting a Subnet
 
 If you want more control over where your module is provisioned, you can select a [subnet](/docs/terminology.md#subnet) during the creation process.
@@ -10688,7 +10708,7 @@ Usage: juno changes reject [options]Options:  -i, --id              The ID of th
 Handle tasks related to the emulator like starting/stopping a local network.
 
 ```
-Usage: juno emulator <subcommand> [options]Subcommands:  clear               Clear the local emulator state (volume and container).  start               Start the emulator for local development.  stop                Stop the local network.  wait                Wait until the emulator is ready.
+Usage: juno emulator <subcommand> [options]Subcommands:  clear               Clear the local emulator state (volume and container).  pull                Pull the latest emulator image.  start               Start the emulator for local development.  stop                Stop the local network.  wait                Wait until the emulator is ready.
 ```
 
 ---
diff --git a/docs/miscellaneous/provisioning-options.mdx b/docs/miscellaneous/provisioning-options.mdx
index 1f7c519b..013e6347 100644
--- a/docs/miscellaneous/provisioning-options.mdx
+++ b/docs/miscellaneous/provisioning-options.mdx
@@ -1,10 +1,15 @@
+---
+toc_min_heading_level: 2
+toc_max_heading_level: 2
+---
+
 # Provisioning Options
 
 The creation wizard for Satellites and Orbiters includes advanced provisioning options for developers who need more control.
 
 ---
 
-## Hosting Memory
+## Website vs Application
 
 When you initialize a satellite, you must decide how the frontend will be kept in memory and served on the web.
 
@@ -30,6 +35,28 @@ For more background on memory behavior and limits, see the [Memory](./memory.md)
 
 ---
 
+### Summary
+
+The table below summaries the difference regarding the **hosting memory**.
+
+:::note
+
+This comparison relates strictly to where your frontend assets (JS, HTML, etc.) are stored and served from.
+
+:::
+
+|                           | Website (heap)                                            | Application (stable)                                      |
+| ------------------------- | --------------------------------------------------------- | --------------------------------------------------------- |
+| **Best for**              | Websites, blogs, content sites                            | SPAs, feature-rich applications                           |
+| **Speed**                 | Faster, more consistent                                   | Slightly slower on average, spikier under load            |
+| **Asset size limit**      | ~1 GB (serialization on upgrade)                          | No practical limit                                        |
+| **Upgrade cost**          | Assets re-serialized on every upgrade                     | Assets survive upgrades without re-processing             |
+| **SEO impact**            | Better (lower TTFB, ~0.5 s faster LCP)                    | Minor overhead (~0.5 s added to CWV)                      |
+| **Default in Console**    | ✅ Website                                                | ✅ Application                                            |
+| **Can be changed later?** | ✅ Yes — in Hosting › Settings (requires no active files) | ✅ Yes — in Hosting › Settings (requires no active files) |
+
+---
+
 ## Selecting a Subnet
 
 If you want more control over where your module is provisioned, you can select a [subnet] during the creation process.