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

[developers-reference.git] / pkgs.dbk

diff --git a/pkgs.dbk b/pkgs.dbk
index 86d9273e90783fe8d7f407cdbd262d614e105ba6..d7273299c1972a79dae2bbf3724bf1022a2ff10d 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -55,7 +55,7 @@ the rejection email in case you are already re-uploading.
 </para>
 <para>
 When closing security bugs include CVE numbers as well as the
-<literal>Closes: #<replaceable>nnnnn</replaceable></literal>
+<literal>Closes: #<replaceable>nnnnn</replaceable></literal>.  
 This is useful for the security team to track vulnerabilities.  If an upload is
 made to fix the bug before the advisory ID is known, it is encouraged to modify
 the historical changelog entry with the next upload.  Even in this case, please
@@ -174,7 +174,7 @@ output a very verbose description of the problem.
 </para>
 <para>
 Normally, a package should <emphasis>not</emphasis> be uploaded if it causes
-lintian to emit errors (they will start with <literal>E</literal>).
+<command>lintian</command> to emit errors (they will start with <literal>E</literal>).
 </para>
 <para>
 For more information on <command>lintian</command>, see <xref
@@ -862,7 +862,7 @@ The nature of the fix, if any is available (patches are especially helpful)
 <listitem>
 <para>
 Any fixed packages that you have prepared yourself (send only the
-<literal>.diff.gz</literal> and <literal>.dsc</literal> files and read <xref
+<filename>.diff.gz</filename> and <filename>.dsc</filename> files and read <xref
 linkend="bug-security-building"/> first)
 </para>
 </listitem>
@@ -2294,7 +2294,7 @@ In any case, it is a bad idea to automatically put all team members in the
 a false sense of good maintenance. For the same reason, team members do
 not need to add themselves to the <literal>Uploaders</literal> field just because they are
 uploading the package once, they can do a “Team upload” (see <xref
-linkend="nmu-team-upload"/>). Conversely, it it a bad idea to keep a
+linkend="nmu-team-upload"/>). Conversely, it is a bad idea to keep a
 package with only the mailing list address as a <literal>Maintainer</literal> and no
 <literal>Uploaders</literal>.
 </para>