<para>
Be very careful with your private keys. Do not place them on any public
servers or multiuser machines, such as the Debian servers (see <xref
-linkend="server-machines"/> ). Back your keys up; keep a copy offline. Read
+linkend="server-machines"/>). Back your keys up; keep a copy offline. Read
the documentation that comes with your software; read the <ulink
url="&url-pgp-faq;">PGP FAQ</ulink>.
</para>
</para>
<para>
Usually this means that other developers are allowed to NMU (see <xref
-linkend="nmu"/> ) your package if a big problem (release critical bug, security
+linkend="nmu"/>) your package if a big problem (release critical bug, security
update, etc.) occurs while you're on vacation. Sometimes it's nothing as
critical as that, but it's still appropriate to let others know that you're
unavailable.
</para>
<para>
Ideally, you should sign up at the <ulink
-url="&url-newmaint-db;gpg.php">GPG coordination site</ulink> when booking a
+url="&url-gpg-coord;">GPG coordination pages</ulink> when booking a
holiday and check if anyone there is looking for signing. This is especially
important when people go to exotic places where we don't have any developers
yet but where there are people who are interested in applying.
<title>Managing release-critical bugs</title>
<para>
Generally you should deal with bug reports on your packages as described in
-<xref linkend="bug-handling"/> . However, there's a special category of bugs
+<xref linkend="bug-handling"/>. However, there's a special category of bugs
that you need to take care of — the so-called release-critical bugs (RC
bugs). All bug reports that have severity <literal>critical</literal>,
<literal>grave</literal> or <literal>serious</literal> are considered to
<email>debian-qa@&lists-host;</email>, or explain your difficulties and
present a plan to fix them by sending a mail to the bug report. Otherwise,
people from the QA group may want to do a Non-Maintainer Upload (see <xref
-linkend="nmu"/> ) after trying to contact you (they might not wait as long as
+linkend="nmu"/>) after trying to contact you (they might not wait as long as
usual before they do their NMU if they have seen no recent activity from you in
the BTS).
</para>
<orderedlist numeration="arabic">
<listitem>
<para>
-Orphan all your packages, as described in <xref linkend="orphaning"/> .
+Orphan all your packages, as described in <xref linkend="orphaning"/>.
</para>
</listitem>
<listitem>
<listitem>
<para>
Notify the Debian key ring maintainers that you are leaving by opening a ticket
-in Debian RT by sending a mail to keyring@rt.debian.org with the words 'Debian
+in Debian RT by sending a mail to &email-keyring; with the words 'Debian
RT' somewhere in the subject line (case doesn't matter).
</para>
</listitem>