use <q> completed

CVS version numbers

danish/devel/testing.wml: 1.19 -> 1.20 
english/devel/testing.wml: 1.21 -> 1.22 
german/devel/testing.wml: 1.27 -> 1.28 
spanish/devel/testing.wml: 1.14 -> 1.15

1 files changed, 16 insertions, 16 deletions

diff --git a/english/devel/testing.wml b/english/devel/testing.wml
index c0e0b11a3f4..a35fcd8e8cf 100644
--- a/english/devel/testing.wml
+++ b/english/devel/testing.wml
@@ -35,11 +35,11 @@ satisfies all of the following criteria:</p>
   <a href="#faq">more information</a>);</li>
 
   <li>All of its dependencies must <em>either</em> be satisfiable by
-  packages already in <q>testing", <em>or</em> be satisfiable by the group
+  packages already in <q>testing</q>, <em>or</em> be satisfiable by the group
   of packages which are going to be installed at the same time;</li>
 
   <li>The operation of installing the package into <q>testing</q> must not break
-  any packages currently in <q>testing". (See below for
+  any packages currently in <q>testing</q>. (See below for
   <a href="#faq">more information</a>.)</li>
 </ol>
 
@@ -47,7 +47,7 @@ satisfies all of the following criteria:</p>
 <q>Valid Candidate</q>.</p>
 
 <p>The update script shows when each package might move from <q>unstable</q> into
-"testing". The output is twofold:</p>
+<q>testing</q>. The output is twofold:</p>
 
 <ul>
   <li>The <a href="http://ftp-master.debian.org/testing/update_excuses.html">\
@@ -55,7 +55,7 @@ satisfies all of the following criteria:</p>
       [<a href="http://ftp-master.debian.org/testing/update_excuses.html.gz">\
       gzipped</a>]:
       list of all candidate package versions and the basic status of their
-      propagation into <q>testing"; this is somewhat shorter and nicer than
+      propagation into <q>testing</q>; this is somewhat shorter and nicer than
   </li>
   <li>The <a href="http://ftp-master.debian.org/testing/update_output.txt">\
       update output</a>
@@ -77,11 +77,11 @@ currently, these are <strong>critical</strong>, <strong>grave</strong> and
 
 <p>Such bugs are presumed to have an impact on the chances that the package
 will be released with the stable release of Debian: in general, if a package
-has open release-critical bugs filed on it, it won't get into <q>testing", and
-consequently won't be released in <q>stable".</p>
+has open release-critical bugs filed on it, it won't get into <q>testing</q>, and
+consequently won't be released in <q>stable</q>.</p>
 
 <p>The <q>testing</q> bug count for a package is considered to be roughly the bug
-count at the last point when the <q>testing</q> version equalled the <q>unstable"
+count at the last point when the <q>testing</q> version equalled the <q>unstable</q>
 version. The bugs tagged <strong><current_release_name></strong> or
 <strong><current_testing_name></strong> will not be counted. Bugs with the
 <strong>sid</strong> tag will be counted, though.</p>
@@ -91,7 +91,7 @@ packages?</q></h3>
 
 <p>The structure of the distribution archives is such that they can only
 contain one version of a package; a package is defined by its name. So, when
-the source package <tt>acmefoo</tt> is installed into <q>testing", along with
+the source package <tt>acmefoo</tt> is installed into <q>testing</q>, along with
 its binary packages <tt>acme-foo-bin</tt>, <tt>acme-bar-bin</tt>,
 <tt>libacme-foo1</tt> and <tt>libacme-foo-dev</tt>, the old version is
 removed.</p>
@@ -110,7 +110,7 @@ declared of the ==, &lt;= or &lt;&lt; varieties.</p>
 this way, all the packages that depended on the old binaries will have to be
 updated to depend on the new binaries instead. Because installing such a
 source package into <q>testing</q> breaks all the packages that depended on it in
-"testing", some care now has to be taken: all the depending packages must be
+<q>testing</q>, some care now has to be taken: all the depending packages must be
 updated and ready to be installed themselves so that they won't be broken,
 and, once everything is ready, manual intervention by the release manager or
 an assistant is normally required.</p>
@@ -120,7 +120,7 @@ contact debian-devel or debian-release for help.</p>
 
 <h3><q>I still don't understand! The <q>testing</q> scripts say that this
 package is a valid candidate, but it still hasn't gone into
-"testing".</q></h3>
+<q>testing</q>.</q></h3>
 
 <p>This tends to happen when in some way, directly or indirectly, installing
 the package will break some other package.</p>
@@ -139,10 +139,10 @@ packages will enter <q>testing</q>.</p>
 textual output</a>
 [<a href="http://ftp-master.debian.org/testing/update_output.txt.gz">gzipped</a>]
 is useful: it gives hints (albeit very terse ones) as to which packages
-break when a valid candidate is added to <q>testing".</p>
+break when a valid candidate is added to <q>testing</q>.</p>
 
 <h3><q>Why is it sometimes hard to get <kbd>Architecture: all</kbd> packages
-into <q>testing"?</q></h3>
+into <q>testing</q>?</q></h3>
 
 <p>If the <kbd>Architecture: all</kbd> package is to be installed, it must
 be possible to satisfy its dependencies on <strong>all</strong>
@@ -205,7 +205,7 @@ it into <q>testing</q> despite not satisfying all of the requirements.</q></h3>
 <h3><q>Can you provide a real, non-trivial example?</q></h3>
 
 <p>Here's one: when the source package <tt>apache</tt> is installed into
-"testing", along with its binary packages <tt>apache</tt>,
+<q>testing</q>, along with its binary packages <tt>apache</tt>,
 <tt>apache-common</tt>, <tt>apache-dev</tt> and <tt>apache-doc</tt>, the
 old version is removed.</p>
 
@@ -260,7 +260,7 @@ things worse.</p>
      * i386: ginac-cint, libginac-dev
 </pre>
 
-<p>This means that if <tt>cln</tt> goes into <q>testing", <tt>ginac-cint</tt>
+<p>This means that if <tt>cln</tt> goes into <q>testing</q>, <tt>ginac-cint</tt>
 and <tt>libginac-dev</tt> become uninstallable in <q>testing</q> on i386.
 Note that the architectures are checked in alphabetical order and only the
 problems on the first architecture with problems are shown &mdash; that's why
@@ -269,7 +269,7 @@ the alpha architecture is shown so often.</p>
 <p>The <q>got</q> line includes the number of problems in <q>testing</q> on the
 different architectures (until the first architecture where a problem is
 found &mdash; see above). The <q>i-45</q> means that if <tt>cln</tt> would go into
-"testing", there would be 45 uninstallable packages on i386. Some of the
+<q>testing</q>, there would be 45 uninstallable packages on i386. Some of the
 entries above and below <tt>cln</tt> show there were 43 uninstallable
 packages in <q>testing</q> on i386 at the time.</p>
 
@@ -279,7 +279,7 @@ is completed, and that 4 packages have been found already that won't be
 planned to be upgraded because they would break dependencies. The <q>(0)</q> is
 irrelevant, you can safely ignore it.</p>
 
-<p>Note that there are several checks of all packages in one <q>testing"
+<p>Note that there are several checks of all packages in one <q>testing</q>
 script run.</p>
 
 <p><i>Jules Bean initially assembled the frequently asked questions and