Update explanation of best practice for closing bugs, seems to

[developers-reference.git] / pkgs.dbk

diff --git a/pkgs.dbk b/pkgs.dbk
index 1e0b29d9593b81ade4d436d9ef8540f87a748780..d96c0ae8ac6c88d7ee3e124928c656ff5b4cc72a 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -735,9 +735,9 @@ several developers working on the same package.
 </listitem>
 <listitem>
 <para>
-Once a corrected package is available in the <literal>unstable</literal>
-distribution, you can close the bug.  This can be done automatically, read
-<xref linkend="upload-bugfix"/> .
+Once a corrected package is available in the archive, the bug should be
+closed indicating the version in which it was fixed. This can be done
+automatically, read <xref linkend="upload-bugfix"/>.
 </para>
 </listitem>
 </orderedlist>
@@ -2281,7 +2281,7 @@ available in <literal>unstable</literal>, but not affecting the version in
 <listitem>
 <para>
 It must be available on all architectures on which it has previously been built
-in <literal>unstable</literal>.  <xref linkend="madison"/> may be of interest
+in <literal>unstable</literal>.  <xref linkend="dak ls"/> may be of interest
 to check that information;
 </para>
 </listitem>