From a36d3601c61d548db8a5b9c110dbf85405ba3443 Mon Sep 17 00:00:00 2001
From: aph <aph@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Tue, 7 May 2002 03:10:20 +0000
Subject: [PATCH] spell check and some awkward grammar

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@1663 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 debian/changelog          |  1 +
 developers-reference.sgml | 42 +++++++++++++++++++--------------------
 2 files changed, 22 insertions(+), 21 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 2759a34..ef4857a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -38,6 +38,7 @@ developers-reference (3.0) unstable; urgency=low
     - change some literal quotes to &lsquo;, &rdquo;, etc.
     - update copyright date
     - some simplifications on the TeX suffix rule
+    - spell check
 
   * Raphael Hertzog:
     - changed -e by -m in the dpkg-buildpackage command line example.
diff --git a/developers-reference.sgml b/developers-reference.sgml
index 061fe12..6a8ecb2 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.94 $">
+  <!entity cvs-rev "$Revision: 1.95 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -101,7 +101,7 @@ generally agreed-upon best practices.  Thus, it is what is called a
 So, you've read all the documentation, you've gone through the <url
 id="&url-newmaint-guide;" name="Debian New Maintainers' Guide">,
 understand what everything in the <package>hello</package> example
-package is for, and you're about to Debianize your favourite piece of
+package is for, and you're about to Debianize your favorite piece of
 software.  How do you actually become a Debian developer so that your
 work can be incorporated into the Project?
 	<p>
@@ -259,8 +259,8 @@ In addition, if you have some packages ready for inclusion in Debian,
 but are waiting for your new maintainer application to go through, you
 might be able find a sponsor to upload your package for you.  Sponsors
 are people who are official Debian maintainers, and who are willing to
-criticize and upload your packages for you.  Sponsorees can request a
-sponsors at <url id="&url-sponsors;">.
+criticize and upload your packages for you.  Those who are seeking a
+sponsor can request one at <url id="&url-sponsors;">.
 	<p>
 If you wish to be a mentor and/or sponsor, more information is
 available in <ref id="newmaint">.
@@ -292,7 +292,7 @@ Read the documentation that comes with your software; read the <url
 id="&url-pgp-faq;" name="PGP FAQ">.
 	<p>
 If you add signatures to your public key, or add user identities, you
-can update the debian keyring by sending your key to the key server at
+can update the debian key ring by sending your key to the key server at
 <tt>&keyserver-host;</tt>.  If you need to add a completely new key,
 or remove an old key, send mail to &email-debian-keyring;.  The same
 key extraction routines discussed in <ref id="registering"> apply.
@@ -313,7 +313,7 @@ work for Debian and they can't be reached by email if any problem occurs.
 The other developers need to know that you're on vacation so that they'll
 do whatever is needed when such a problem occurs. Usually this means that
 other developers are allowed to NMU (see <ref id="nmu">) your package if a
-big problem (release critical bugs, security update, ...) occurs while
+big problem (release critical bugs, security update, etc.) occurs while
 you're on vacation.
 	<p>
 In order to inform the other developers, there's two things that you should do.
@@ -342,7 +342,7 @@ submit patches to fix upstream bugs, and you should evaluate and
 forward these patches upstream.
         <p>
 If you need to modify the upstream sources in order to build a policy
-conformant package, then you should propose a nice fix to the upstream
+compliant package, then you should propose a nice fix to the upstream
 developers which can be included there, so that you won't have to
 modify the sources of the next upstream version. Whatever changes you
 need, always try not to fork from the upstream sources.
@@ -533,7 +533,7 @@ Debian account should own the CVS root area, and why you need it.
 
       <sect1 id="devel-db">The Developers Database
 	<p>
-The Deverlopers Database, at <url id="&url-debian-db;">, is an LDAP
+The Developers Database, at <url id="&url-debian-db;">, is an LDAP
 directory for managing Debian developer attributes.  You can use this
 resource to search the list of Debian developers.  For information on
 keeping your entry the developer database up-to-date, see <ref
@@ -690,7 +690,7 @@ pages">.
 	<p>
 The sections <em>main</em>, <em>contrib</em>, and <em>non-free</em>
 are split into <em>subsections</em> to simplify the installation
