Typos and other nip ticking issues

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@7422 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/developer-duties.dbk b/developer-duties.dbk
index b753160a7004ec3c00d2c515cd947af00ae516dc..f09e3cf09ab1002607f9813a2cd312c55a79f16d 100644 (file)
--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -16,8 +16,7 @@ as well as the address where you get your debian-private subscription if you
 choose to subscribe there.
 </para>
 <para>
-For more information about the database, please see <xref linkend="devel-db"/>
-.
+For more information about the database, please see <xref linkend="devel-db"/>.
 </para>
 </section>
 

diff --git a/pkgs.dbk b/pkgs.dbk
index 86d9273e90783fe8d7f407cdbd262d614e105ba6..2acdf5c40e15d98208bc19c9e8e40cece75da22d 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
@@ -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>

diff --git a/resources.dbk b/resources.dbk
index c4ab2eb2184254fc55dad257b5c657b790fcca25..0c1c75ac1552795ea940a1611efe0fb43326ac0d 100644 (file)
--- a/resources.dbk
+++ b/resources.dbk
@@ -883,10 +883,10 @@ script is called to ask all the primary mirrors to update themselves.
 <para>
 The archive maintenance software will also send the OpenPGP/GnuPG signed
 <filename>.changes</filename> file that you uploaded to the appropriate mailing
-lists.  If a package is released with the <literal>Distribution:</literal> set
+lists.  If a package is released with the <literal>Distribution</literal> set
 to <literal>stable</literal>, the announcement is sent to
 &email-debian-changes;.  If a package is released with
-<literal>Distribution:</literal> set to <literal>unstable</literal> or
+<literal>Distribution</literal> set to <literal>unstable</literal> or
 <literal>experimental</literal>, the announcement will be posted to
 &email-debian-devel-changes; instead.
 </para>

diff --git a/tools.dbk b/tools.dbk
index b7728ca09a657d0ea49ec93ebfacc237f67f9bd5..c2b26a1eb6fb8211f8d57234b55a2662c4bd4d53 100644 (file)
--- a/tools.dbk
+++ b/tools.dbk
@@ -26,7 +26,7 @@ exclusion of a competing tool.
 Most of the descriptions of these packages come from the actual package
 descriptions themselves.  Further information can be found in the package
 documentation itself.  You can also see more info with the command
-<command>apt-cache show <literal>package-name</literal></command>.
+<command>apt-cache show <replaceable>package-name</replaceable></command>.
 </para>
 <section id="tools-core">
 <title>Core tools</title>