From b4c0f4c44a1c5482d595653e7da4e0b2e73d9f59 Mon Sep 17 00:00:00 2001
From: aph <aph@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Thu, 1 Oct 1998 07:44:38 +0000
Subject: [PATCH] spell check

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index bc8d66b..276f811 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -178,7 +178,7 @@ tampering.  You can do it by executing `<tt>pgp -ks
 If your PGP key isn't on public PGP key servers such as
 <tt>pgp.net</tt>, please read the documentation available locally
 <tt>/usr/doc/pgp/keyserv.doc</tt>.  That document contains
-instructions on how to put your key on the public keyservers.
+instructions on how to put your key on the public key servers.
 	<p>
 Due to export restrictions by the United States government some Debian
 packages, including PGP, have been moved to an ftp site outside of the
@@ -189,7 +189,7 @@ United States. You can find the current locations of those packages on
 Some countries restrict the use of cryptographic software by their
 citizens.  This need not impede one's activities as a Debian package
 maintainer however, as it may be perfectly legal to use cryptographic
-products for authenication, rather than encryption purposes (as is
+products for authentication, rather than encryption purposes (as is
 the case in France).  The Debian Project does not require the use of
 cryptography <em/qua/ cryptography in any manner.  If you live in a
 country where use of cryptography even for authentication is forbidden
@@ -522,7 +522,7 @@ in the description.  However, if there is a chance that the software
 could do grave damage to a system, it might be better to put it into
 <em/experimental/.
 	  <p>
-For instance, an experimental encrypted filesystem should probably go
+For instance, an experimental encrypted file system should probably go
 into experimental.  A new, beta, version of some software which uses
 completely different configuration might go into experimental at the
 maintainer's discretion.  New software which isn't likely to damage
@@ -787,7 +787,7 @@ To upload a package to the <em/non-us/ server you just have to
 transfer the files via anonymous ftp to <url
 id="ftp://non-us.debian.org/pub/debian-non-US/Incoming">.  Note, that
 the <tt>.changes</tt> file must have a valid PGP signature from one of
-the keys of the developers keyring.
+the keys of the developers key-ring.
 
 
       <sect>Announcing package uploads
@@ -808,7 +808,7 @@ If a package is released with <tt/Distribution:/ set to <tt/unstable/,
 should be posted to <email/debian-devel-changes@lists.debian.org/
 instead.
 	<p>
-On occassion, it is necessary to upload a package to both the <tt/stable/
+On occasion, it is necessary to upload a package to both the <tt/stable/
 and <tt/unstable/ distributions; this is done by putting both distributions
 in the <tt/Distribution:/ line.  In such a case the upload announcement
 should go to both of the above mailing lists.
@@ -884,7 +884,7 @@ the fixed bugs explaining that they have been fixed.  Using
 set the severity of the bugs fixed in the NMU to "fixed".  This
 ensures that everyone knows that the bug was fixed in an NMU; however
 the bug is left open until the changes in the NMU are incorporated
-"officially" into the package by the offical package maintainer.
+"officially" into the package by the official package maintainer.
 	<p>
 The normal maintainer should do at least one of the following:
 	  <list compact>
@@ -954,7 +954,7 @@ details on what you did, since it might be a <prgn/dinstall/ bug.
       <sect>Removing packages
 	<p>
 If for some reason you want to completely remove a package (say, if it
-is an old compatability library which is not longer required), you
+is an old compatibility library which is not longer required), you
 need to file a bug against <prgn/ftp.debian.org/ asking that the
 package be removed.  Make sure you indicate which distribution the
 package should be removed from.
@@ -1062,7 +1062,7 @@ free their time for critical tasks.
       <p>
 Some people prefer to use high-level package maintenance tools and
 some do not.  Debian is officially agnostic on this issue, other than
-making the attempt to accomodate the reasonable wishes of developers.
+making the attempt to accommodate the reasonable wishes of developers.
 Therefore, this section is not meant to stipulate to anyone which
 tools they should use or how they should go about with their duties of
 maintainership.  Nor is it meant to endorse any particular tool to the
-- 
2.30.2