-process and the maintainance of the archive.  Subsections are not
+process and the maintenance of the archive.  Subsections are not
 formally defined, except perhaps the `base' subsection.
 Subsections simply exist to simplify the organization and browsing of
 available packages.  Please check the current Debian distribution to
@@ -1033,7 +1033,7 @@ files, and will not need to be re-uploaded.
 By default, <prgn>dpkg-genchanges</prgn> and
 <prgn>dpkg-buildpackage</prgn> will include the original source tar
 file if and only if the Debian revision part of the source version
-number is 0 or 1, indicating a new upstream version.  This behaviour
+number is 0 or 1, indicating a new upstream version.  This behavior
 may be modified by using <tt>-sa</tt> to always include it or
 <tt>-sd</tt> to always leave it out.
 	  <p>
@@ -1116,7 +1116,7 @@ Extra care should be taken when uploading to <em>stable</em>. Basically, a
 package should only be uploaded to stable if one of the following happens:
 <list>
 	<item>a security problem (e.g. a Debian security advisory)
-	<item>a truely critical functionality problem
+	<item>a truly critical functionality problem
 	<item>the package becomes uninstallable
 	<item>a released architecture lacks the package
 </list>
@@ -1124,7 +1124,7 @@ package should only be uploaded to stable if one of the following happens:
 It is discouraged to change anything else in the package that isn't
 important, because even trivial fixes can cause bugs later on. Uploading
 new upstream versions to fix security problems is deprecated; applying the
-specific patch from the new upstream version to the old one ("backporting"
+specific patch from the new upstream version to the old one ("back-porting"
 the patch) is the right thing to do in most cases.
 	    <p>
 Packages uploaded to <em>stable</em> need to be compiled on systems running
@@ -1156,7 +1156,7 @@ if you use anonymous FTP to upload, place them into
 <ftppath>/pub/UploadQueue/</ftppath>.  Please note that you should transfer
 the changes file last.  Otherwise, your upload may be rejected because the
 archive maintenance software will parse the changes file and see that not
-all files have been uploaded.  If you don't want to bother with transfering
+all files have been uploaded.  If you don't want to bother with transferring
 the changes file last, you can simply copy your files to a temporary
 directory on <tt>ftp-master</tt> and then move them to
 <tt>&us-upload-dir;</tt>.
@@ -1191,7 +1191,7 @@ As discussed above, export controlled software should not be uploaded
 to <tt>ftp-master</tt>.  Instead, upload the package to
 <ftpsite>non-us.debian.org</ftpsite>, placing the files in
 <tt>&non-us-upload-dir;</tt> (both <ref id="dupload"> and <ref
-id="dput"> can be used also, with the right invokation). By default,
+id="dput"> can be used also, with the right invocation). By default,
 you can use the same account/password that works on
 <tt>ftp-master</tt>.  If you use anonymous FTP to upload, place the
 files into <ftppath>/pub/UploadQueue/</ftppath>.
@@ -1372,7 +1372,7 @@ official package maintainer to make a release of a package.  This is
 called a non-maintainer upload, or NMU.
        <p>
 Debian porters, who compile packages for different architectures,
-occasionnaly do binary-only NMUs as part of their porting activity
+occasionally do binary-only NMUs as part of their porting activity
 (see <ref id="porting">).  Another reason why NMUs are done is when a
 Debian developers needs to fix another developers' packages in order to
 address serious security problems or crippling bugs, especially during
@@ -1711,7 +1711,7 @@ includes <file>debian/changelog</file>.
 The way to invoke <prgn>dpkg-buildpackage</prgn> is as
 <tt>dpkg-buildpackage -B -m<var>porter-email</var></tt>.  Of course,
 set <var>porter-email</var> to your email address.  This will do a
-binary-only build of only the architecture-dependant portions of the
+binary-only build of only the architecture-dependent portions of the
 package, using the `binary-arch' target in <file>debian/rules</file>.
 
 	<sect2 id="binary-only-nmu">
@@ -1880,7 +1880,7 @@ the ftpmasters in order to understand what happened.
 If, on the other hand, you need to change the <em>subsection</em> of
 one of your packages (e.g., ``devel'', ``admin''), the procedure is
 slightly different.  Correct the subsection as found in the control
-file of the package, and reupload that.  Also, you'll need to get the
+file of the package, and re-upload that.  Also, you'll need to get the
 override file updated, as described in <ref id="override-file">.
 
 
@@ -2074,7 +2074,7 @@ acme-cannon (3.1415) unstable; urgency=low
   * Frobbed with options (closes: Bug#98339)
   * Added safety to prevent operator dismemberment, closes: bug#98765,
     bug#98713, #98714.
-  * Added manpage. Closes: #98725.
+  * Added man page. Closes: #98725.
 </example>
 
 Technically speaking, the following Perl regular expression is what is
@@ -2282,7 +2282,7 @@ id="upload-checking"> and <ref id="lintian-reports">.
         <p>
 <package>debconf</package> provides a consistent interface to
 configuring packages interactively.  It is user interface
-independant, allowing end-users to configure packages with a
+independent, allowing end-users to configure packages with a
 text-only interface, an HTML interface, or a dialog interface.  New
 interfaces can be added modularly.
         <p>
@@ -2373,7 +2373,7 @@ a version control system.
       <sect id="dupload">
 	<heading><package>dupload</package>
 	<p>
-<package>dupload</package> is a package and a script to automagically
+<package>dupload</package> is a package and a script to automatically
 upload Debian packages to the Debian archive, to log the upload, and
 to send mail about the upload of a package.  You can configure it for
 new upload locations or methods.
@@ -2404,7 +2404,7 @@ user: <tt>dpkg-buildpackage -rfakeroot</tt>.
 	<heading><package>debootstrap</package>
 	<p>
 The <package>debootstrap</package> package and script allows you to
-"bootstrap" a Debian base system into any part of your filesystem.
+"bootstrap" a Debian base system into any part of your file-system.
 By "base system", we mean the bare minimum of packages required to
 operate and install the rest of the system.
 	<p>
-- 
2.30.2