fix: address the sixth review round

- The Ollama upgrade commands hard-coded `--profile gpu` while the comment said
  to use the install's profile. It is a variable now.
- `sim-setup reset` on Kubernetes runs `helm uninstall`, which leaves the
  Postgres volumes behind — they come from a StatefulSet's
  `volumeClaimTemplates`, which Kubernetes does not delete. The row promised a
  full data wipe.
- Noted that the command table drops the `npx` prefix for brevity.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015BwsJTEQRzWJaY4BRCkPZt

Author: waleedlatif1

apps/docs/content/docs/platform/self-hosting/docker.mdx

@@ -162,7 +162,7 @@ docker compose -f "$COMPOSE_FILE" up -d --force-recreate simstudio
 
 ## The `sim-setup` CLI
 
-`npx sim-setup` also manages an existing install created from the production or local-development Compose files. It does not detect or manage an Ollama-stack install. Run it from the directory holding your `.env` and Compose file.
+`npx sim-setup` also manages an existing install created from the production or local-development Compose files. It does not detect or manage an Ollama-stack install. Run it from the directory holding your `.env` and Compose file. The table drops the `npx` prefix for brevity — keep it unless you installed the package globally.
 
 | Command | What it does |
 |---|---|
@@ -172,7 +172,7 @@ docker compose -f "$COMPOSE_FILE" up -d --force-recreate simstudio
 | `sim-setup start` / `stop` / `restart` | Bring the install up, down, or cycle it. On a source checkout this covers only the managed Postgres and Redis containers — the dev server is yours to start and stop. On Kubernetes it prints the equivalent `kubectl` commands instead of acting |
 | `sim-setup update` | Pull or rebuild images and apply them. Compose installs only — it refuses on source checkouts and Kubernetes, which update through git and `helm upgrade` |
 | `sim-setup down` | Remove containers, keep the data |
-| `sim-setup reset` | Archive `.env` and wipe managed data |
+| `sim-setup reset` | Archive `.env` and wipe managed data. On Kubernetes it runs `helm uninstall`, which leaves the Postgres volumes behind — they come from a StatefulSet's `volumeClaimTemplates`, which Kubernetes never deletes. Delete those PVCs yourself to reset the data |
 | `sim-setup config` | Show configured capabilities and integrations |
 | `sim-setup doctor` | Check the setup. `--fix` repairs what it can, `--json` prints machine-readable output |
 | `sim-setup add <feature>` | Configure one capability: `email`, `storage`, `sandbox`, `jobs`, `cache`, `knowledge`, `knowledge-embeddings`, `chat`, `llm`, or `integration <slug>` |

apps/docs/content/docs/platform/self-hosting/upgrades.mdx

@@ -196,10 +196,11 @@ Inspect the result with `npx sim-setup logs`, which targets whichever Compose fi
 The CLI detects only those two files. An install started from `docker-compose.ollama.yml` is invisible to it — `update`, `logs`, and `status` all report no install — so upgrade that stack directly:
 
 ```bash
-# Same --profile you installed with: gpu or cpu. The Ollama service is
-# profile-scoped, so an unprofiled command silently skips it.
-docker compose -f docker-compose.ollama.yml --profile gpu pull
-docker compose -f docker-compose.ollama.yml --profile gpu up -d
+# The Ollama service is profile-scoped, so an unprofiled command silently
+# skips it. Use the profile you installed with.
+PROFILE=gpu  # or cpu
+docker compose -f docker-compose.ollama.yml --profile "$PROFILE" pull
+docker compose -f docker-compose.ollama.yml --profile "$PROFILE" up -d
 ```
 
 <Callout type="warn">