# DistributionPackages
-Build recipes, authenticated handoffs, signing and publication for SNodeC distribution packages. This is the maintainer control repository; [Packages](https://github.com/SNodeC/Packages#project-overview) is the public installation and availability hub.
+Build recipes, authenticated handoffs, signing and publication for SNode.C distribution packages. This is the maintainer control repository; [Packages](https://github.com/SNodeC/Packages#project-overview) is the public installation and availability hub.
## Operations
diff --git a/docs/README.md b/docs/README.md
index bacf8cb..1cfae66 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -1,7 +1,7 @@
# Repository maintenance
@@ -61,7 +61,7 @@ Superseded files remain for 30 days after leaving the active index. Cleanup runs
| [MQTTSuite build-distribution-packages.yml](https://github.com/SNodeC/mqttsuite/blob/master/.github/workflows/build-distribution-packages.yml) | Same lifecycle, using the corresponding published SNode.C dependency |
| [sign-and-publish-packages.yml](https://github.com/SNodeC/DistributionPackages/blob/main/.github/workflows/sign-and-publish-packages.yml) | Validate completed upstream artifacts, sign, publish and dispatch dependent targets |
-The manual-only **Render package status** workflow in DistributionPackages runs the default-branch renderer against the current Packages state, with the existing publication concurrency group and metadata retry transaction. It does not build, sign or publish packages, and is not triggered automatically after merge. Run it only after explicit approval. Locally: `python3 -m ci.publish.publication render /path/to/Packages`. The local renderer preserves authored documentation, feed records and `status.json`. The approved manual workflow also hands off the current `site/` README, documentation and keys guide through the same metadata retry transaction; it removes obsolete documentation without changing key bytes or installer behavior.
+The manual-only **Publish package guides and render status** workflow in DistributionPackages runs the default-branch renderer against the current Packages state, with the existing publication concurrency group and metadata retry transaction. It does not build, sign or publish packages, and is not triggered automatically after merge. Run it only after explicit approval. Locally: `python3 -m ci.publish.publication render /path/to/Packages`. The local renderer preserves authored documentation, feed records and `status.json`. The approved manual workflow also hands off the current `site/` README, documentation and keys guide through the same metadata retry transaction; it removes obsolete documentation without changing key bytes or installer behavior.
SNode.C and MQTTSuite package workflows also support a manual fresh start: choose **Run workflow** on the source repository’s default branch and supply an existing `vMAJOR.MINOR.PATCH` tag as `release_tag`. This allocates a new package revision and captures that tag with current DistributionPackages tooling; no tag is created, moved or deleted. Publication authenticates the manual run’s repository, workflow, default branch, capture identity, attempt and target job. Tag/Version validation remains in the existing capture path. A job retry retains the original capture and requires its artifact; a new manual start is the recovery route when a full rerun loses that artifact.
diff --git a/docs/media/banner.svg b/docs/media/banner.svg
index 90f27d3..0a572ce 100644
--- a/docs/media/banner.svg
+++ b/docs/media/banner.svg
@@ -1 +1 @@
-
+
diff --git a/docs/media/hero-mobile.svg b/docs/media/hero-mobile.svg
index 5f2dcf5..e9a9ce6 100644
--- a/docs/media/hero-mobile.svg
+++ b/docs/media/hero-mobile.svg
@@ -1 +1 @@
-
+
diff --git a/docs/media/nav/organization-dark.svg b/docs/media/nav/organization-dark.svg
index a63a53c..b7f440f 100644
--- a/docs/media/nav/organization-dark.svg
+++ b/docs/media/nav/organization-dark.svg
@@ -1,4 +1,4 @@
-