X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=developers-reference.sgml;h=0b0de53fac9614ff1b7301e56bd6819a400ff0e0;hp=af972e7fc7ae67b7b5508c071192ec50b7277b37;hb=d8f60cb36cd4fd22d02851d4465749f4233391da;hpb=eb93665f453f3dbb7e8813a722cc2c3f7099a578

diff --git a/developers-reference.sgml b/developers-reference.sgml
index af972e7..0b0de53 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -5,7 +5,7 @@
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.87 $">
+  <!entity cvs-rev "$Revision: 1.88 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -928,7 +928,7 @@ better feel of what is going on, and what is new, in the project.
 Changes that you make to the package need to be recorded in the
 <file>debian/changelog</file>.  These changes should provide a concise
 description of what was changed, why (if it's in doubt), and note if
-any bugs were closed.  They also record when the packages was
+any bugs were closed.  They also record when the package was
 completed.  This file will be installed in
 <file>/usr/share/doc/<var>package</var>/changelog.Debian.gz</file>, or
 <file>/usr/share/doc/<var>package</var>/changelog.gz</file> for native
@@ -937,14 +937,14 @@ packages.
 The <file>debian/changelog</file> file conform to a certain structure,
 with a number of different fields.  One field of note, the
 <em>distribution</em>, is described in <ref id="upload-dist">.  More
-information about the structure structure of this file can be found in
+information about the structure of this file can be found in
 the Debian Policy section titled "<file>debian/changelog</file>".
 	  <p>
 Changelog entries can be used to automatically close Debian bugs when
 the package is installed into the archive.  See <ref
 id="upload-bugfix">.
 	  <p>
-It is conventional that the changelog entry notating that the package
+It is conventional that the changelog entry notating of a package that
 contains a new upstream version of the software looks like this:
 <example>
   * new upstream version
@@ -1149,7 +1149,7 @@ directory on <tt>ftp-master</tt> and then move them to
           <p>
 <em>Note:</em> Do not upload to <tt>ftp-master</tt> packages
 containing software that is patent-restricted by the United States
-government, any cryptographic packages which belong in
+government, nor any cryptographic packages which belong to
 <em>contrib</em> or <em>non-free</em>.  If you can't upload it to
 <tt>ftp-master</tt>, then neither can you upload it to the overseas
 upload queues on <tt>chiark</tt> or <tt>erlangen</tt>.  Uploads of
@@ -1162,7 +1162,7 @@ You may also find the Debian packages <package>dupload</package> or
 <package>dput</package> useful
 when uploading packages.  These handy program are distributed with
 defaults for uploading via <prgn>ftp</prgn> to <tt>ftp-master</tt>,
-<tt>chiark</tt>, and <tt>erlangen</tt>.  It can also be configured to
+<tt>chiark</tt>, and <tt>erlangen</tt>. They can also be configured to
 use <prgn>ssh</prgn> or <prgn>rsync</prgn>.  See <manref name="dupload"
 section="1">, <manref name="dupload" section="5"> and <manref name="dput"
 section="1"> for more information.
@@ -1194,8 +1194,8 @@ restriction has been waived for software which is already available
 outside the U.S.  Therefore, any cryptographic software which belongs
 in the <em>main</em> section of the Debian archive and does not depend
 on any package outside of <em>main</em> (e.g., does not depend on
-anything in <em>non-US/main</em>) can be uploaded to ftp-master or its
-queues, described above.
+anything in <em>non-US/main</em>) can be uploaded to <tt>ftp-master</tt>
+or its queues, described above.
 	  <p>
 Debian policy does not prevent upload to non-US by U.S. residents or
 citizens, but care should be taken in doing so. It is recommended that
@@ -2235,7 +2235,7 @@ favor of <package>debhelper</package>.  However, it's not a bug to use
 	<p>
 <package>yada</package> is another packaging helper tool.  It uses a
 <file>debian/packages</file> file to auto-generate
-<file>debian/rules</file> other necessary files in the
+<file>debian/rules</file> and other necessary files in the
 <file>debian/</file> subdirectory.
 	<p>
 Note that <package>yada</package> is called "essentially unmaintained"
@@ -2306,7 +2306,7 @@ The <package>debootstrap</package> package and script allows you to
 By "base system", we mean the bare minimum of packages required to
 operate and install the rest of the system.
 	<p>
-Having a system link this can be useful in many ways. For instance,
+Having a system like this can be useful in many ways. For instance,
 you can <prgn>chroot</prgn> into it if you want to test your build
 depends.  Or, you can test how your package behaves when installed
 into a bare base system.