diff --git a/content/docs/build/marketplace.mdx b/content/docs/build/marketplace.mdx
index 7f7d47b..5305d33 100644
--- a/content/docs/build/marketplace.mdx
+++ b/content/docs/build/marketplace.mdx
@@ -57,7 +57,7 @@ You ─→ ObjectOS ─→ Marketplace tab ─→ pick app ─→ Install
 
 | Catalog | Source | When to use |
 |---|---|---|
-| **Default** | Pre-bundled with the runtime image | First-time eval, demos, offline |
+| **Default** | Pre-bundled with the ObjectOS runtime image | First-time eval, demos, offline |
 | **ObjectStack public catalog** | Public app registry | Latest community + first-party apps |
 | **Private catalog** | Your own published artifacts | Internal apps you don't want public |
 | **Local** | Files mounted into the runtime | Air-gapped, custom builds |
diff --git a/content/docs/deploy/air-gapped.mdx b/content/docs/deploy/air-gapped.mdx
index a482192..06fdc5a 100644
--- a/content/docs/deploy/air-gapped.mdx
+++ b/content/docs/deploy/air-gapped.mdx
@@ -81,8 +81,9 @@ with it.
 
 ## Getting the image inside the network
 
-The runtime image lives in a private registry that a disconnected site cannot
-reach, so the image crosses the boundary the way your other artefacts do.
+The ObjectOS runtime image lives in a private registry that a disconnected
+site cannot reach, so the image crosses the boundary the way your other
+artefacts do.
 
 Do the verification on the connected side, while you still have the registry
 and the tooling: check the **signature**, the **SBOM** and the **build
diff --git a/content/docs/reference/environment-variables.mdx b/content/docs/reference/environment-variables.mdx
index e5eb336..7128404 100644
--- a/content/docs/reference/environment-variables.mdx
+++ b/content/docs/reference/environment-variables.mdx
@@ -156,7 +156,7 @@ they can be used.
 | Retired name | What to use instead |
 |---|---|
 | `OS_ARTIFACT_FILE` | `OS_ARTIFACT_URL`. Nothing in the shipped runtime reads `OS_ARTIFACT_FILE`; a deployment that sets it gets the boot it would have got with nothing set, and no error naming the mistake. A local file is `file://` on the replacement, and the replacement carries the integrity pin. |
-| `OS_ARTIFACT_PATH` | `OS_ARTIFACT_URL`. **The runtime image refuses a boot that carries a non-default `OS_ARTIFACT_PATH`**, naming the replacement. Two spellings for "which artifact do I boot" is one dialect too many, and the retired one never carried an integrity pin. |
+| `OS_ARTIFACT_PATH` | `OS_ARTIFACT_URL`. **The ObjectOS runtime image refuses a boot that carries a non-default `OS_ARTIFACT_PATH`**, naming the replacement. Two spellings for "which artifact do I boot" is one dialect too many, and the retired one never carried an integrity pin. |
 | `OS_BUSINESS_DB_URL` | `OS_DATABASE_URL`, or a datasource declared in the artifact. Nothing reads `OS_BUSINESS_DB_URL`; a deployment that sets it and nothing else has no database configured at all. |
 
 `OS_CLOUD_API_KEY` is **not** a variable a self-hosted deployment sets. It is
diff --git a/content/docs/reference/runtime-capabilities.mdx b/content/docs/reference/runtime-capabilities.mdx
index d4141b8..dc14100 100644
--- a/content/docs/reference/runtime-capabilities.mdx
+++ b/content/docs/reference/runtime-capabilities.mdx
@@ -56,8 +56,8 @@ when an optional package is missing during development — but in
 1. Treat capability warnings as deployment failures. Grep startup logs
    for `capability not loaded` (or your equivalent) and fail the
    readiness probe / rollout if any appear.
-2. Pin the runtime image to one that includes every package your
-   artifacts declare in `requires`.
+2. Pin the ObjectOS runtime image to one that includes every package
+   your artifacts declare in `requires`.
 3. When publishing an artifact, document its `requires` list alongside
    it so operators can verify the matching image.