Update URL explaining the "Debian Maintainer" status.

[developers-reference.git] / new-maintainer.dbk

diff --git a/new-maintainer.dbk b/new-maintainer.dbk
index 3f71082311098a80cb946a5d2410d4e6b3dc61eb..5ff7cccd860b5654b05e9d2173c575888f5690b6 100644 (file)
--- a/new-maintainer.dbk
+++ b/new-maintainer.dbk
@@ -18,7 +18,7 @@ developer so that your work can be incorporated into the Project?
 <para>
 Firstly, subscribe to &email-debian-devel; if you haven't
 already.  Send the word <literal>subscribe</literal> in the
-<emphasis>Subject</emphasis> of an email to
+<literal>Subject</literal> of an email to
 &email-debian-devel-req;.  In case of problems, contact the
 list administrator at &email-listmaster;.  More information on
 available mailing lists can be found in <xref linkend="mailing-lists"/> .
@@ -167,7 +167,7 @@ DSA (sign only), (5) RSA (sign only).  If you don't have any special
 requirements just pick the default.  </para> <para> The easiest way to tell
 whether an existing key is a v4 key or a v3 (or v2) key is to look at the
 fingerprint: Fingerprints of version 4 keys are the SHA-1 hash of some key
-matieral, so they are 40 hex digits, usually grouped in blocks of 4.
+material, so they are 40 hex digits, usually grouped in blocks of 4.
 Fingerprints of older key format versions used MD5 and are generally shown in
 blocks of 2 hex digits.  For example if your fingerprint looks like
 <literal>5B00 C96D 5D54 AEE1 206B  AF84 DE7A AF6E 94C0 9C7F</literal>
@@ -196,7 +196,7 @@ can make special arrangements.
 </para>
 <para>
 To apply as a new maintainer, you need an existing Debian Developer to support
-your application (an <emphasis>advocate</emphasis>).  After you have
+your application (an <literal>advocate</literal>).  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 have worked over the past months
 has to express their belief that you can contribute to Debian successfully.