From 99d60459e75a249d5b940284097e8b6e450a8e4a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Vin=C3=ADcius=20Ferr=C3=A3o?=
 <2031761+viniciusferrao@users.noreply.github.com>
Date: Sun, 6 Sep 2026 10:54:29 -0300
Subject: [PATCH] docs(genesis): explain release formats

---
 BUILD.md                       |  5 +++--
 genesis-openembedded/README.md | 15 +++++++--------
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/BUILD.md b/BUILD.md
index eb04577..7ce76e3 100644
--- a/BUILD.md
+++ b/BUILD.md
@@ -248,8 +248,9 @@ or backup directories behind, rerun it with ``--force-unlock`` to recover the
 previous repository before starting a new publication.
 
 Repository publication requires all eight current architectures. Version 1
-remains readable but cannot replace the current repository because it lacks
-`s390x`. The packages are `noarch`, and each publication contains the full set.
+release manifests remain readable, but they cannot replace the current
+repository because they lack `s390x`. The packages are `noarch`, and each
+publication contains the full set.
 
 The release checksums cover the unsigned input packages. If repository signing
 is enabled, `rpmsign` changes the deployed RPM bytes after collection.
diff --git a/genesis-openembedded/README.md b/genesis-openembedded/README.md
index 78871fe..d20beb8 100644
--- a/genesis-openembedded/README.md
+++ b/genesis-openembedded/README.md
@@ -89,14 +89,13 @@ repository with a single rename, under one global publish lock, so a failed or
 interrupted publication leaves the previous repository exactly as it was.
 
 Both consumers verify package identities and checksums before publication.
-Version 2 releases require all eight architectures. Version 1 remains readable,
-but current publishers refuse it because replacing the repository would remove
-`s390x`. Builder and publisher hosts must use the same xcat-dep revision when
-the release format changes. Building `s390x` requires an xcat-core revision
-that reports the target.
-Merge or deploy that xcat-core change first. Builds for the other architectures
-still accept older xcat-core revisions. A management node can install an image
-for a different target architecture.
+Releases containing `s390x` use format version 2. Other releases keep version 1
+and remain readable by older tools. Current publishers require all eight
+architectures, so a version 1 release cannot replace the shared repository.
+Building `s390x` requires an xcat-core revision that reports the target. Merge
+or deploy that xcat-core change first. Builds for the other architectures still
+accept older xcat-core revisions. A management node can install an image for a
+different target architecture.
 
 Without `--genesis-release`, both builders keep their existing behavior. The
 new packages do not provide, replace, or obsolete the old package names.