From a21071b51f7ecc56130f08cb77d1d84903a5ad96 Mon Sep 17 00:00:00 2001
From: Carl George <carl@george.computer>
Date: Sep 21 2023 20:32:45 +0000
Subject: Fix formatting in the "Requiring Base Package" section


This section has some incorrect formatting and duplicate phrasing.

---

diff --git a/guidelines/modules/ROOT/pages/index.adoc b/guidelines/modules/ROOT/pages/index.adoc
index 3638c6a..cc030c2 100644
--- a/guidelines/modules/ROOT/pages/index.adoc
+++ b/guidelines/modules/ROOT/pages/index.adoc
@@ -1422,14 +1422,19 @@ not installed in a user runtime, e.g. gcc or gdb.
 
 Subpackages are often extensions for their base package
 and in that case they should require their base package.
-It is almost always better to over specify the version,
-so it is best practice to just use a fully versioned dependency:
-Requires: %\{name}%\{?_isa} = %\{version}-%\{release}.
+When a subpackage requires the base package,
+it *MUST* do so using a fully versioned arch-specific
+(for non-noarch packages) dependency:
+
+[source, rpm-spec]
+----
+Requires: %{name}%{?_isa} = %{version}-%{release}
+----
+
 Devel packages are an example of a package
 that must require their base packages using a fully versioned dependency.
 -libs subpackages which only contain shared libraries
-do not normally need to explicitly depend on
-%\{name}%\{?_isa} = %\{version}-%\{release},
+do not normally need to explicitly depend on their base packages
 as they usually do not need the base package to be functional libraries.
 
 If you end up in a situation where the main package depends on the subpackage
@@ -1437,15 +1442,6 @@ and the subpackage on the main package
 you should think carefully
 about why you don't have everything in the main package.
 
-When a subpackage requires the base package,
-it must do so using a fully versioned arch-specific
-(for non-noarch packages) dependency:
-
-[source, rpm-spec]
-----
-Requires: %{name}%{?_isa} = %{version}-%{release}
-----
-
 == Shared Libraries
 
 Whenever possible (and feasible),