From 24e10d87f2bbdefd7bc3c870de6948418e10cfd4 Mon Sep 17 00:00:00 2001
From: Manoj Srivastava <srivasta@debian.org>
Date: Thu, 16 Jun 2005 05:37:32 +0000
Subject: [PATCH] explicate that appendices aren't necessarily normative

Author: joy
Date: 2003/02/22 15:55:07
explicate that appendices aren't necessarily normative

git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-191
---
 policy.sgml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/policy.sgml b/policy.sgml
index f8e3b7d..549a928 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -66,7 +66,6 @@
 	  distribution.
 	</p>
 
-
 	<p>
 	  This manual also describes Debian policy as it relates to
 	  creating Debian packages. It is not a tutorial on how to build
@@ -116,7 +115,13 @@
 	</p>
 
 	<p>
-	  In this manual, the words <em>must</em>, <em>should</em> and
+	  The appendices to this manual are not necessarily normative,
+	  either. Please see <ref id="pkg-scope"> for more information.
+	</p>
+
+	<p>
+	  In the normative part of this manual,
+	  the words <em>must</em>, <em>should</em> and
 	  <em>may</em>, and the adjectives <em>required</em>,
 	  <em>recommended</em> and <em>optional</em>, are used to
 	  distinguish the significance of the various guidelines in
-- 
2.39.5