fix examples

[developers-reference.git] / developers-reference.sgml

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 675097fb6405008e5e2c8951ca5884a061b034af..9f7759a1b2b2f247f3c2ca9795553b7bede3ef9f 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!ENTITY % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!ENTITY cvs-rev "$Revision: 1.238 $">
+  <!ENTITY cvs-rev "$Revision: 1.240 $">
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
@@ -3166,12 +3166,12 @@ has in testing.
        <p>
 Consider this example:
        <p>
-       <tt>
-       foo      | alpha | arm 
+       <example>
+foo      | alpha | arm 
 ---------+-------+----
 testing  |   1   |  -
 unstable |   1   |  2
-</tt>
+</example>
        <p>
 The package is out of date on alpha in unstable, and will not go to
 testing. And removing foo from testing would not help at all, the package
@@ -3179,12 +3179,12 @@ is still out of date on alpha, and will not propagate to testing.
        <p>
 However, if ftp-master removes a package in unstable (here on arm):
        <p>
-       <tt>
+       <example>
 foo      | alpha | arm | hurd-i386
 ---------+-------+-----+----------
 testing  |   1   |  1  |    -
 unstable |   2   |  -  |    1
-       </tt>
+       </example>
        <p>
 In this case, the package is up to date on all release architectures in
 unstable (and the extra hurd-i386 doesn't matter, as it's not a release
@@ -3213,12 +3213,12 @@ depends on the new version of package b, and vice versa.
        <p>
 An example of this is:
        <p>
-       <tt>
+       <example>
   | testing         |  unstable
 --+-----------------+------------
 a | 1; depends: b=1 |  2; depends: b=2
 b | 1; depends: a=1 |  2; depends: a=2
-       </tt>
+       </example>
        <p>
 Package a is not considered for update, and package b also not.
        <p>