(fr) Proofread [ Jean-Paul Guillonneau ] <4D6FEE65.5060800@tilapin.org>

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

diff --git a/new-maintainer.dbk b/new-maintainer.dbk
index 5ff7cccd860b5654b05e9d2173c575888f5690b6..dc514d0e37170d7ba0865bd952882655a80e3c02 100644 (file)
--- a/new-maintainer.dbk
+++ b/new-maintainer.dbk
@@ -21,7 +21,7 @@ already.  Send the word <literal>subscribe</literal> in the
 <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
 <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"/> .
+available mailing lists can be found in <xref linkend="mailing-lists"/>.

 &email-debian-devel-announce; is another list which is
 mandatory for anyone who wishes to follow Debian's development.
 </para>
 &email-debian-devel-announce; is another list which is
 mandatory for anyone who wishes to follow Debian's development.
 </para>


@@ -34,7 +34,7 @@ something to avoid duplicated effort.
 Another good list to subscribe to is &email-debian-mentors;.
 See <xref linkend="mentors"/> for details.  The IRC channel
 <literal>#debian</literal> can also be helpful; see <xref
 Another good list to subscribe to is &email-debian-mentors;.
 See <xref linkend="mentors"/> for details.  The IRC channel
 <literal>#debian</literal> can also be helpful; see <xref

-linkend="irc-channels"/> .
+linkend="irc-channels"/>.

 </para>
 <para>
 When you know how you want to contribute to &debian-formal;,
 </para>
 <para>
 When you know how you want to contribute to &debian-formal;,


@@ -87,7 +87,7 @@ url="&url-mentors;"></ulink> first.
 </para>
 <para>
 If you wish to be a mentor and/or sponsor, more information is available in
 </para>
 <para>
 If you wish to be a mentor and/or sponsor, more information is available in

-<xref linkend="newmaint"/> .
+<xref linkend="newmaint"/>.

 </para>
 </section>
 
 </para>
 </section>
 


@@ -147,7 +147,7 @@ human error than to software failure or high-powered spy techniques.  See <xref
 linkend="key-maint"/> for more information on maintaining your public key.
 </para>
 <para>
 linkend="key-maint"/> for more information on maintaining your public key.
 </para>
 <para>

-Debian uses the <command>GNU Privacy Guard</command> (package <systemitem
+Debian uses the <literal>GNU Privacy Guard</literal> (package <systemitem

 role="package">gnupg</systemitem> version 1 or better) as its baseline
 standard.  You can use some other implementation of OpenPGP as well.  Note that
 OpenPGP is an open standard based on <ulink
 role="package">gnupg</systemitem> version 1 or better) as its baseline
 standard.  You can use some other implementation of OpenPGP as well.  Note that
 OpenPGP is an open standard based on <ulink


@@ -156,7 +156,7 @@ url="&url-rfc2440;">RFC 2440</ulink>.
 <para>
 You need a version 4 key for use in Debian Development.  Your key length must
 be at least 1024 bits; there is no reason to use a smaller key, and doing so
 <para>
 You need a version 4 key for use in Debian Development.  Your key length must
 be at least 1024 bits; there is no reason to use a smaller key, and doing so

-would be much less secure.  <footnote><para> Version 4 keys are keys conforming
+would be much less secure.<footnote><para> Version 4 keys are keys conforming

 to the OpenPGP standard as defined in RFC 2440.  Version 4 is the key type that
 has always been created when using GnuPG.  PGP versions since 5.x also could
 create v4 keys, the other choice having beein pgp 2.6.x compatible v3 keys
 to the OpenPGP standard as defined in RFC 2440.  Version 4 is the key type that
 has always been created when using GnuPG.  PGP versions since 5.x also could
 create v4 keys, the other choice having beein pgp 2.6.x compatible v3 keys