Miscellaneous corrections

[developers-reference.git] / developers-reference.sgml

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 7ffd5c16c05f8d8e0e29f6ff3e74aed266afbacf..6917d4f99547bad48a20082e21a259b93af70fb9 100644 (file)
--- 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.80 $">
+  <!entity cvs-rev "$Revision: 1.81 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -218,7 +218,7 @@ cryptography <em>qua</em> cryptography in any manner.  If you live in a
 country where use of cryptography even for authentication is forbidden
 then please contact us so we can make special arrangements.
        <p>
-When you are ready to apply, you need an existing Debian maintainer
+To apply as a new maintainer, you need an existing Debian maintainer
 to verify your application (an <em>advocate</em>).  After you have
 contributed to Debian for a while, and you want to apply to become a
 registered developer, an existing developer with whom you
@@ -238,7 +238,7 @@ name="applications status board">.
 For more details, please consult <url id="&url-newmaint;" name="New
 Maintainer's Corner"> at the Debian web site.  Make sure that you
 are familiar with the necessary steps of the New Maintainer process
-before actually applying.  If you are prepared well, you can save
+before actually applying.  If you are well prepared, you can save
 a lot of timer later on.
 
 
@@ -363,14 +363,14 @@ for help on &email-debian-qa; or &email-debian-devel;).
       <p>
 If you notice that a package is lacking maintenance, you should
 make sure the maintainer is active and will continue to work on
-their packages. Try contacting them yourself.
+his packages. Try contacting him yourself.
       <p>
 If you do not get a reply after a few weeks you should collect all 
-useful information about this maintainer. Start by logging in to 
-the <url id="http://db.debian.org" name="Debian Developer's Database">
+useful information about this maintainer. Start by logging into 
+the <url id="&url-debian-db;" name="Debian Developer's Database">
 and doing a full search to check whether the maintainer is on vacation
-and when they were last seen. Collect any important package names
-they maintain and any Release Critical bugs filled against them.
+and when he was last seen. Collect any important package names
+he maintains and any Release Critical bugs filled against them.
       <p>
 Send all this information to &email-debian-qa;, in order to let the 
 QA people do whatever is needed.
@@ -773,7 +773,7 @@ until the distribution is prepared for release, as decided by the
 release manager.  At the end of the last test cycle, the
 <em>testing</em> distribution is renamed to <em>stable</em>,
 overriding the old <em>stable</em> distribution, which is removed at
-that time (although they can be found at <tt>archive-host;</tt>).
+that time (although it can be found at <tt>&archive-host;</tt>).
        <p>
 This development cycle is based on the assumption that the
 <em>unstable</em> distribution becomes <em>stable</em> after passing a
@@ -1941,7 +1941,7 @@ outlining all the open bugs against your packages:
 # ask for weekly reports of bugs in my packages
 &cron-bug-report;
 </example>
-Replace <var>maintainer-address</var> with you official Debian
+Replace <var>address</var> with you official Debian
 maintainer address.
 
       <sect id="submit-bug">Submitting Bugs