From da1c934242582ff391606ad26e68dc93d147d067 Mon Sep 17 00:00:00 2001
From: Russ Allbery <rra@debian.org>
Date: Thu, 3 Jun 2010 22:20:44 -0700
Subject: [PATCH] Move Architecture Wildcards to a subsection

Make Architecture Wildcards a subsection of Architecture specification
strings so that we don't renumber all the subsequent sections (and
because it seems to make slightly more sense).
---
 policy.sgml | 38 +++++++++++++++++++-------------------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/policy.sgml b/policy.sgml
index f246c13..0c47a9f 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -8016,27 +8016,27 @@ done
 	  <tt><var>arch</var>-unknown-linux</tt>, since the
 	  <tt>unknown</tt> does not look very good.
 	</p>
-      </sect>
 
-      <sect id="arch-wildcard-spec">
-        <heading>Architecture Wildcards</heading>
+	<sect1 id="arch-wildcard-spec">
+          <heading>Architecture wildcards</heading>
 
-        <p>
-	  A package may specify an architecture wildcard. Architecture
-	  wildcards are in the format <tt>any</tt> (which matches every
-	  architecture), <tt><var>os</var></tt>-any, or
-	  any-<tt><var>cpu</var></tt>. <footnote>
-	    Internally, the package system normalizes the GNU triplets and
-	    the Debian arches into Debian arch triplets (which are kind of
-	    inverted GNU triplets), with the first component of the
-	    triplet representing the libc and ABI in use, and then does
-	    matching against those triplets.  However, such triplets are
-	    an internal implementation detail that should not be used by
-	    packages directly.  The libc and ABI portion is handled
-	    internally by the package system based on the <var>os</var>
-	    and <var>cpu</var>.
-          </footnote>
-        </p>
+          <p>
+	    A package may specify an architecture wildcard. Architecture
+	    wildcards are in the format <tt>any</tt> (which matches every
+	    architecture), <tt><var>os</var></tt>-any, or
+	    any-<tt><var>cpu</var></tt>. <footnote>
+	      Internally, the package system normalizes the GNU triplets
+	      and the Debian arches into Debian arch triplets (which are
+	      kind of inverted GNU triplets), with the first component of
+	      the triplet representing the libc and ABI in use, and then
+	      does matching against those triplets.  However, such
+	      triplets are an internal implementation detail that should
+	      not be used by packages directly.  The libc and ABI portion
+	      is handled internally by the package system based on
+	      the <var>os</var> and <var>cpu</var>.
+            </footnote>
+          </p>
+	</sect1>
       </sect>
 
       <sect>
-- 
2.39.5