Update changelog for NMU

[developers-reference.git] / resources.dbk

diff --git a/resources.dbk b/resources.dbk
index c4ab2eb2184254fc55dad257b5c657b790fcca25..8b7dbed4d37aa5458ace161631ed8e2ab83bf0cd 100644 (file)
--- a/resources.dbk
+++ b/resources.dbk
@@ -873,7 +873,7 @@ Once the package is accepted, the system sends a confirmation mail to the
 maintainer and closes all the bugs marked as fixed by the upload, and the
 auto-builders may start recompiling it.  The package is now publicly accessible
 at <ulink url="&url-incoming;"></ulink> until it is really
-installed in the Debian archive.  This happens only once a day (and is also
+installed in the Debian archive.  This happens four times a day (and is also
 called the `dinstall run' for historical reasons); the package is then removed
 from incoming and installed in the pool along with all the other packages.
 Once all the other updates (generating new <filename>Packages</filename> and
@@ -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>