From 24e0610fe07c8bcfad76aa090cf3a3461c0d3d2d Mon Sep 17 00:00:00 2001
From: joy <joy@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Sat, 22 Feb 2003 22:16:10 +0000
Subject: [PATCH] another typo fix and a clarification of my sentence

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2181 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 developers-reference.sgml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/developers-reference.sgml b/developers-reference.sgml
index c2f263c..3c41cbe 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.185 $">
+  <!entity cvs-rev "$Revision: 1.186 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -3553,9 +3553,9 @@ this data is negligible compared to the size of the rest of the
 package, it's probably best to keep it all in a single package.
           <p>
 However, if the size of the data is considerable, consider splitting
-it out into a separate, architecture-independent package.
-("_all.deb").  By doing this, you avoid needless duplication of the
-same data into eleven or more .debs per each architecture.  While this
+it out into a separate, architecture-independent package ("_all.deb").
+By doing this, you avoid needless duplication of the same data into
+eleven or more .debs, one per each architecture.  While this
 adds some extra overhead into the <file>Packages</file> files, it
 saves a lot of disk space on Debian mirrors.  Separating out
 architecture-independent data also reduces processing time of
-- 
2.30.2