Small typo fixes and clarifications/rewordings suggested by Karl Goetz. Closes: ...

[developers-reference.git] / pkgs.dbk

diff --git a/pkgs.dbk b/pkgs.dbk
index 40ace63772f27819c5a533f4a79e5800c5b3caf3..f40e7f3d873b5a7b04cb75db6106ebac6590711c 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -37,15 +37,15 @@ Please send a copy to &email-debian-devel; by using the X-Debbugs-CC
 header (don't use CC:, because that way the message's subject won't
 indicate the bug number). If you are packaging so many new packages (>10)
 that notifying the mailing list in seperate messages is too disruptive,
-do send a summary after filing the bugs to the debian-devel list instead.
+send a summary after filing the bugs to the debian-devel list instead.
 This will inform the other developers about upcoming packages and will
 allow a review of your description and package name.
 </para>
 <para>
-Please include a <literal>Closes:
-bug#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the
-new package in order for the bug report to be automatically closed once the new
-package is installed in the archive (see <xref linkend="upload-bugfix"/> ).
+Please include a <literal>Closes: #<replaceable>nnnnn</replaceable></literal>
+entry in the changelog of the new package in order for the bug report to
+be automatically closed once the new package is installed in the archive
+(see <xref linkend="upload-bugfix"/>).
 </para>
 <para>
 If you think your package needs some explanations for the administrators of the