Suddenly realised none of the

  <informalexample>
    <screen>
      ...
    </screen>
  </informalexample>

need the <informalexample> element. So remove it. Simple search and
replace does the trick.

21 files changed, 556 insertions, 557 deletions

diff --git a/en/handbook/advanced-networking/chapter.sgml b/en/handbook/advanced-networking/chapter.sgml
index 4f00275b26..1a2a36d58e 100644
--- a/en/handbook/advanced-networking/chapter.sgml
+++ b/en/handbook/advanced-networking/chapter.sgml
@@ -28,7 +28,7 @@
 	    following example which is the output of the command
 	    <command>netstat -r</command>:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>Destination      Gateway            Flags     Refs     Use     Netif Expire
 
 default          outside-gw         UGSc       37      418      ppp0
@@ -40,7 +40,7 @@ host1            0:e0:a8:37:8:1e    UHLW        3     4601       lo0
 host2            0:e0:a8:37:8:1e    UHLW        0        5       lo0 =>
 host2.foobar.com link#1             UC          0        0
 224              link#1             UC          0        0</screen>
-	  </informalexample>
+	  
 	  
 	  <para>The first two lines specify the default route (which we will
 	    cover in the next section) and the <hostid>localhost</hostid> route.</para>
@@ -382,9 +382,9 @@ fastws:/sharedfs /project nfs rw,-r=1024 0 0</programlisting>
 
 	  <para>As a manual mount command on <hostid>freebox</hostid>:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>mount -t nfs -o -r=1024 fastws:/sharedfs /project</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>Examples for the FreeBSD system as the server: in
 	  <filename>/etc/fstab</filename> on <hostid>fastws</hostid>:</para>
@@ -394,9 +394,9 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
 
 	  <para>As a manual mount command on <hostid>fastws</hostid>:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>mount -t nfs -o -w=1024 freebox:/sharedfs /project</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>Nearly any 16-bit Ethernet adapter will allow operation without
 	  the above restrictions on the read or write size.</para>
@@ -617,18 +617,18 @@ hostname myclient.mydomain</programlisting>
 		<filename>/swapfs/swap.<replaceable>X.X.X.X</replaceable></filename> where
 		  <replaceable>X.X.X.X</replaceable> is the client's IP addr, eg:</para>
 
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>dd if=/dev/zero of=/swapfs/swap.192.1.2.4 bs=1k count=20000</userinput></screen>
-		  </informalexample>
+		  
 
 	      <para>Also, the client's swap space might
 		  contain sensitive information once swapping starts, so make
 		  sure to restrict read and write access to this file to
 		  prevent unauthorized access:</para>
 	      
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>chmod 0600 /swapfs/swap.192.1.2.4</userinput></screen>
-		  </informalexample>
+		  
 	      </step>
 	      
 	      <step>
diff --git a/en/handbook/backups/chapter.sgml b/en/handbook/backups/chapter.sgml
index f7c05d2731..d0bc0b1d65 100644
--- a/en/handbook/backups/chapter.sgml
+++ b/en/handbook/backups/chapter.sgml
@@ -164,10 +164,10 @@
 completely blank tape, the operation will fail. The console
 messages should be similar to:</para>
       
-<informalexample>
+
 	<screen>st0(ncr1:4:0): NOT READY asc:4,1
 st0(ncr1:4:0):  Logical unit is in process of becoming ready</screen>
-      </informalexample>
+      
 
       <para>The tape does not contain an Identifier Block (block number 0).
 	All QIC tape drives since the adoption of QIC-525 standard write an
diff --git a/en/handbook/basics/chapter.sgml b/en/handbook/basics/chapter.sgml
index 761f1146f4..4fd4f4b9fd 100644
--- a/en/handbook/basics/chapter.sgml
+++ b/en/handbook/basics/chapter.sgml
@@ -12,17 +12,17 @@
 	  <command>man</command>
 	  command. Use of the <command>man</command> command is simple:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>man <replaceable>command</replaceable></userinput>
 	    </screen>
-	  </informalexample>
+	  
 
 	<para><replaceable>command</replaceable> is
 	  the name of the command you wish to learn about. For example, to
 	  learn more about <command>ls</command> command type:</para>
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>man ls</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>The online manual is divided up into numbered sections:</para>
 	
@@ -69,9 +69,9 @@
 	  this case, you can tell the <command>man</command> command which one you want by
 	  specifying the section:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>man 1 chmod</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>This will display the manual page for the user
 	  command <command>chmod</command>. References to a
@@ -87,9 +87,9 @@
 	  command <emphasis>descriptions</emphasis> by using the
 	  <option>-k</option> switch:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>man -k mail</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>With this command you will be presented with a
 	  list of commands that have the keyword &ldquo;mail&rdquo; in their descriptions.
@@ -100,15 +100,15 @@
 	  <filename>/usr/bin</filename> but do not even have the faintest idea
 	  what most of them actually do? Simply do a
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>cd /usr/bin; man -f *</userinput></screen>
-	  </informalexample>
+	  
 
 	  or
 
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>cd /usr/bin; whatis *</userinput></screen>
-	  </informalexample> which does the same thing.</para>
+	   which does the same thing.</para>
 	
       </sect1>
       
@@ -124,9 +124,9 @@
 	
 	<para>To use the <citerefentry><refentrytitle>info</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, simply type:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>info</userinput></screen>
-	  </informalexample>
+	  
 
 	  <para>For a brief introduction, type <userinput>h</userinput>. For a quick
 	  command reference, type <userinput>?</userinput>.</para>
diff --git a/en/handbook/contrib/chapter.sgml b/en/handbook/contrib/chapter.sgml
index bd3723e510..ad9ec398bc 100644
--- a/en/handbook/contrib/chapter.sgml
+++ b/en/handbook/contrib/chapter.sgml
@@ -588,15 +588,15 @@
 	    the <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></citerefentry> command, with the &ldquo;context diff&rdquo;
 	    form being preferred. For example:</para>
 	  
-	    <para><informalexample>
+	    <para>
 	      <screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
-	    </informalexample>
+	    
 
 	    or
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
-	    </informalexample>
+	    
 
 	    would generate such a set of context diffs for
 	    the given source file or directory hierarchy. See the man page
diff --git a/en/handbook/cutting-edge/chapter.sgml b/en/handbook/cutting-edge/chapter.sgml
index f29687c694..e06beb5775 100644
--- a/en/handbook/cutting-edge/chapter.sgml
+++ b/en/handbook/cutting-edge/chapter.sgml
@@ -154,9 +154,9 @@ subscribe cvs-all</programlisting>
 			program with <ulink
 			  URL="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this supfile</ulink>. This is the second most recommended method, since it allows  you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron and keep their sources up-to-date automatically. For a fairly easy interface to this, simply type:</para>
 
-    <informalexample>
+    
        <screen>&prompt.root; <userinput>pkg_add -f ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz</userinput></screen>
-    </informalexample>
+    
 
  
 		    </listitem>
@@ -166,16 +166,16 @@ subscribe cvs-all</programlisting>
 			always &ldquo;exported&rdquo; on: <ulink
 		      URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current</ulink> We also use <command>wu-ftpd</command> which allows compressed/tar'd grabbing of whole trees. e.g. you see:</para>
 
-			<informalexample>
+			
 			  <screen>usr.bin/lex</screen>
-			</informalexample>
+			
 
 		    <para>You can do:
 
-			<informalexample>
+			
 			  <screen><prompt>ftp&gt;</prompt> <userinput>cd usr.bin</userinput>
 <prompt>ftp&gt;</prompt> <userinput>get lex.tar.Z</userinput></screen>
-			</informalexample>
+			
 
 		      and it will get the whole directory for you as a compressed tar file.</para>
 		    </listitem>
@@ -318,9 +318,9 @@ subscribe cvs-all</programlisting>
 			program with <ulink
 			  URL="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/stable-supfile">this supfile</ulink>. This is the second most recommended method, since it allows  you to grab the entire collection once and then only what has changed from then on. Many people run cvsup from cron to keep their sources up-to-date automatically. For a fairly easy interface to this, simply type;</para>
 
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>pkg_add -f ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz</userinput></screen>
-	      </informalexample>
+	      
 		    </listitem>
 		    
 		    <listitem>
@@ -332,16 +332,16 @@ subscribe cvs-all</programlisting>
 			compressed/tar'd grabbing of whole trees. e.g. you
 			see:</para>
 
-			<informalexample>
+			
 			  <screen>usr.bin/lex</screen>
-			</informalexample>
+			
 
 		      <para>You can do:
 
-			<informalexample>
+			
 			  <screen><prompt>ftp&gt;</prompt> <userinput>cd usr.bin</userinput>
 <prompt>ftp&gt;</prompt> <userinput>get lex.tar.Z</userinput></screen>
-			</informalexample>
+			
 
 			and it will get the
 			whole directory for you as a compressed tar
@@ -891,10 +891,10 @@ However, since the trees
 	    
 	    <para>To apply the deltas, simply say:</para>
 	    
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>cd /where/ever/you/want/the/stuff</userinput>
 &prompt.root; <userinput>ctm -v -v /where/you/store/your/deltas/src-xxx.*</userinput></screen>
-	      </informalexample>
+	      
 	    
 	    <para><application>CTM</application> understands deltas which have been
 	      put through <command>gzip</command>, so you do not
@@ -991,10 +991,10 @@ However, since the trees
 		<filename>lib/libc/Makefile</filename> from your collection of
 		saved CTM deltas, run the commands:</para>
 	      
-		<informalexample>
+		
 		  <screen>&prompt.root; <userinput>cd /where/ever/you/want/to/extract/it/</userinput>
 &prompt.root; <userinput>ctm -e '^lib/libc/Makefile' ~ctm/src-xxx.*</userinput></screen>
-		</informalexample>
+		
 	      
 	      <para>For every file specified in a <application>CTM</application> delta, the
 		<option>-e</option> and <option>-x</option> options
@@ -1684,9 +1684,9 @@ cvs-crypto</programlisting>
 	    <para>You are now ready to try an update. The command line for
 	      doing this is quite simple:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cvsup <replaceable>supfile</replaceable></userinput></screen>
-	    </informalexample>
+	    
 	    
 	    <para>where <filename><replaceable>supfile</replaceable></filename> is of course the name of the supfile you
 	      have just created. Assuming you are running under X11, <command>cvsup</command>
@@ -1703,10 +1703,10 @@ cvs-crypto</programlisting>
 	      convenient, and name it as an extra argument on the command
 	      line:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>mkdir /var/tmp/dest</userinput>
 &prompt.root; <userinput>cvsup supfile /var/tmp/dest</userinput></screen>
-	    </informalexample>
+	    
 	    
 	    <para>The directory you specify will be used as the destination
 	      directory for all file updates. <application>CVSup</application> will examine your usual
@@ -1723,9 +1723,9 @@ cvs-crypto</programlisting>
 	      you should add a couple of options to the command line when you
 	      run cvsup:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cvsup -g -L 2 supfile</userinput></screen>
-	    </informalexample>
+	    
 	    
 	    <para>The <option>-g</option> tells cvsup not to use its GUI. This is automatic
 	      if you are not running X11, but otherwise you have to specify
diff --git a/en/handbook/disks/chapter.sgml b/en/handbook/disks/chapter.sgml
index ee74a49501..1bfe3b074c 100644
--- a/en/handbook/disks/chapter.sgml
+++ b/en/handbook/disks/chapter.sgml
@@ -107,7 +107,7 @@
 	&ldquo;appropriate&rdquo; any partition it finds which it doesn't
 	understand.</para>
       
-      <informalexample>
+      
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/rsd1 bs=1k count=1</userinput>
 &prompt.root; <userinput>disklabel -Brw sd1 auto</userinput>
 &prompt.root; <userinput>disklabel -e sd</userinput>1				# create the `e' partition
@@ -115,18 +115,18 @@
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>vi /etc/fstab</userinput>					# add an entry for /dev/sd1e
 &prompt.root; <userinput>mount /1</userinput></screen>
-    </informalexample>
+    
 
 	<para>An alternate method is:</para>
 	
-    <informalexample>
+    
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/rsd1 count=2</userinput>
 &prompt.root; <userinput>disklabel /dev/rsd1 | disklabel -BrR sd1 /dev/stdin</userinput>
 &prompt.root; <userinput>newfs /dev/rsd1e</userinput>
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>vi /etc/fstab</userinput>					# add an entry for /dev/sd1e
 &prompt.root; <userinput>mount /1</userinput></screen>
-      </informalexample>
+      
     </sect2>
   </sect1>
 
diff --git a/en/handbook/eresources/chapter.sgml b/en/handbook/eresources/chapter.sgml
index 56e4bc2172..93d21fbb15 100644
--- a/en/handbook/eresources/chapter.sgml
+++ b/en/handbook/eresources/chapter.sgml
@@ -347,11 +347,11 @@ subscribe &lt;listname&gt; [&lt;optional address&gt;]</programlisting>
 	    in the body of your message. For example, to
 	    subscribe yourself to <literal>freebsd-announce</literal>, you'd do:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>mail majordomo@FreeBSD.ORG</userinput>
 subscribe freebsd-announce
 ^D</screen>
-	    </informalexample>
+	    
 
 	  <para>If you want to subscribe yourself under a
 	    different name, or submit a subscription request for a local
@@ -359,11 +359,11 @@ subscribe freebsd-announce
 	    interested parties at one site, and highly appreciated by us!),
 	    you would do something like:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>mail majordomo@FreeBSD.ORG</userinput>
 subscribe freebsd-announce local-announce@somesite.com
 ^D</screen>
-	    </informalexample>
+	    
 
 	  <para>Finally, it is also possible to unsubscribe
 	    yourself from a list, get a list of other list members or see the
@@ -371,11 +371,11 @@ subscribe freebsd-announce local-announce@somesite.com
 	    messages to majordomo. For a complete list of available commands,
 	    do this:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>mail majordomo@FreeBSD.ORG</userinput>
 help
 ^D</screen>
-	    </informalexample>
+	    
 
 	  <para>Again, we would like to request that you keep
 	    discussion in the technical mailing lists on a technical track.
diff --git a/en/handbook/hw/chapter.sgml b/en/handbook/hw/chapter.sgml
index 61c9047178..9397bbcfee 100644
--- a/en/handbook/hw/chapter.sgml
+++ b/en/handbook/hw/chapter.sgml
@@ -1788,9 +1788,9 @@ INS8250  -&gt; INS8250B
 		echo any of the test characters. If you forget to do this,
 		COMTEST will report at least this one difference:</para>
 
-		<informalexample>
+		
 		  <screen>Error (6)...Timeout interrupt failed: IIR = c1  LSR = 61</screen>
-		</informalexample>
+		
 	      
 	    </sect4>
 	    
@@ -2763,7 +2763,7 @@ flags 0x1005</programlisting> indicates that the master port is
 		    as follows: (obviously the sio numbers, IO and IRQ could
 		    be different)</para>
 		    
-		    <informalexample>
+		    
 		      <screen>sio1 at 0x100-0x107 flags 0x1005 on isa
 sio1: type 16550A (multiport)
 sio2 at 0x108-0x10f flags 0x1005 on isa
@@ -2796,14 +2796,14 @@ sio15 at 0x170-0x177 flags 0x1005 on isa
 sio15: type 16550A (multiport)
 sio16 at 0x178-0x17f irq 3 flags 0x1005 on isa
 sio16: type 16550A (multiport master)</screen>
-		      </informalexample>
+		      
 
 		  <para>If the messages go by too fast to
 		      see,
 
-		    <informalexample>
+		    
 		      <screen>&prompt.root; <userinput>dmesg | more</userinput></screen>
-		    </informalexample> will
+		     will
 		      show you the boot messages.</para>
 		  </step>
 		  
@@ -2813,14 +2813,14 @@ sio16: type 16550A (multiport master)</screen>
 		      using the <filename>/dev/MAKEDEV</filename> script.
 		      After becoming root:</para>
 		    
-		      <informalexample>
+		      
 		      <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV tty1</userinput>
 &prompt.root; <userinput>./MAKEDEV cua1</userinput>
 <emphasis>(everything in between)</emphasis>
 &prompt.root; <userinput>./MAKEDEV ttyg</userinput>
 &prompt.root; <userinput>./MAKEDEV cuag</userinput></screen>
-		      </informalexample>
+		      
 
 		  <para>If you do not want or need callout
 		      devices for some reason, you can dispense with making
@@ -2832,9 +2832,9 @@ sio16: type 16550A (multiport master)</screen>
 		      devices are working, you can simply plug a modem into
 		      each port and (as root)
 
-		    <informalexample>
+		    
 		      <screen>&prompt.root; <userinput>echo at &gt; ttyd*</userinput></screen>
-		    </informalexample> for each device you have made. You
+		     for each device you have made. You
 		      <emphasis>should</emphasis> see the RX lights flash for
 		      each working port.</para>
 		  </step>
@@ -2875,10 +2875,10 @@ device cy0 at isa? tty irq 10 iomem 0xd4000 iosiz 0x2000 vector cyintr</programl
 		    nodes</link> by typing (the following example
 		  assumes an 8-port board):</para>
 		  
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>for i in 0 1 2 3 4 5 6 7;do ./MAKEDEV cuac$i ttyc$i;done</userinput></screen>
-		  </informalexample>
+		  
 	      </step>
 	      
 	      <step>
@@ -3944,17 +3944,17 @@ disk            wd3     at wdc1 drive 1</programlisting>
 		FreeBSD kernels used to report the geometry of SCSI disks when
 		booting. An example from one of my systems:</para>
 	      
-	      <informalexample>
+	      
 		<screen>aha0 targ 0 lun 0: &lt;MICROP 1588-15MB1057404HSP4&gt;
 sd0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512</screen>
-	      </informalexample>
+	      
 	      
 	      <para>Newer kernels usually do not report this information. e.g.</para>
 
-		<informalexample>
+		
 		  <screen>(bt0:0:0): "SEAGATE ST41651 7574" type 0 fixed SCSI 2
 sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen>
-		</informalexample>
+		
 	      
 	      <para>Why has this changed?</para>
 	      
@@ -4189,13 +4189,13 @@ options         SCSI_DELAY=15         #Be pessimistic about Joe SCSI device</pro
 		reported by the kernel when booting. An example for two of my
 		cartridge tape units:</para>
 	      
-	      <informalexample>
+	      
 		<screen>Feb 25 21:03:34 yedi /kernel: ahb0 targ 5 lun 0: &lt;TANDBERG TDC 3600       -06:&gt;
 Feb 25 21:03:34 yedi /kernel: st0: Tandberg tdc3600 is a known rogue
 
 Mar 29 21:16:37 yedi /kernel: aha0 targ 5 lun 0: &lt;ARCHIVE VIPER 150  21247-005&gt;
 Mar 29 21:16:37 yedi /kernel: st1: Archive  Viper 150 is a known rogue </screen>
-	      </informalexample>
+	      
 	      
 	      <para>For instance, there are devices that respond to  all LUNs
 		on a certain target ID, even if they are actually only one
@@ -5107,24 +5107,24 @@ options        "TUNE_1542"             #dynamic tune of bus DMA speed</programli
 		the drive. Before using this drive, set the tape blocksize
 		with</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>mt -f /dev/st0ctl.0 blocksize 1024</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>Before using a minicartridge for the first time, the
 		minicartridge must be formated. FreeBSD 2.1.0-RELEASE and
 		earlier:</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>/sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0"</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>(Alternatively, fetch a copy of the <command>scsiformat</command> shell script from FreeBSD
 		2.1.5/2.2.) FreeBSD 2.1.5 and later:</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>/sbin/scsiformat -q -w /dev/rst0.ctl</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>Right now, this drive cannot really be recommended for
 		FreeBSD.</para>
diff --git a/en/handbook/install/chapter.sgml b/en/handbook/install/chapter.sgml
index b11bbc33d0..e058416801 100644
--- a/en/handbook/install/chapter.sgml
+++ b/en/handbook/install/chapter.sgml
@@ -104,9 +104,9 @@
 		  <para>If you are using MS-DOS then download  <ulink
 		      URL="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/tools/fdimage.exe">fdimage.exe</ulink> or get it from <filename>tools\fdimage.exe</filename> on the CDROM and then run it like so:</para>
 
-		    <informalexample>
+		    
 		      <screen><prompt>E:\&gt;</prompt> <userinput>tools\fdimage floppies\boot.flp a:</userinput></screen>
-		    </informalexample>
+		    
 	      <para>The <emphasis>fdimage</emphasis>
 		    program will format the <devicename>A:</devicename> drive and then copy the
 		    <filename>boot.flp</filename> image onto it (assuming that you're at the top
@@ -119,9 +119,9 @@
 		  <para>If you are using a UNIX system to create the floppy
 		    image:</para>
 
-		    <informalexample>
+		    
 		      <screen>&prompt.root; <userinput>dd if=boot.flp of=<replaceable>disk_device</replaceable></userinput></screen>
-		    </informalexample>
+		    
 	      <para><replaceable>disk_device</replaceable> is
 		    the <filename>/dev</filename> entry for the floppy drive.
 		    On FreeBSD systems, this is <filename>/dev/rfd0</filename>
@@ -135,7 +135,7 @@
 	  <step>
 	    <para>With the installation disk in the A: drive, reboot your
 	      computer. You should get a boot prompt something like this:</para>
-	      <informalexample>
+	      
 		<screen>
 &gt;&gt; FreeBSD BOOT ...
 Usage: [[[0:][wd](0,a)]/kernel][-abcCdhrsv]
@@ -143,7 +143,7 @@ Use 1:sd(0,a)kernel to boot sd0 if it is BIOS drive 1
 Use ? for file list or press Enter for defaults
 Boot:
 		</screen>
-	      </informalexample>
+	      
 	  <para>If you do <emphasis>not</emphasis> type
 	      anything, FreeBSD will automatically boot with its default
 	      configuration after a delay of about five seconds. As FreeBSD
@@ -786,12 +786,12 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
 	    illustrates:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
 &prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput>
 &prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0</userinput>
 	      </screen>
-	    </informalexample>
+	    
 	  
 
 	  <note>
@@ -827,11 +827,11 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
 	    suggest using the DOS <command>xcopy</command> command.
 	    For example, to prepare for a minimal installation of FreeBSD:</para>
 
-	    <informalexample>
+	    
 	      <screen><prompt>C:\&gt;</prompt> <userinput>MD C:\FREEBSD</userinput>
 <prompt>C:\&gt;</prompt> <userinput>XCOPY /S E:\BIN C:\FREEBSD\BIN\</userinput>
 <prompt>C:\&gt;</prompt> <userinput>XCOPY /S E:\MANPAGES C:\FREEBSD\MANPAGES\</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>Assuming that <devicename>C:</devicename>
 	    is where you have free space and <devicename>E:</devicename>
@@ -853,10 +853,10 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
 	    after getting all of the files for distribution you are interested
 	    in, simply tar them onto the tape with a command like:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /freebsd/distdir</userinput>
 &prompt.root; <userinput>tar cvf /dev/rwt0 dist1 ... dist2</userinput></screen>
-	    </informalexample>
+	    
 
 	  
 	  <para>When you go to do the installation, you should also make sure
@@ -1011,9 +1011,9 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
 	      of a name server:</para>
 	    
 	    
-	      <informalexample>
+	      
 		<screen><userinput>ftp://165.113.121.81/pub/FreeBSD/&rel.current;-RELEASE</userinput></screen>
-	      </informalexample>
+	      
 	    
 	    
 	    <para>There are two FTP installation modes you can use:</para>
@@ -1200,9 +1200,9 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
 	  mount extended partitions exactly like you would mount any other DOS
 	  drive, e.g.:</para>
 	
-	<informalexample>
+	
 	  <screen>&prompt.root; <userinput>mount -t msdos /dev/sd0s5 /dos_d</userinput></screen>
-	</informalexample>
+	
 	
 	<para><emphasis>Can I run MS-DOS binaries under
 	    FreeBSD?</emphasis></para>
diff --git a/en/handbook/kernelconfig/chapter.sgml b/en/handbook/kernelconfig/chapter.sgml
index 35d0fd1e36..bfdf8592c9 100644
--- a/en/handbook/kernelconfig/chapter.sgml
+++ b/en/handbook/kernelconfig/chapter.sgml
@@ -84,10 +84,10 @@
 	  copy the <filename>GENERIC</filename> configuration file to the name
 	  you want to give your kernel. For example:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cd /usr/src/sys/i386/conf</userinput>
 &prompt.root; <userinput>cp GENERIC MYKERNEL</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>Traditionally, this name is in all capital
 	  letters and, if you are maintaining multiple FreeBSD machines with
@@ -132,13 +132,13 @@
 	<para>When you are finished, type the following to compile and install
 	  your kernel:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>/usr/sbin/config MYKERNEL</userinput>
 &prompt.root; <userinput>cd ../../compile/MYKERNEL</userinput>
 &prompt.root; <userinput>make depend</userinput>
 &prompt.root; <userinput>make</userinput>
 &prompt.root; <userinput>make install</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>The new kernel will be copied to the root
 	  directory as <filename>/kernel</filename> and the old kernel will be
@@ -1551,9 +1551,9 @@ controller wcd0</programlisting>
 	  device. It turns out that those files are not there, so I must
 	  change to the <filename>/dev</filename> directory and type:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>sh MAKEDEV wcd0</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>When this script finishes, you will find that
 	  there are now <filename>wcd0c</filename> and <filename>rwcd0c</filename> entries in <filename>/dev</filename> so
@@ -1561,9 +1561,9 @@ controller wcd0</programlisting>
 	
 	<para>For sound cards, the command:
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>sh MAKEDEV snd0</userinput></screen>
-	  </informalexample> creates the appropriate entries.</para>
+	   creates the appropriate entries.</para>
 
 	<note>
 	  <para>When creating device nodes for devices such as sound cards, if
@@ -1604,9 +1604,9 @@ controller wcd0</programlisting>
 		  it with <command>vi</command>. For example, if
 		  you see:
 		
-		  <informalexample>
+		  
 		    <screen>config: line 17: syntax error</screen>
-		  </informalexample> you can skip to the problem in <command>vi</command> by typing <COMMAND>17G</COMMAND> in command mode.
+		   you can skip to the problem in <command>vi</command> by typing <COMMAND>17G</COMMAND> in command mode.
 		  Make sure the keyword is typed correctly, by comparing it to
 		  the GENERIC kernel or another reference.</para>
 	      </listitem>
@@ -1660,18 +1660,18 @@ controller wcd0</programlisting>
 		    kernel file that <command>make</command> installs (in
 		    order to move another kernel back permanently) is:</para>
 		  
-		    <informalexample>
+		    
 		    <screen>&prompt.root; <userinput>chflags noschg /kernel</userinput></screen>
-		    </informalexample>
+		    
 
 		<para>And, if you want to
 		    &ldquo;lock&rdquo; your new kernel into place, or any
 		    file for that matter, so that it cannot be moved or
 		    tampered with:</para>
 		  
-		    <informalexample>
+		    
 		    <screen>&prompt.root; <userinput>chflags schg /kernel</userinput></screen>
-		    </informalexample>
+		    
 	        </note>
 	      </listitem>
 	    </varlistentry>
diff --git a/en/handbook/kerneldebug/chapter.sgml b/en/handbook/kerneldebug/chapter.sgml
index 796252e1d3..2507290ae1 100644
--- a/en/handbook/kerneldebug/chapter.sgml
+++ b/en/handbook/kerneldebug/chapter.sgml
@@ -61,12 +61,12 @@ Dumps to non-swap devices, tapes for example,
 	  single user state using the <option>-s</option> flag at the boot
 	  prompt, and then perform the following steps:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>fsck -p</userinput>
 &prompt.root; <userinput>mount -a -t ufs</userinput>       # so your file system for /var/crash is writable
 &prompt.root; <userinput>savecore -N /kernel.panicked /var/crash</userinput>
 &prompt.root; <userinput>exit</userinput>                  # ...to multi-user</screen>
-	  </informalexample>
+	  
 
 	<para>This instructs <citerefentry><refentrytitle>savecore</refentrytitle><manvolnum>8</manvolnum></citerefentry> to
 	  use another kernel for symbol name extraction. It would otherwise
@@ -78,11 +78,11 @@ Dumps to non-swap devices, tapes for example,
 	  <filename>/sys/compile/WHATEVER</filename> and run <command>kgdb</command>. From <command>kgdb</command>
 	  do:
 	  
-	  <informalexample>
+	  
 	    <screen><userinput>symbol-file kernel.debug</userinput>
 <userinput>exec-file /var/crash/kernel.0</userinput>
 <userinput>core-file /var/crash/vmcore.0</userinput></screen>
-	  </informalexample>
+	  
 
 	  and voila, you can debug the crash dump using the
 	  kernel sources just like you can for any other program.</para>
@@ -93,7 +93,7 @@ Dumps to non-swap devices, tapes for example,
 	  Despite this, it is a real-world error trace taken during the
 	  development of the pcvt console driver.</para>
 
-	  <informalexample>
+	  
 	    <screen> 1:Script started on Fri Dec 30 23:15:22 1994
  2:&prompt.root; <userinput>cd /sys/compile/URIAH</userinput>
  3:&prompt.root; <userinput>kgdb kernel /var/crash/vmcore.1</userinput> 
@@ -174,7 +174,7 @@ Dumps to non-swap devices, tapes for example,
 78:exit
 79:
 80:Script done on Fri Dec 30 23:18:04 1994</screen>
-	  </informalexample>
+	  
 
 	<para>Comments to the above script:</para>
 	
@@ -247,9 +247,9 @@ Dumps to non-swap devices, tapes for example,
       option to the <command>ddd</command> command line you would use
       normally. For example;</para>
 
-    <informalexample>
+    
       <screen>&prompt.root; <userinput>ddd -k /var/crash/kernel.0 /var/crash/vmcore.0</userinput></screen>
-    </informalexample>
+    
 
     <para>You should then be able to go about looking at the crash dump using
       <command>ddd</command>'d graphical interface.</para>
@@ -348,10 +348,10 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	<para>The DDB commands roughly resemble some <command>gdb</command> commands. The first thing you probably
 	  need to do is to set a breakpoint:</para>
 	
-	  <informalexample>
+	  
 	    <screen><userinput>b function-name</userinput>
 <userinput>b address</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>Numbers are taken hexadecimal by default, but to make them
 	  distinct from symbol names; hexadecimal numbers starting with the
@@ -362,15 +362,15 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	
 	<para>To continue the operation of an interrupted kernel, simply type:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>c</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>To get a stack trace, use:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>trace</userinput></screen>
-	  </informalexample>
+	  
 
 	<note>
 	  <para>Note that when entering DDB via a hot-key, the kernel is
@@ -380,32 +380,32 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	
 	<para>If you want to remove a breakpoint, use</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>del</userinput>
 <userinput>del address-expression</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>The first form will be accepted immediately after
 	  a breakpoint hit, and deletes the current breakpoint. The second
 	  form can remove any breakpoint, but you need to specify the exact
 	  address; this can be obtained from:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>show b</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>To single-step the kernel, try:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>s</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>This will step into functions, but you can make
 	  DDB trace them until the matching return statement is reached by:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>n</userinput></screen>
-	  </informalexample>
+	  
 
 	<note>
 	  <para>This is different from <command>gdb</command>'s <command>next</command>
@@ -414,27 +414,27 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	
 	<para>To examine data from memory, use (for example):
 
-	  <informalexample>
+	  
 	    <screen><userinput>x/wx 0xf0133fe0,40</userinput>
 <userinput>x/hd db_symtab_space</userinput>
 <userinput>x/bc termbuf,10</userinput>
 <userinput>x/s stringbuf</userinput></screen>
-	  </informalexample>
+	  
 
 	  for word/halfword/byte access, and
 	  hexadecimal/decimal/character/ string display. The number after the
 	  comma is the object count. To display the next 0x10 items, simply
 	  use:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>x ,10</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>Similarly, use
 
-	  <informalexample>
+	  
 	    <screen><userinput>x/ia foofunc,10</userinput></screen>
-	  </informalexample>
+	  
 
 	  to disassemble the first 0x10 instructions of
 	  <function>foofunc</function>, and display them along with
@@ -442,10 +442,10 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	
 	<para>To modify memory, use the write command:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>w/b termbuf 0xa 0xb 0</userinput>
 <userinput>w/w 0xf0010030 0 0</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>The command modifier
 	  (<literal>b</literal>/<literal>h</literal>/<literal>w</literal>) specifies the size of the data to be
@@ -455,36 +455,36 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	
 	<para>If you need to know the current registers, use:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>show reg</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>Alternatively, you can display a single register
 	  value by e.g.
 
-	  <informalexample>
+	  
 	    <screen><userinput>p $eax</userinput></screen>
-	  </informalexample> and modify it by:</para>
+	   and modify it by:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>set $eax new-value</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>Should you need to call some kernel functions from DDB, simply
 	  say:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>call func(arg1, arg2, ...)</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>The return value will be printed.</para>
 	
 	<para>For a <citerefentry><refentrytitle>ps</refentrytitle><manvolnum>1</manvolnum></citerefentry> style summary of all running
 	  processes, use:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>ps</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>Now you have now examined why your kernel failed, and you wish
 	  to reboot. Remember that, depending on the severity of previous
@@ -492,18 +492,18 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	  as expected. Perform one of the following actions to shut down and
 	  reboot your system:</para>
 
-	  <informalexample>
+	  
 	    <screen><userinput>call diediedie()</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>This will cause your kernel to dump core and reboot, so you can
 	  later analyze the core on a higher level with kgdb. This command
 	  usually must be followed by another <command>continue</command> statement. There is now an alias for
 	  this: <command>panic</command>.</para>
 	
-	  <informalexample>
+	  
 	    <screen><userinput>call boot(0)</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>Which might be a good way to cleanly shut down the
 	  running system, <function>sync()</function> all disks, and finally
@@ -511,18 +511,18 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	  kernel are not damaged, this might be a good way for an almost clean
 	  shutdown.</para>
 	
-	  <informalexample>
+	  
 	    <screen><userinput>call cpu_reset()</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>is the final way out of disaster and almost the
 	  same as hitting the Big Red Button.</para>
 	
 	<para>If you need a short command summary, simply type:</para>
 	
-	  <informalexample>
+	  
 	    <screen><userinput>help</userinput></screen>
-	  </informalexample>
+	  
 
 	<para>However, it is highly recommended to have a
 	  printed copy of the <citerefentry><refentrytitle>ddb</refentrytitle><manvolnum>4</manvolnum></citerefentry> manual page
@@ -556,7 +556,7 @@ options DDB</programlisting> to your config file, and rebuild. (See <link
 	  serial line of the debugging host. Now, on the debugging machine,
 	  go to the compile directory of the target kernel, and start gdb:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>gdb -k kernel</userinput>
 GDB is free software and you are welcome to distribute copies of it
  under certain conditions; type "show copying" to see the conditions.
@@ -564,41 +564,41 @@ There is absolutely no warranty for GDB; type "show warranty" for details.
 GDB 4.16 (i386-unknown-freebsd),
 Copyright 1996 Free Software Foundation, Inc...
 <prompt>(kgdb)</prompt> </screen>
-	  </informalexample>
+	  
 	
 	<para>Initialize the remote debugging session (assuming the first
 	  serial port is being used) by:</para>
 
-	  <informalexample>
+	  
 	    <screen><prompt>(kgdb)</prompt> <userinput>target remote /dev/cuaa0</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>Now, on the target host (the one that entered DDB right before
 	  even starting the device probe), type:</para>
 
-	  <informalexample>
+	  
 	    <screen>Debugger("Boot flags requested debugger")
 Stopped at Debugger+0x35: movb	$0, edata+0x51bc
 <prompt>db&gt;</prompt> <userinput>gdb</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>DDB will respond with:</para>
 	
-	  <informalexample>
+	  
 	    <screen>Next trap will enter GDB remote protocol mode</screen>
-	  </informalexample>
+	  
 	
 	<para>Every time you type <command>gdb</command>, the mode will be toggled between
 	  remote GDB and local DDB. In order to force a next trap
 	  immediately, simply type <command>s</command> (step). Your hosting GDB will now
 	  gain control over the target kernel:</para>
 	
-	  <informalexample>
+	  
 	    <screen>Remote debugging using /dev/cuaa0
 Debugger (msg=0xf01b0383 "Boot flags requested debugger")
     at ../../i386/i386/db_interface.c:257
 <prompt>(kgdb)</prompt></screen>
-	  </informalexample>
+	  
 	
 	<para>You can use this session almost as any other GDB session,
 	  including full access to the source, running it in gud-mode inside
@@ -608,33 +608,33 @@ Debugger (msg=0xf01b0383 "Boot flags requested debugger")
 	<para>Remote GDB can also be used to debug LKMs. First build the LKM
 	  with debugging symbols:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cd /usr/src/lkm/linux</userinput>
 &prompt.root; <userinput>make clean; make COPTS=-g</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>Then install this version of the module on the target machine,
 	  load it and use <command>modstat</command> to find out
 	  where it was loaded:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>linux</userinput>
 &prompt.root; <userinput>modstat</userinput>
 Type     Id Off Loadaddr Size Info     Rev Module Name
 EXEC      0   4 f5109000 001c f510f010   1 linux_mod</screen>
-	  </informalexample>
+	  
 	
 	<para>Take the load address of the module and add 0x20 (probably to
 	  account for the a.out header). This is the address that the module
 	  code was relocated to. Use the <command>add-symbol-file</command> command in GDB to tell the
 	  debugger about the module:</para>
 
-	  <informalexample>
+	  
 	    <screen><prompt>(kgdb)</prompt> <userinput>add-symbol-file /usr/src/lkm/linux/linux_mod.o 0xf5109020</userinput>
 add symbol table from file "/usr/src/lkm/linux/linux_mod.o" at
 text_addr = 0xf5109020? (y or n) <userinput>y</userinput>
 <prompt>(kgdb)</prompt></screen>
-	  </informalexample>
+	  
 	
 	<para>You now have access to all the symbols in the LKM.</para>
 	
diff --git a/en/handbook/kernelopts/chapter.sgml b/en/handbook/kernelopts/chapter.sgml
index 0e6defe0cb..4b494b6c43 100644
--- a/en/handbook/kernelopts/chapter.sgml
+++ b/en/handbook/kernelopts/chapter.sgml
@@ -125,9 +125,9 @@ options		notyet,notdef</programlisting>
 	  Unless you have just invented your option, and it does not exist
 	  anywhere yet,
 	
-	<informalexample>
+	
 	  <screen>&prompt.user; <userinput>find /usr/src/sys -name type f | xargs fgrep NEW_OPTION</userinput></screen>
-	</informalexample>
+	
 	
 	is your friend in finding them. Go and edit all those files,
 	  and add
diff --git a/en/handbook/l10n/chapter.sgml b/en/handbook/l10n/chapter.sgml
index 7ab182a604..b37df3d188 100644
--- a/en/handbook/l10n/chapter.sgml
+++ b/en/handbook/l10n/chapter.sgml
@@ -146,18 +146,18 @@ defaultclass = russian</programlisting> in
 		  <listitem>
 		    <para>Alternative variant will be answering <literal>russian</literal> each time when you see
 
-		      <informalexample>
+		      
 			<screen><prompt>Enter login class:</prompt> default []:</screen>
-		      </informalexample> prompt from
+		       prompt from
 		      <citerefentry><refentrytitle>adduser</refentrytitle><manvolnum>8</manvolnum></citerefentry>;</para>
 		  </listitem>
 		  
 		  <listitem>
 		    <para>Another variant: call
 
-		      <informalexample>
+		      
 			<screen>&prompt.root; <userinput>adduser -class russian</userinput></screen>
-			</informalexample> for each Russian user
+			 for each Russian user
 		      you want to add.</para>
 		  </listitem>
 		  
@@ -171,9 +171,9 @@ defaultclass = russian</programlisting> in
 	      <para>If you use <citerefentry><refentrytitle>pw</refentrytitle><manvolnum>8</manvolnum></citerefentry> for adding new users,
 		call it in this form:</para>
 
-		<informalexample>
+		
 		  <screen>&prompt.root; <userinput>pw useradd user_name -L russian</userinput></screen>
-		</informalexample>
+		
 	      
 	    </sect4>
 	  </sect3>
@@ -293,9 +293,9 @@ lp|Russian local line printer:\
 		<para>Go to <filename>/usr/ports/russian/X.language</filename>
 		  directory and say
 
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>make all install</userinput></screen>
-		  </informalexample> there. This port install latest
+		   there. This port install latest
 		  version of KOI8-R fonts. XFree86 3.3 already have some
 		  KOI8-R fonts, but this ones scaled better.</para>
 		
diff --git a/en/handbook/linuxemu/chapter.sgml b/en/handbook/linuxemu/chapter.sgml
index 044c736cf4..adf9e71a9e 100644
--- a/en/handbook/linuxemu/chapter.sgml
+++ b/en/handbook/linuxemu/chapter.sgml
@@ -71,28 +71,28 @@ options  LINUX</programlisting>
 	    loadable module can cause the kernel to crash, so the safest thing
 	    to do is to reinstall the LKM when you install the kernel.</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /usr/src/lkm/linux</userinput>
 &prompt.root; <userinput>make all install</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>Once you have installed the kernel and the LKM,
 	    you can invoke `linux' as root to load the LKM.</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>linux</userinput>
 Linux emulator installed
 Module loaded as ID 0</screen>
-	    </informalexample>
+	    
 
 	  <para>To see whether the LKM is loaded, run
 	    <command>modstat</command>.</para>
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; modstat
 Type     Id Off Loadaddr Size Info     Rev
 Module Name EXEC      0   3 f0baf000 0018 f0bb4000   1 linux_emulator</screen>
-	    </informalexample>
+	    
 
 	  <para>You can cause the LKM to be loaded when the
 	    system boots in either of two ways. In FreeBSD 2.2.1-RELEASE and
@@ -142,11 +142,11 @@ fi</programlisting>
 	  
 	  <para>If you want to verify it is running, modstat will do that:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.user; modstat
 Type     Id Off Loadaddr Size Info     Rev Module Name
 EXEC      0   4 f09e6000 001c f09ec010   1 linux_mod</screen>
-	    </informalexample>
+	    
 
 	  <para>However, there have been reports that this
 	    fails on some 2.2-RELEASE and later systems. If for some reason
@@ -174,10 +174,10 @@ options  LINUX</programlisting>
 	      possible to do this by hand, however, it is vastly simpler to
 	      just grab the linux_lib port:</para>
 
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_lib</userinput>
 &prompt.root; <userinput>make all install</userinput></screen>
-	      </informalexample>
+	      
 	    
 	    <para>and you should have a working linux emulator. Legend (and
 	      the mail archives <!-- smiley -->:-) seems to hold that Linux emulation works
@@ -240,12 +240,12 @@ options  LINUX</programlisting>
 	      libraries it needs by running <command>ldd linuxxdoom</command>:</para>
 	    
 	    
-	      <informalexample>
+	      
 		<screen>&prompt.user; <userinput>ldd linuxxdoom</userinput>
 libXt.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libXt.so.3.1.0
 libX11.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libX11.so.3.1.0
 libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
-	      </informalexample>
+	      
 	    
 	    <para>You would need to get all the files from the last column,
 	      and put them under <filename>/compat/linux</filename>, with the
@@ -253,13 +253,13 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 	      This means you eventually have these files on your FreeBSD
 	      system:</para>
 	      
-	      <informalexample>
+	      
 		<screen>/compat/linux/usr/X11/lib/libXt.so.3.1.0
 /compat/linux/usr/X11/lib/libXt.so.3 -&gt; libXt.so.3.1.0
 /compat/linux/usr/X11/lib/libX11.so.3.1.0
 /compat/linux/usr/X11/lib/libX11.so.3 -&gt; libX11.so.3.1.0
 /compat/linux/lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4 -&gt; libc.so.4.6.29</screen>
-	      </informalexample>
+	      
 
 	    <note>
 	      <para>Note that if you already have a Linux shared library with
@@ -271,17 +271,17 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 		long as you make the symbolic link point to the new one. So,
 		if you have these libraries on your system:</para>
 
-		<informalexample>
+		
 		  <screen>/compat/linux/lib/libc.so.4.6.27
 /compat/linux/lib/libc.so.4 -&gt; libc.so.4.6.27</screen>
-		</informalexample>
+		
 	    
 	      <para>and you find a new binary that claims to require a later
 		version according to the output of <command>ldd</command>:</para>
 
-		<informalexample>
+		
 		  <screen>libc.so.4 (DLL Jump 4.5pl26) -&gt; libc.so.4.6.29</screen>
-		</informalexample>
+		
 
 	      <para>If it is only one or two versions out of date in the in
 		the trailing digit then do not worry about copying
@@ -291,10 +291,10 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 		<filename>libc.so</filename> anyway, and that should leave you
 		with:</para>
 
-		<informalexample>
+		
 		  <screen>/compat/linux/lib/libc.so.4.6.29
 /compat/linux/lib/libc.so.4 -&gt; libc.so.4.6.29</screen>
-		</informalexample>
+		
 	    </note>
 
 	    <note>
@@ -318,10 +318,10 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 	      to their appropriate place on your FreeBSD system (to the
 	      <filename>/compat/linux</filename> tree):</para>
 
-	      <informalexample>
+	      
 		<screen>/compat/linux/lib/ld.so
 /compat/linux/etc/ld.so.config</screen>
-	      </informalexample>
+	      
 	    
 	    <para>If you do not have access to a Linux system, you should get
 	      the extra files you need from various ftp sites. Information on
@@ -334,12 +334,12 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 	      <filename>/foo/bar</filename> is installed as
 	      <filename>/compat/linux/foo/bar</filename>):</para>
 
-	      <informalexample>
+	      
 		<screen>/sbin/ldconfig
 /usr/bin/ldd
 /lib/libc.so.x.y.z
 /lib/ld.so</screen>
-	      </informalexample>
+	      
 	    
 	    <para><command>ldconfig</command> and <command>ldd</command> do not necessarily need to be under
 	      <filename>/compat/linux</filename>; you can install them
@@ -371,11 +371,11 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 	    <para>Those running FreeBSD 2.2-RELEASE should run the Linux
 	      ldconfig program.</para>
 
-	      <informalexample>
+	      
 		<screen>&prompt.root <userinput>cd /compat/linux/lib</userinput>
 &prompt.root; <userinput>/compat/linux/sbin/ldconfig</userinput>
 		</screen>
-	      </informalexample>
+	      
 	    
 	    <para><command>ldconfig</command> is statically linked, so it does not need any
 	      shared libraries to run. It creates the file
@@ -394,10 +394,10 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 	      itself. Supposing that you have it installed as <command>ldd-linux</command>, it
 	      should produce something like:</para>
 
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>ldd-linux `which ldd-linux`</userinput>
 libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
-	      </informalexample>
+	      
 	    
 	    <para>This being done, you are ready to install new Linux
 	      binaries. Whenever you install a new Linux program, you should
@@ -426,11 +426,11 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 	&ldquo;branding&rdquo;. If you attempt to run an unbranded ELF binary,
 	you will get an error message like the following;</para>
 
-      <informalexample>
+      
 	<screen>&prompt.user; <userinput>./my-linux-elf-binary</userinput>
 ELF binary type not known
 Abort</screen>
-      </informalexample>
+      
 
       <para>To help the FreeBSD kernel distinguish between a FreeBSD ELF
 	binary from a Linux binary, use the <citerefentry>
@@ -438,9 +438,9 @@ Abort</screen>
 	  <manvolnum>1</manvolnum>
 	</citerefentry> utility.</para>
 
-      <informalexample>
+      
 	<screen>&prompt.user; <userinput>brandelf -t Linux my-linux-elf-binary</userinput></screen>
-      </informalexample>
+      
 
       <para>The GNU toolchain now places the appropriate branding information
 	into ELF binaries automatically, so you should be needing to do this
@@ -452,10 +452,10 @@ Abort</screen>
 	  
 	  <para>If DNS does not work or you get the messages
 
-	    <informalexample>
+	    
 	      <screen>resolv+: "bind" is an invalid keyword resolv+:
 "hosts" is an invalid keyword</screen>
-	    </informalexample>
+	    
 	  
 	  then you need to configure a
 	    <filename>/compat/linux/etc/host.conf</filename> file containing:
@@ -480,15 +480,15 @@ multi on</programlisting>
 	    2.2-RELEASE or later, you can skip this. For the
 	    <filename>/bin/csh</filename> shell use:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>setenv RESOLV_HOST_CONF /compat/linux/etc/host.conf</userinput></screen>
-	    </informalexample>
+	    
 	  
 	  <para>For <filename>/bin/sh</filename> use:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>RESOLV_HOST_CONF=/compat/linux/etc/host.conf; export RESOLV_HOST_CONF</userinput></screen>
-	    </informalexample>
+	    
 	  
 	</sect2>
 	
@@ -675,12 +675,12 @@ multi on</programlisting>
 	    example, unpack this into
 	    <filename>/usr/local/Mathematica</filename>:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /usr/local</userinput>
 &prompt.root; <userinput>mkdir Mathematica</userinput>
 &prompt.root; <userinput>cd Mathematica</userinput>
 &prompt.root; <userinput>tar -xvf /cdrom/LINUX.TAR</userinput></screen>
-	    </informalexample>
+	    
 	  
 	</sect2>
 	
@@ -695,12 +695,12 @@ multi on</programlisting>
 	    libraries and unpacked the mathematica you can obtain the &ldquo;machine
 	      ID&rdquo; by running the program <command>mathinfo</command> in the Install directory.</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /usr/local/Mathematica/Install</userinput>
 &prompt.root; <userinput>mathinfo</userinput>
 LINUX: 'ioctl' fd=5, typ=0x89(), num=0x27 not implemented
 richc.isdn.bcm.tmc.edu   9845-03452-90255</screen>
-	    </informalexample>
+	    
 
 	  <para>So, for example, the &ldquo;machine ID&rdquo; of <hostid>richc</hostid> is
 	    <literal>9845-03452-90255</literal>. You can ignore the message about the ioctl
@@ -716,10 +716,10 @@ richc.isdn.bcm.tmc.edu   9845-03452-90255</screen>
 	  
 	  <para>You can do this by invoking:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /usr/local/Mathematica/Install</userinput>
 &prompt.root; <userinput>math.install</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>It will ask you to enter your license number
 	    and the Wolfram supplied password. If you get them mixed up or
@@ -782,9 +782,9 @@ richc.isdn.bcm.tmc.edu   9845-03452-90255</screen>
 	    in <filename>/usr/local/Mathematica/bin</filename> add the
 	    following line:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>XKEYSYMDB=/usr/local/Mathematica/lib/X11/XKeysymDB; export XKEYSYMDB</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>This tells Mathematica were to find its own
 	    version of the key mapping file <filename>XKeysymDB</filename>.
@@ -793,9 +793,9 @@ richc.isdn.bcm.tmc.edu   9845-03452-90255</screen>
 	  
 	  <para>On 2.1-STABLE you need to add the following as well:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>RESOLV_HOST_CONF=/compat/linux/etc/host.conf; export RESOLV_HOST_CONF</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>This tells Mathematica to use the linux version
 	    of host.conf. This file has a different syntax from FreeBSD's
@@ -823,9 +823,9 @@ richc.isdn.bcm.tmc.edu   9845-03452-90255</screen>
 	  <para>The Notebook front end is known to hang sometimes when reading
 	    notebook files with an error messages similar to:</para>
 	  
-	    <informalexample>
+	    
 	      <screen><errorname>File .../Untitled-1.mb appears to be broken for OMPR.257.0</errorname></screen>
-	    </informalexample>
+	    
 	  
 	  <para>We have not found the cause for this, but it only affects the
 	    Notebook's X Window front end, not the mathematica engine itself.
diff --git a/en/handbook/mail/chapter.sgml b/en/handbook/mail/chapter.sgml
index 189309586a..237282c3da 100644
--- a/en/handbook/mail/chapter.sgml
+++ b/en/handbook/mail/chapter.sgml
@@ -151,12 +151,12 @@
 	  
 	  <para>Try this:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>hostname</userinput>
 newbsdbox.freebsd.org
 &prompt.root; <userinput>host newbsdbox.freebsd.org</userinput>
 newbsdbox.freebsd.org has address 204.216.27.xx</screen>
-	    </informalexample>
+	    
 	  
 	  <para>If that is all that comes out for your machine, mail directory
 	    to <email>root@newbsdbox.freebsd.org</email>
@@ -164,11 +164,11 @@ newbsdbox.freebsd.org has address 204.216.27.xx</screen>
 	  
 	  <para>If instead, you have this:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>host newbsdbox.freebsd.org</userinput>
 newbsdbox.FreeBSD.org has address 204.216.27.xx
 newbsdbox.FreeBSD.org mail is handled (pri=10) by freefall.FreeBSD.org</screen>
-	    </informalexample>
+	    
 
 	  <para>All mail sent to your host
 	    directly will end up on <hostid>freefall</hostid>, under the same username.</para>
@@ -296,10 +296,10 @@ foo.bar                  MX  10	smtp.smalliap.com	; your mailhost</programlistin
 	    distribution tarball just for you. Assuming you have your CD-ROM
 	    mounted, do:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>tar -xvzf /cdrom/dists/src/ssmailcf.aa</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>Do not panic, this is only a few hundred kilobytes in size.
 	    The file <filename>README</filename> in the <filename>cf</filename> directory can serve as a basic
@@ -318,23 +318,23 @@ foo.bar                  MX  10	smtp.smalliap.com	; your mailhost</programlistin
 	    you need to do in order to convert it into a valid
 	    <filename>sendmail.cf</filename> is:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cd /usr/src/usr.sbin/sendmail/cf/cf</userinput>
 &prompt.root; <userinput>make foo.cf</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>If you don't have a <filename>/usr/obj</filename> hiearchy,
 	    then:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cp foo.cf /etc/sendmail.cf</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>Otherwise:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cp /usr/obj/`pwd`/foo.cf /etc/sendmail.cf</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>A typical <filename>.mc</filename> file might look
 	    like:</para>
@@ -411,7 +411,7 @@ uucp-dom:if-bus .	      uucp-dom:sax</programlisting>
 	    be called with, and the (possibly translated) address. Leave this
 	    mode by typing Control-D.</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>sendmail -bt</userinput>
 ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
 Enter &lt;ruleset&gt; &lt;address&gt;
@@ -419,7 +419,7 @@ Enter &lt;ruleset&gt; &lt;address&gt;
 rewrite: ruleset  0   input: foo @ interface-business . de
 &hellip;
 rewrite: ruleset  0 returns: $# uucp-dom $@ if-bus $: foo &lt; @ interface-business . de</screen>
-	  </informalexample>
+	  
 	  
 	</sect2>
       </sect1>
diff --git a/en/handbook/ports/chapter.sgml b/en/handbook/ports/chapter.sgml
index 59c780838e..2712be81df 100644
--- a/en/handbook/ports/chapter.sgml
+++ b/en/handbook/ports/chapter.sgml
@@ -126,7 +126,7 @@
 	  will need to be root.</para>
 	</note>
 	
-	<informalexample>
+	
 	  <screen>&prompt.root; <userinput>cd /usr/ports/devel/ElectricFence</userinput>
 &prompt.root; <userinput>make install</userinput>
 &gt;&gt; Checksum OK for ElectricFence-2.0.5.tar.gz.
@@ -143,7 +143,7 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
 install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFence-2.0.5/libefence.3 /usr/local/man/man3
 ===&gt;  Compressing manual pages for ElectricFence-2.0.5
 ===&gt;  Registering installation for ElectricFence-2.0.5</screen>
-	</informalexample>
+	
 	
 	<para>To avoid confusing the issue, I have completely removed the
 	  build output.</para>
@@ -152,11 +152,10 @@ install -c -o bin -g bin -m 444 /usr/ports/devel/ElectricFence/work/ElectricFenc
 	  this at the start:-</para>
 	
 	
-	  <informalexample id="ports-fetch">
-	    <screen>&prompt.root; <userinput>make install</userinput>
+	    <screen id="ports-fetch">&prompt.root; <userinput>make install</userinput>
 &gt;&gt; ElectricFence-2.0.5.tar.gz doesn't seem to exist on this system.
 &gt;&gt; Attempting to fetch from ftp://ftp.doc.ic.ac.uk/Mirrors/sunsite.unc.edu/pub/Linux/devel/lang/c/.</screen>
-	  </informalexample>
+	  
 	
 	
 	<para>The <command>make</command> program has noticed that you did not have a local
@@ -294,7 +293,7 @@ WRKDIRPREFIX=   /tmp</programlisting>
 	    an example (the bits in square brackets are comments. Do not type
 	    them in if you are trying this yourself!):-</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>mkdir databases</userinput>
 &prompt.root; <userinput>cd databases</userinput>
@@ -310,7 +309,7 @@ password. Remember to use binary (also known as image) mode!]
 &prompt.root; <userinput>cd gnats</userinput>
 &prompt.root; <userinput>make install</userinput>
 [build and install gnats]</screen>
-	  </informalexample>
+	  
 	  
 	  <para>What happened here? We connected to the FTP server in the
 	    usual way and went to its <filename>databases</filename> sub-directory. When we gave it
@@ -328,7 +327,7 @@ password. Remember to use binary (also known as image) mode!]
 	    all the database skeletons in the ports collection. It looks
 	    almost the same:-</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>ftp ftp.freebsd.org</userinput>
 [log in as `ftp' and give your email address when asked for a
@@ -342,7 +341,7 @@ password. Remember to use binary (also known as image) mode!]
 &prompt.root; <userinput>cd databases</userinput>
 &prompt.root; <userinput>make install</userinput>
 [build and install all the database ports]</screen>
-	  </informalexample>
+	  
 	  
 	  <para>With half a dozen straightforward commands, we have now got a
 	    set of database programs on our FreeBSD machine! All we did that
@@ -640,13 +639,13 @@ do-install:
 		yourself, by using the standard Unix tar program, which comes
 		with the base FreeBSD system, like this:-</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.user; <userinput>tar tvzf foobar.tar.gz</userinput>		
 &prompt.user; <userinput>tar xzvf foobar.tar.gz</userinput>
 &prompt.user; <userinput>tar tvf foobar.tar</userinput>
 &prompt.user; <userinput>tar xvf foobar.tar</userinput>
 		</screen>
-	      </informalexample>
+	      
 	    </listitem>
 	    
 	    <listitem>
@@ -665,11 +664,11 @@ do-install:
 	      <para>Q. I did what you said for <link linkend="ports-cd">compiling ports from a CDROM</link> and it worked great
 		until I tried to install the kermit port:-</para>
 
-		<informalexample>
+		
 		  <screen>&prompt.root; <userinput>make install</userinput>
 &gt;&gt; cku190.tar.gz doesn't seem to exist on this system.
 &gt;&gt; Attempting to fetch from ftp://kermit.columbia.edu/kermit/archives/.</screen>
-		</informalexample>
+		
 		<para>Why can it not be found? Have I got a dud CDROM?</para>
 	      
 	      <para>A. The licensing terms for kermit do not allow us to put
@@ -693,9 +692,9 @@ do-install:
 		CDROM, which is read-only. You can tell it to look somewhere
 		else by doing</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>make  DISTDIR=/where/you/put/it install</userinput></screen>
-	      </informalexample>
+	      
 	    </listitem>
 	    
 	    <listitem>
@@ -709,17 +708,17 @@ do-install:
 		the ports mechanism to use different directories. For
 		instance,</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>make PORTSDIR=/u/people/guests/wurzburger/ports install</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>will compile the port in
 		<filename>/u/people/guests/wurzburger/ports</filename> and
 		install everything under <filename>/usr/local</filename>.</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>make PREFIX=/u/people/guests/wurzburger/local install</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>will compile it in <filename>/usr/ports</filename> and
 		install it in
@@ -727,9 +726,9 @@ do-install:
 	      
 	      <para>And of course</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>make PORTSDIR=.../ports PREFIX=.../local install</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>will combine the two (it is too long to fit on the page if
 		I write it in full, but I am sure you get the idea).</para>
@@ -748,18 +747,18 @@ do-install:
 	      <para>A. To get every single tarball for the ports collection,
 		do</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>make fetch</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>For all the tarballs for a single ports directory,
 		do</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>cd /usr/ports/directory</userinput>
 &prompt.root; <userinput>make fetch</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>and for just one port &mdash; well, I think you have guessed
 		already.</para>
@@ -775,10 +774,10 @@ do-install:
 		closer than sites listed in <makevar>MASTER_SITES</makevar>, do as following
 		example.</para>
 
-		<informalexample>
+		
 		  <screen>&prompt.root; <userinput>cd /usr/ports/directory</userinput>
 &prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
-		</informalexample>
+		
 	    </listitem>
 	    
 	    <listitem>
@@ -822,9 +821,9 @@ do-install:
 		<emphasis>should</emphasis> be able to specify the compiler
 		options used by something like</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>make CFLAGS='-O2 -fno-strength-reduce' install</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>or by editing <filename>/etc/make.conf</filename>, but
 		unfortunately not all ports respect this. The surest way is to
@@ -844,10 +843,10 @@ do-install:
 	  you can find ports relevant to the LISP programming language
 	  using:</para>
 
-	<informalexample>
+	
 	  <screen>&prompt.user; <userinput>cd /usr/ports</userinput>
 &prompt.user; <userinput>make search key=lisp</userinput></screen>
-	</informalexample>
+	
 	    </listitem>
 	    
 	    <listitem>
@@ -871,9 +870,9 @@ do-install:
 	      
 	      <para>A. No problem, just do</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>pkg_delete grizzle-6.5</userinput></screen>
-	      </informalexample>
+	      
 	    </listitem>
 	    
 	    <listitem>
@@ -884,11 +883,11 @@ do-install:
 	      
 	      <para>A. Not at all, you can find it out by doing</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>pkg_info -a | grep grizzle</userinput>
 Information for grizzle-6.5:
 grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arcade game.</screen>
-	      </informalexample>
+	      
 	    </listitem>
 	    
 	    <listitem>
@@ -901,10 +900,10 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
 		in keeping it hanging around. The best way to do this
 		is</para>
 	      
-	      <informalexample>
+	      
 	    <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>make clean</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>which will go through all the ports subdirectories and
 		delete everything except the skeletons for each port.</para>
@@ -925,10 +924,10 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
 	      
 	      <para>A. Just do</para>
 	      
-	      <informalexample>
+	      
 	    <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>make install</userinput></screen>
-	      </informalexample>
+	      
 	    </listitem>
 	    
 	    <listitem>
@@ -950,19 +949,19 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
 	      <para>A. OK, do this before you go to bed/work/the local
 		park:-</para>
 	      
-	      <informalexample>
+	      
 	    <screen>&prompt.root <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>make -DBATCH install</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>This will install every port that does
 		<emphasis>not</emphasis> require user input. Then, when you
 		come back, do</para>
 	      
-	      <informalexample>
+	      
 	    <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>make -DIS_INTERACTIVE install</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>to finish the job.</para>
 	    </listitem>
@@ -976,14 +975,14 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
 	      <para>A. No problem, assuming you know how to make patches for
 		your changes:-</para>
 	      
-	      <informalexample>
+	      
 	    <screen>&prompt.root; <userinput>cd /usr/ports/somewhere/frobble</userinput>
 &prompt.root; <userinput>make extract</userinput>
 &prompt.root; <userinput>cd work/frobble-2.8</userinput>
 [Apply your patches]
 &prompt.root; <userinput>cd ../..</userinput>
 &prompt.root; <userinput>make package</userinput></screen>
-	      </informalexample>
+	      
 	    </listitem>
 	    
 	    <listitem>
@@ -2497,7 +2496,7 @@ ${PREFIX}/man/ja/man4/baz.4.gz</programlisting>
 
 	  <para>First, this is what you (as a porter) need to know</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>install-info --help</userinput>
 install-info [OPTION]... [INFO-FILE [DIR-FILE]]
   Install INFO-FILE in the Info directory file DIR-FILE.
@@ -2509,7 +2508,7 @@ Options:
 --entry=TEXT      Insert TEXT as an Info directory entry.
  :
 --section=SEC     Put this file's entries in section SEC of the directory. :</screen>
-	    </informalexample>
+	    
 
 	    <note>
 	      <para>This program will not actually
diff --git a/en/handbook/ppp-and-slip/chapter.sgml b/en/handbook/ppp-and-slip/chapter.sgml
index a83def5913..fa8199e611 100644
--- a/en/handbook/ppp-and-slip/chapter.sgml
+++ b/en/handbook/ppp-and-slip/chapter.sgml
@@ -150,7 +150,7 @@ pseudo-device tun 1</programlisting>
 	    by typing the following:</para>
 	  
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>ifconfig -a</userinput>
 tun0: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1500
         inet 200.10.100.1 --&gt; 203.10.100.24 netmask 0xffffffff
@@ -158,7 +158,7 @@ tun1: flags=8050&lt;POINTOPOINT,RUNNING,MULTICAST&gt; mtu 576
 tun2: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1500
         inet 203.10.100.1 --&gt; 203.10.100.20 netmask 0xffffffff
 tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
-	    </informalexample>
+	    
 	  
 	  <para>This case shows four tunnel devices, two of which are
 	currently configured and being used. It should be noted that the
@@ -190,36 +190,36 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
 	    following commands:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV tun0</userinput></screen>
-	    </informalexample>
+	    
 	  
 	  <para>If you require 16 tunnel devices in your kernel, you will need
 	    to create more than just tun0:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV tun15</userinput></screen>
-	    </informalexample>
+	    
 	  
 	  <para>Also, to confirm that the kernel is configured correctly, the
 	    following command should give the indicated output:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>ifconfig tun0</userinput>
 tun0: flags=8050&lt;POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1500</screen>
-	    </informalexample>
+	    
 
       <para>The <literal>RUNNING</literal> flag may not yet be set, in which
 	case you will see:</para>
 
-      <informalexample>
+      
 	<screen>&prompt.root; <userinput>ifconfig tun0</userinput>
 tun0: flags=8010&lt;POINTOPOINT,MULTICAST> mtu 1500</screen>
-      </informalexample>
+      
 	</sect2>
 	
 	<sect2>
@@ -433,12 +433,12 @@ domain <replaceable>bar.com</replaceable></programlisting>
 		      a service whose login session looks like this:</para>
 		    
 		    
-		    <informalexample>
+		    
 		      <screen>J. Random Provider
 login: <replaceable>foo</replaceable>
 password: <replaceable>bar</replaceable>
 protocol: ppp</screen>
-		    </informalexample>
+		    
 		    
 		    <para>You will need to alter this script to suit your own
 		      needs. When you write this script for the first time,
@@ -720,9 +720,9 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting>
 		link called <filename>ppp-dialup</filename> to this script
 		using the following commands:</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>ln -s ppp-shell /etc/ppp/ppp-dialup</userinput></screen>
-	      </informalexample>
+	      
 	      
 	      <para>You should use this script as the
 		<emphasis>shell</emphasis> for all your dialup ppp users.
@@ -737,10 +737,10 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlistin
 		world readable containing the following 0 byte files
 	      
 	      
-	      <informalexample>
+	      
 		<screen>-r--r--r--   1 root     wheel           0 May 27 02:23 .hushlogin
 -r--r--r--   1 root     wheel           0 May 27 02:22 .rhosts</screen>
-	      </informalexample>
+	      
 	      
 	      which prevents <filename>/etc/motd</filename> from being
 		displayed.</para>
@@ -759,11 +759,11 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlistin
 		the following:</para>
 	      
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-fred</userinput>
 &prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-sam</userinput>
 &prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-mary</userinput></screen>
-		</informalexample>
+		
 	      
 	      <para>Each of these users dialup accounts should have their
 		shell set to the symbolic link created above. (ie. <username>mary</username>'s
@@ -1092,9 +1092,9 @@ sendmail_flags="-bd"</programlisting>
 	    re-examine the mail queue whenever the ppp link is up by
 	    typing:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>/usr/sbin/sendmail -q</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>You may wish to use the <command>!bg</command>
 	    command in <filename>ppp.linkup</filename> to do this
@@ -1114,18 +1114,18 @@ sendmail_flags="-bd"</programlisting>
 	  
 	  <para>After rebooting, you can now either type</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>ppp</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>and then <command>dial provider</command> to start the PPP session, or, if
 	    you want <command>ppp</command> to establish sessions automatically when there is
 	    outbound traffic (and you haven't created the <filename>start_if.tun0</filename>
 	    script), type</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>ppp -auto provider</userinput></screen>
-	  </informalexample>
+	  
 	  
 	</sect2>
 	
@@ -1311,9 +1311,9 @@ defaultroute    # put this if you want that PPP server will be your
 	      <step>
 		<para>enter:</para>
 
-		  <informalexample>
+		  
 		<screen>&prompt.root; <userinput>/usr/src/usr.sbin/pppd.new/pppd <replaceable>/dev/tty01</replaceable> <replaceable>19200</replaceable></userinput></screen>
-		  </informalexample>
+		  
 
 	      <para>Use the appropriate speed and device name.</para>
 	      </step>
@@ -1456,9 +1456,9 @@ ABORT BUSY ABORT 'NO CARRIER' "" AT OK ATDT&lt;phone.number&gt;
 	  <para>Once these are installed and modified correctly, all you need
 	    to do is</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>pppd</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>This sample based primarily on information provided
 	      by: Trev Roydhouse
@@ -1868,9 +1868,9 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
 		<para>Leave the kermit there (you can suspend it by <command>z</command>) and
 		  as root, type:</para>
 
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>slattach -h -c -s 115200 /dev/modem</userinput></screen>
-		  </informalexample>
+		  
 
 	      <para>If you are able to <command>ping</command> hosts
 		  on the other side of the router, you are connected! If it
@@ -1888,9 +1888,9 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
 	  
 	  <para>Type
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>kill -INT `cat /var/run/slattach.modem.pid`</userinput></screen>
-	    </informalexample>(as root)
+	    (as root)
 	    to kill slattach. Then go back to kermit (<command>fg</command> if you suspended
 	    it) and exit from it (<command>q</command>).</para>
 	  
@@ -1928,11 +1928,11 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
 		<para>Try <command>ifconfig sl0</command> to see your
 		interface status. I get:</para>
 	      
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>ifconfig sl0</userinput>
 sl0: flags=10&lt;POINTOPOINT&gt;
         inet 136.152.64.181 --&gt; 136.152.64.1 netmask ffffff00</screen>
-		  </informalexample>
+		  
 	      </listitem>
 	      
 	      <listitem>
@@ -1940,7 +1940,7 @@ sl0: flags=10&lt;POINTOPOINT&gt;
 		  routing table, in case you get the "no route to host"
 		  messages from ping. Mine looks like:</para>
 
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>netstat -r</userinput>
 Routing tables
 Destination      Gateway            Flags     Refs     Use  IfaceMTU    Rtt    Netmasks:
@@ -1955,7 +1955,7 @@ localhost.Berkel localhost.Berkeley UH          5    42127  lo0 -       0.438
 inr-3.Berkeley.E silvia.HIP.Berkele UH          1        0  sl0 -      -
 silvia.HIP.Berke localhost.Berkeley UGH        34 47641234  lo0 -       0.438
 (root node)</screen>
-		  </informalexample>
+		  
 	      <para>(this is after transferring a bunch
 		  of files, your numbers should be smaller).</para>
 	      </listitem>
@@ -2104,7 +2104,7 @@ Shelmerg        dc-slip sl-helmer       0xfffffc00		  autocomp</programlisting>
 	  <para>Sample output from <command>netstat -i</command>:</para>
 	  
 	  
-	  <informalexample>
+	  
 	    <screen>Name  Mtu   Network     Address            Ipkts Ierrs    Opkts Oerrs  Coll
 ed0   1500  &lt;Link&gt;0.0.c0.2c.5f.4a         291311     0   174209     0   133
 ed0   1500  138.247.224 ivory             291311     0   174209     0   133
@@ -2112,7 +2112,7 @@ lo0   65535 &lt;Link&gt;                            79     0       79     0
 lo0   65535 loop        localhost             79     0       79     0     0
 sl0*  296   &lt;Link&gt;                             0     0        0     0     0
 sl1*  296   &lt;Link&gt;                             0     0        0     0     0</screen>
-	    </informalexample>
+	    
 	  
 	  <para>The <devicename>sl0</devicename> and <devicename>sl1</devicename> interfaces shown in <command>netstat -i</command>'s output indicate that there are
 	    two SLIP interfaces built into the kernel. (The asterisks after
@@ -2344,10 +2344,10 @@ Shelmerg  dc-slip       sl-helmerg      0xfffffc00      autocomp</programlisting
 	      <command>netstat -i</command>; the second line of the output
 	      should look something like:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>ed0   1500  &lt;Link&gt;0.2.c1.28.5f.4a         191923	0   129457     0   116
 	      </screen>
-	    </informalexample>
+	    
 	    
 	    <para>This indicates that this particular system's Ethernet MAC
 	      address is <hostid role="mac">00:02:c1:28:5f:4a</hostid> &mdash;
diff --git a/en/handbook/printing/chapter.sgml b/en/handbook/printing/chapter.sgml
index 0b045fd4e9..7756117e3a 100644
--- a/en/handbook/printing/chapter.sgml
+++ b/en/handbook/printing/chapter.sgml
@@ -393,35 +393,35 @@
 	    <para>To find out if the kernel you are currently using supports a
 	      serial interface, type:</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>dmesg | grep sio<replaceable>N</replaceable></userinput></screen>
-	      </informalexample>
+	      
 
 	    <para>Where <replaceable>N</replaceable> is the
 	      number of the serial port, starting from zero. If you see
 	      output similar to the following:</para>
 	      
-	      <informalexample>
+	      
 		<screen>sio2 at 0x3e8-0x3ef irq 5 on isa
 sio2: type 16550A</screen>
-	      </informalexample>
+	      
 
 	    <para>then the kernel supports the port.</para>
 	    
 	    <para>To find out if the kernel supports a parallel interface,
 	      type:</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>dmesg | grep lpt<replaceable>N</replaceable></userinput></screen>
-	      </informalexample>
+	      
 
 	    <para>Where <replaceable>N</replaceable> is the
 	      number of the parallel port, starting from zero. If you see
 	      output similar to the following
 	      
-	      <informalexample>
+	      
 		<screen>lpt0 at 0x378-0x37f on isa</screen>
-	      </informalexample> then the kernel supports the port.</para>
+	       then the kernel supports the port.</para>
 	    
 	    <para>You might have to reconfigure your kernel in order for the
 	      operating system to recognize and use the parallel or serial
@@ -456,17 +456,17 @@ sio2: type 16550A</screen>
 		  <step>
 		    <para>Change to the <filename>/dev</filename> directory:</para>
 		    
-		      <informalexample>
+		      
 			<screen>&prompt.root; cd /dev</screen>
-		      </informalexample>
+		      
 		  </step>
 		  
 		  <step>
 		    <para>Type:</para>
 		    
-		      <informalexample>
+		      
 			<screen>&prompt.root; <userinput>./MAKEDEV <replaceable>port</replaceable></userinput></screen>
-		      </informalexample>
+		      
 
 		  <para>Where <replaceable>port</replaceable> is the device entry for the
 		      port you want to make. Use <literal>lpt0</literal> for the first parallel port,
@@ -479,9 +479,9 @@ sio2: type 16550A</screen>
 		  <step>
 		    <para>Type:</para>
 		    
-		      <informalexample>
+		      
 			<screen>&prompt.root; <userinput>ls -l <replaceable>port</replaceable></userinput></screen>
-		      </informalexample>
+		      
 
 		  <para>to make sure the device entry got
 		      created.</para>
@@ -579,9 +579,9 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
 		  <step>
 		    <para>Type:</para>
 		    
-		      <informalexample>
+		      
 			<screen>&prompt.root; <userinput>lptcontrol -i -u <replaceable>N</replaceable></userinput></screen>
-		      </informalexample>
+		      
 
 		  <para>to set interrupt-driven mode for
 		      <literal>lpt<replaceable>N</replaceable></literal>.</para>
@@ -590,9 +590,9 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
 		  <step>
 		    <para>Type:</para>
 		    
-		      <informalexample>
+		      
 			<screen>&prompt.root; <userinput>lptcontrol -p -u <replaceable>N</replaceable></userinput></screen>
-		      </informalexample>
+		      
 
 		  <para>to set polled-mode for <literal>lpt<replaceable>N</replaceable></literal>.</para>
 		  </step>
@@ -666,9 +666,9 @@ showpage</programlisting>
 			      use <citerefentry>
 				<refentrytitle>lptest</refentrytitle></citerefentry>. Type:</para>
 			    
-			      <informalexample>
+			      
 				<screen>&prompt.root; <userinput>lptest &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
-			      </informalexample>
+			      
 
 			<para>Where <replaceable>N</replaceable> is the number of the
 			      parallel port, starting from zero.</para>
@@ -679,9 +679,9 @@ showpage</programlisting>
 			      other printer language, then send a small
 			      program to the printer. Type:</para>
 			    
-			      <informalexample>
+			      
 				<screen>&prompt.root; <userinput>cat &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
-			      </informalexample>
+			      
 
 			<para>Then, line by line, type the
 			      program <emphasis>carefully</emphasis> as you
@@ -693,9 +693,9 @@ showpage</programlisting>
 			    <para>Alternatively, you can put the program in a
 			      file and type:</para>
 			    
-			      <informalexample>
+			      
 				<screen>&prompt.root; <userinput>cat <replaceable>file</replaceable> &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
-			      </informalexample>
+			      
 
 			<para>Where <replaceable>file</replaceable> is the name of the
 			      file containing the program you want to send to
@@ -755,9 +755,9 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
 		    <step>
 		      <para>Connect to the printer with  <citerefentry>
 			  <refentrytitle>tip</refentrytitle></citerefentry>. Type:</para>
-			<informalexample>
+			
 			  <screen>&prompt.root; <userinput>tip printer</userinput></screen>
-			</informalexample>
+			
 
 		    <para>If this step does not work, edit
 			the file <filename>/etc/remote</filename> again and
@@ -774,9 +774,9 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
 			      use  <citerefentry>
 				<refentrytitle>lptest</refentrytitle></citerefentry>. Type:</para>
 			    
-			      <informalexample>
+			      
 				<screen><prompt>~</prompt><userinput>$lptest</userinput></screen>
-			      </informalexample>
+			      
 			  </listitem>
 			  
 			  <listitem>
@@ -793,9 +793,9 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
 			    <para>Alternatively, you can put the program in a
 			      file and type:</para>
 			    
-			      <informalexample>
+			      
 				<screen><prompt>~</prompt><userinput>&gt;<replaceable>file</replaceable></userinput></screen>
-			      </informalexample>
+			      
 
 			<para>Where <replaceable>file</replaceable> is the name of the
 			      file containing the program. After
@@ -1012,9 +1012,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      <para>It is also customary to make the directory with a name
 		that is identical to the name of the printer, as shown below:</para>
 		
-		<informalexample>
+		
 		  <screen>&prompt.root; <userinput>mkdir /var/spool/<replaceable>printer-name</replaceable></userinput></screen>
-		</informalexample>
+		
 
 	      <para>However, if you have a lot of printers on
 		your network, you might want to put the spooling directories
@@ -1022,11 +1022,11 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 		with LPD. We will do this for our two example printers
 		<literal>rattan</literal> and <literal>bamboo</literal>:</para>
 		
-		<informalexample>
+		
 		  <screen>&prompt.root; <userinput>mkdir /var/spool/lpd</userinput>
 &prompt.root; <userinput>mkdir /var/spool/lpd/rattan</userinput>
 &prompt.root; <userinput>mkdir /var/spool/lpd/bamboo</userinput></screen>
-		</informalexample>
+		
 
 	      <note>
 		<para>If you are concerned about the privacy of jobs that
@@ -1037,12 +1037,12 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 		  We will do this for our example printers:</para>
 		
 		
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>chown daemon.daemon /var/spool/lpd/rattan</userinput>
 &prompt.root; <userinput>chown daemon.daemon /var/spool/lpd/bamboo</userinput>
 &prompt.root; <userinput>chmod 770 /var/spool/lpd/rattan</userinput>
 &prompt.root; <userinput>chmod 770 /var/spool/lpd/bamboo</userinput></screen>
-		  </informalexample>
+		  
 	      </note>
 	      
 	      <para>Finally, you need to tell LPD about these directories
@@ -1262,9 +1262,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 exit 2</programlisting>
 		<para>Make the file executable:</para>
 		
-		<informalexample>
+		
 		  <screen>&prompt.root; <userinput>chmod 555 /usr/local/libexec/if-simple</userinput></screen>
-		</informalexample>
+		
 	      
 	      <para>And then tell LPD to use it by specifying it with the
 		<literal>if</literal> capability in
@@ -1309,9 +1309,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      
 	      <para>Type:</para>
 		
-		<informalexample>
+		
 		  <screen>&prompt.root; <userinput>lptest 20 5 | lpr -P<replaceable>printer-name</replaceable></userinput></screen>
-		</informalexample>
+		
 
 	      <para>Where <replaceable>printer-name</replaceable> is a the name of a printer
 		(or an alias) specified in <filename>/etc/printcap</filename>.
@@ -1719,9 +1719,9 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
 	  
 	  <para>To print files, type:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>lpr <replaceable>filename</replaceable> <replaceable>...</replaceable></userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>This prints each of the listed files to the
 	    default printer. If you list no files, <citerefentry>
@@ -1729,22 +1729,22 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
 	    data to print from standard input. For example, this command
 	    prints some important system files:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>lpr /etc/host.conf /etc/hosts.equiv</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>To select a specific printer, type:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>lpr -P <replaceable>printer-name</replaceable> <replaceable>filename</replaceable> <replaceable>...</replaceable></userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>This example prints a long listing of the
 	    current directory to the printer named <literal>rattan</literal>:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>ls -l | lpr -P rattan</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>Because no files were listed for the
 	    <citerefentry>
@@ -1780,18 +1780,18 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
 	    specific printer, use the <option>-P</option> option. For
 	    example, the command
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>lpq -P bamboo</userinput></screen>
-	    </informalexample> shows the queue for the printer named <hostid>bamboo</hostid>. Here is an example of the output of
+	     shows the queue for the printer named <hostid>bamboo</hostid>. Here is an example of the output of
 	    the <command>lpq</command> command:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>bamboo is ready and printing
 Rank   Owner    Job  Files                              Total Size
 active kelly    9    /etc/host.conf, /etc/hosts.equiv   88 bytes
 2nd    kelly    10   (standard input)                   1635 bytes
 3rd    mary     11   ...                                78519 bytes</screen>
-	    </informalexample>
+	    
 
 	  <para>This shows three jobs in the queue for
 	    <literal>bamboo</literal>. The first job, submitted by
@@ -1829,7 +1829,7 @@ active kelly    9    /etc/host.conf, /etc/hosts.equiv   88 bytes
 	    also support a <option>-l</option> option to generate a detailed
 	    long listing. Here is an example of <command>lpq -l</command>:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>waiting for bamboo to become ready (offline ?)
 kelly: 1st				 [job 009rose]
        /etc/host.conf                    73 bytes
@@ -1840,7 +1840,7 @@ kelly: 2nd				 [job 010rose]
 
 mary: 3rd                                [job 011rose]
       /home/orchid/mary/research/venus/alpha-regio/mapping 78519 bytes</screen>
-	    </informalexample>
+	    
 	  
 	</sect2>
 	
@@ -1860,18 +1860,18 @@ mary: 3rd                                [job 011rose]
 	      <refentrytitle>lpq</refentrytitle></citerefentry> to find
 	    the job number. Then type:</para>
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>lprm <replaceable>job-number</replaceable></userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>To remove the job from a specific printer, add
 	    the <option>-P</option> option. The following command removes job
 	    number 10 from the queue for the printer
 	    <hostid>bamboo</hostid>:</para>
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>lprm -P bamboo 10</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>The  <citerefentry>
 	      <refentrytitle>lprm</refentrytitle></citerefentry>
@@ -1912,9 +1912,9 @@ mary: 3rd                                [job 011rose]
 	    For example, the following command removes all jobs for the
 	    current user in the queue for the printer named <literal>rattan</literal>:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>lprm -P rattan -</userinput></screen>
-	  </informalexample>
+	  
 
 	  <note>
 	    <para>If you are working in a networked
@@ -1924,7 +1924,7 @@ mary: 3rd                                [job 011rose]
 	      were submitted, even if the same printer is available from other
 	      hosts. The following command sequence demonstrates this:</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.user; <userinput>lpr -P rattan myfile</userinput>
 &prompt.user; <userinput>rlogin orchid</userinput>
 &prompt.user; <userinput>lpq -P rattan</userinput>
@@ -1938,7 +1938,7 @@ rose: Permission denied
 dfA013rose dequeued
 cfA013rose dequeued
 		</screen>
-	      </informalexample>
+	      
 	  </note>
 	</sect2>
 	
@@ -1968,9 +1968,9 @@ cfA013rose dequeued
 	      the TeX typesetting system) named
 	      <filename>fish-report.dvi</filename> to the printer named
 	      <literal>bamboo</literal>:</para>
-	      <informalexample>
+	      
 		<screen>&prompt.user; <userinput>lpr -P bamboo -d fish-report.dvi</userinput></screen>
-	      </informalexample>
+	      
 
 	    <para>These options apply to every file in the job,
 	      so you cannot mix (say) DVI and ditroff files together in a job.
@@ -2090,9 +2090,9 @@ cfA013rose dequeued
 		<refentrytitle>ls</refentrytitle></citerefentry> manual
 	      page on the default printer:</para>
 	    
-	      <informalexample>
+	      
 		<screen>&prompt.user; <userinput>zcat /usr/share/man/man1/ls.1.gz | troff -t -man | lpr -t</userinput></screen>
-	      </informalexample>
+	      
 
 	    <para>The  <citerefentry>
 		<refentrytitle>zcat</refentrytitle></citerefentry>
@@ -2137,9 +2137,9 @@ cfA013rose dequeued
 		      of <filename>parser.h</filename> to the default
 		      printer:</para>
 		    
-		      <informalexample>
+		      
 			<screen>&prompt.user; <userinput>lpr -#3 parser.c parser.h</userinput></screen>
-		      </informalexample>
+		      
 		  </listitem>
 		</varlistentry>
 		
@@ -2956,19 +2956,19 @@ exit 2</programlisting>
 		directly until we convert the DVI file into PostScript. The
 		command sequence goes like this:</para>
 		
-		<informalexample>
+		
 		  <screen>&prompt.user; <userinput>dvips seaweed-analysis.dvi</userinput>
 &prompt.user; <userinput>lpr seaweed-analysis.ps</userinput></screen>
-		</informalexample>
+		
 
 	      <para>By installing a conversion filter for DVI
 		files, we can skip the hand conversion step each time by
 		having LPD do it for us. Now, each time we get a DVI file, we
 		are just one step away from printing it:</para>
 	      
-		<informalexample>
+		
 		  <screen>&prompt.user; <userinput>lpr -d seaweed-analysis.dvi</userinput></screen>
-		</informalexample>
+		
 
 	      <para>We got LPD to do the DVI file conversion
 		for us by specifying the <option>-d</option> option. Section
@@ -4058,19 +4058,19 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	    <para>Then, we just need to make spooling
 	      directories on <hostid>orchid</hostid>:</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>mkdir -p /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput>
 &prompt.root; <userinput>chmod 770 /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput>
 &prompt.root; <userinput>chown daemon.daemon /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput></screen>
-	      </informalexample>
+	      
 	    
 	    <para>Now, users on <hostid>orchid</hostid> can print to
 	      <literal>rattan</literal> and <literal>bamboo</literal>. If, for example, a user on orchid
 	      typed
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.user; <userinput>lpr -P bamboo -d sushi-review.dvi</userinput></screen>
-	      </informalexample> the LPD system on orchid would copy the job
+	       the LPD system on orchid would copy the job
 	      to the spooling directory
 	      <filename>/var/spool/lpd/bamboo</filename> and note that it was
 	      a DVI job. As soon as the host rose has room in its <hostid>bamboo</hostid> spooling directory, the two LPDs
@@ -4181,9 +4181,9 @@ exit 0;</programlisting>
 	      <filename>/etc/printcap</filename> file. When users submit jobs
 	      with the <option>-#</option> option, they will see:</para>
 	      
-	      <informalexample>
+	      
 		<screen>lpr: multiple copies are not allowed</screen>
-	      </informalexample>
+	      
 	    
 	    <para>Note that if you have set up access to a printer remotely
 	      (see section <link linkend="printing-advanced-network-rm">Printers Installed on Remote      Hosts</link>), you need
@@ -4240,9 +4240,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 	      multiple times, or from submitting the same file multiple times
 	      in one job like this:</para>
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.user; <userinput>lpr forsale.sign forsale.sign forsale.sign forsale.sign forsale.sign</userinput></screen>
-	      </informalexample>
+	      
 
 	    <para>There are many ways to prevent this abuse
 	      (including ignoring it) which you are free to explore.</para>
@@ -4458,9 +4458,9 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 		      the amount of free disk space that must exist on the
 		      filesystem for LPD to accept remote jobs:</para>
 		  
-		      <informalexample>
+		      
 			<screen>&prompt.root; <userinput>echo 6144 &gt; /var/spool/lpd/bamboo/minfree</userinput></screen>
-		      </informalexample>
+		      
 		    
 		  </listitem>
 		</varlistentry>
@@ -4613,7 +4613,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
 		<refentrytitle>pac</refentrytitle></citerefentry>. You
 	      will get a dollar-centric summary like the following:</para>
 	    
-	      <informalexample>
+	      
 		<screen>  Login               pages/feet   runs    price
 orchid:kelly                5.00    1   $  0.10
 orchid:mary                31.00    3   $  0.62
@@ -4624,7 +4624,7 @@ rose:mary                  87.00   32   $  1.74
 rose:root                  26.00   12   $  0.52
 
 total                     337.00  154   $  6.74</screen>
-	      </informalexample>
+	      
 
 	    <para>These are the arguments  <citerefentry>
 		<refentrytitle>pac</refentrytitle></citerefentry>
@@ -4701,7 +4701,7 @@ total                     337.00  154   $  6.74</screen>
 	      users can use any host), run <command>pac -m</command>, to
 	      produce the following summary:</para>
 	    
-	      <informalexample>
+	      
 		<screen>  Login               pages/feet   runs    price
 andy                        2.00    1   $  0.04
 kelly                     182.00  105   $  3.64
@@ -4710,7 +4710,7 @@ root                       26.00   12   $  0.52
 zhang                       9.00    1   $  0.18
 
 total                     337.00  154   $  6.74</screen>
-	      </informalexample>
+	      
 
 	    <para>To compute the dollar amount due,
 	      <citerefentry>
@@ -4726,9 +4726,9 @@ total                     337.00  154   $  6.74</screen>
 	      <option>-p</option> option are in dollars, though, not
 	      hundredths of cents. For example,
 	      
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>pac -p1.50</userinput></screen>
-	      </informalexample>
+	      
 
 	      makes each page cost one dollar and fifty
 	      cents. You can really rake in the profits by using this
diff --git a/en/handbook/quotas/chapter.sgml b/en/handbook/quotas/chapter.sgml
index 8d9c3de622..d594296cc4 100644
--- a/en/handbook/quotas/chapter.sgml
+++ b/en/handbook/quotas/chapter.sgml
@@ -96,9 +96,9 @@ check_quotas=YES</programlisting>
 	<para>Once you have configured your system to enable quotas, verify
 	  that they really are enabled. An easy way to do this is to run</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>quota -v</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>You should see a one line summary of
 	  disk usage and current quota limits for each file system that quotas
@@ -137,9 +137,9 @@ check_quotas=YES</programlisting>
 	  editor  if the <envar>EDITOR</envar> variable is not set, to
 	  allow you to edit the quota limits.</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>edquota -u test</userinput></screen>
-	  </informalexample>
+	  
 
 	  <programlisting>
 Quotas for user test:
@@ -174,9 +174,9 @@ Quotas for user test:
 	  following command can be used to duplicate those quota limits for
 	  uids 10,000 through 19,999:</para>
 
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>edquota -p test 10000-19999</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>The ability to specify uid ranges was added to the system after
 	  2.1 was released. If you need this feature on a 2.1 system, you
diff --git a/en/handbook/security/chapter.sgml b/en/handbook/security/chapter.sgml
index ccc28daebc..2bc0726f7a 100644
--- a/en/handbook/security/chapter.sgml
+++ b/en/handbook/security/chapter.sgml
@@ -70,13 +70,13 @@
 	    on a system using the DES versions:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user;<userinput> cd /usr/lib</userinput>
 &prompt.user; <userinput>ls -l /usr/lib/libcrypt*</userinput>
 lrwxr-xr-x  1 bin  bin  13 Sep  5 12:50 libcrypt.a -&gt; libdescrypt.a
 lrwxr-xr-x  1 bin  bin  18 Sep  5 12:50 libcrypt.so.2.0 -&gt; libdescrypt.so.2.0
 lrwxr-xr-x  1 bin  bin  15 Sep  5 12:50 libcrypt_p.a -&gt; libdescrypt_p.a</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>On a system using the MD5-based libraries, the same links will
@@ -171,7 +171,7 @@ lrwxr-xr-x  1 bin  bin  15 Sep  5 12:50 libcrypt_p.a -&gt; libdescrypt_p.a</scre
 	    command without any parameters while logged in as yourself:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; keyinit
 Updating wollman:			) these will not appear if you
 Old key: ha73895  		        ) have not used S/Key before
@@ -182,7 +182,7 @@ If you are using telnet or rlogin exit with no password and use keyinit -s.
 
 wollman s/key is 99 ha73896		) discussed below SAG
 HAS FONT GOUT FATE BOOM		        )</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>There is a lot of information here. At the<prompt>Enter secret
@@ -213,14 +213,14 @@ HAS FONT GOUT FATE BOOM		        )</screen>
 	    <command>keyinit -s</command> command:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>keyinit -s</userinput>
 Updating wollman: Old key: kh94741
 Reminder you need the 6 English words from the skey command.
 <prompt>Enter sequence count from 1 to 9999:</prompt> <userinput>100</userinput>	) I typed this
 <prompt>Enter new key [default kh94742]:</prompt>
 s/key 100 kh94742</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>To accept the default seed (which the <command>keyinit</command> program
@@ -229,12 +229,12 @@ s/key 100 kh94742</screen>
 	    parameters:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>key 100 kh94742</userinput>
 Reminder - Do not use this program while logged in via telnet or rlogin.
 <prompt>Enter secret password:</prompt>             ) I typed my secret password
 HULL NAY YANG TREE TOUT VETO</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>Now switch back over to the insecure connection, and copy the
@@ -243,11 +243,11 @@ HULL NAY YANG TREE TOUT VETO</screen>
 	    program:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen><prompt>s/key access password:</prompt> <userinput>HULL NAY YANG TREE TOUT VETO</userinput>
 ID wollman s/key is 100 kh94742
 HULL NAY YANG TREE TOUT VETO</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>The rest of the description from the previous section applies
@@ -262,14 +262,14 @@ HULL NAY YANG TREE TOUT VETO</screen>
 	    should go over an S/Key login prompt:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>telnet himalia</userinput>
 Trying 18.26.0.186...
 Connected to himalia.lcs.mit.edu.
 Escape character is '^]'.
 s/key 92 hi52030
 <prompt>Password:</prompt></screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>Note that, before prompting for a password, the login program
@@ -302,25 +302,25 @@ s/key 92 hi52030
 	    the end of the line. Thus:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>key 92 hi52030</userinput>		     ) pasted from previous section
 Reminder - Do not use this program while logged in via telnet or rlogin.
 <prompt>Enter secret password:</prompt>		) I typed my secret password
 ADEN BED WOLF HAW HOT STUN</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>And in the other window:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>s/key 92 hi52030				) from previous section
 <prompt>Password:</prompt>
   (turning echo on)
 <prompt>Password:</prompt>ADEN BED WOLF HAW HOT STUN
 Last login: Wed Jun 28 15:31:00 from halloran-eldar.l
 [etc.]</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>This is the easiest mechanism <emphasis>if</emphasis> you have
@@ -341,7 +341,7 @@ Last login: Wed Jun 28 15:31:00 from halloran-eldar.l
 	    be printed out. For example:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.user; <userinput>key -n 25 57 zz99999</userinput>
 Reminder - Do not use this program while logged in via telnet or rlogin.
 <prompt>Enter secret password:</prompt>
@@ -350,7 +350,7 @@ Reminder - Do not use this program while logged in via telnet or rlogin.
 &hellip;
 56: AMOS BOWL LUG FAT CAIN INCH
 57: GROW HAYS TUN DISH CAR BALM</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>The <option>-n 25</option> requests twenty-five keys in
@@ -453,11 +453,11 @@ permit port ttyd0</programlisting>
 	    check that only the following files are present:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /etc/kerberosIV</userinput>
 &prompt.root; <userinput>ls</userinput>
 README		krb.conf        krb.realms</screen>
-	    </informalexample>
+	    
 	  
 	  
 	  <para>If any additional files (such as
@@ -473,7 +473,7 @@ README		krb.conf        krb.realms</screen>
 	    <filename>grunt.grondar.za</filename>. We edit or create the
 	    <filename>krb.conf</filename> file:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cat krb.conf</userinput>
 GRONDAR.ZA
 GRONDAR.ZA grunt.grondar.za admin server
@@ -485,7 +485,7 @@ ATHENA.MIT.EDU kerberos-3.mit.edu
 LCS.MIT.EDU kerberos.lcs.mit.edu
 TELECOM.MIT.EDU bitsy.mit.edu
 ARC.NASA.GOV trident.arc.nasa.gov</screen>
-	  </informalexample>
+	  
 	  
 	  <para>In this case, the other realms do not need to be there. They
 	    are here as an example of how a machine may be made aware of
@@ -507,14 +507,14 @@ ARC.NASA.GOV trident.arc.nasa.gov</screen>
 	    <filename>krb.realms</filename> file would be updated as
 	    follows:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cat krb.realms</userinput>
 grunt.grondar.za GRONDAR.ZA
 .grondar.za GRONDAR.ZA
 .berkeley.edu CS.BERKELEY.EDU
 .MIT.EDU ATHENA.MIT.EDU
 .mit.edu ATHENA.MIT.EDU</screen>
-	  </informalexample>
+	  
 	  
 	  <para>Again, the other realms do not need to be there. They are here
 	    as an example of how a machine may be made aware of multiple
@@ -528,19 +528,19 @@ grunt.grondar.za GRONDAR.ZA
 	    run on the Kerberos server (or Key Distribution Centre). Issue the
 	    <command>kdb_init</command> command to do this:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>kdb_init</userinput>
 <prompt>Realm name [default  ATHENA.MIT.EDU ]:</prompt> <userinput>GRONDAR.ZA</userinput>
 You will be prompted for the database Master Password.
 It is important that you NOT FORGET this password.
 		
 <prompt>Enter Kerberos master key:</prompt> </screen>
-	  </informalexample>
+	  
 	  
 	  <para>Now we have to save the key so that servers on the local
 	    machine can pick it up. Use the <command>kstash</command> command to do this.</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>kstash</userinput>
 	      
 <prompt>Enter Kerberos master key:</prompt>
@@ -548,7 +548,7 @@ It is important that you NOT FORGET this password.
 Current Kerberos master key version is 1.
 
 Master key entered. BEWARE!</screen>
-	  </informalexample>
+	  
 	  
 	  <para>This saves the encrypted master password in
 	    <filename>/etc/kerberosIV/master_key</filename>.</para>
@@ -572,7 +572,7 @@ Master key entered. BEWARE!</screen>
 	  <para>Now let's add these entries:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>kdb_edit</userinput>
 Opening database...
 
@@ -621,7 +621,7 @@ Principal's new key version = 1
 <prompt>Attributes [ 0 ] ?</prompt>
 Edit O.K.
 <prompt>Principal name:</prompt>         &lt;---- null entry here will cause an exit</screen>
-	    </informalexample>
+	    
 	  
 	  
 	</sect2>
@@ -637,7 +637,7 @@ Edit O.K.
 	    directory. This file must be present on each server and client,
 	    and is crucial to the operation of Kerberos.</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>ext_srvtab grunt</userinput>
 <prompt>Enter Kerberos master key:</prompt>
 		
@@ -645,16 +645,16 @@ Current Kerberos master key version is 1.
 
 Master key entered. BEWARE!
 Generating 'grunt-new-srvtab'....</screen>
-	  </informalexample>
+	  
 	  
 	  <para>Now, this command only generates a temporary file which must
 	    be renamed to <filename>srvtab</filename> so that all the
 	    server can pick it up. Use the <command>mv</command>
 	    command to move it into place on the original system:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>mv grunt-new-srvtab srvtab</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>If the file is for a client system, and the network is not
 	    deemed safe, then copy the <filename><replaceable>client</replaceable>-new-srvtab</filename> to removable media
@@ -663,10 +663,10 @@ Generating 'grunt-new-srvtab'....</screen>
 	    <filename>/etc/kerberosIV</filename> directory, and make sure it
 	    is mode 600:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>mv grumble-new-srvtab srvtab</userinput>
 &prompt.root; <userinput>chmod 600 srvtab</userinput></screen>
-	  </informalexample>
+	  
 	</sect2>
 	
 	<sect2>
@@ -676,7 +676,7 @@ Generating 'grunt-new-srvtab'....</screen>
 	    let's create an entry for the user <username>jane</username>. Use
 	    the <command>kdb_edit</command> command to do this:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>kdb_edit</userinput>
 Opening database...
 
@@ -704,7 +704,7 @@ Principal's new key version = 1
 <prompt>Attributes [ 0 ] ?</prompt>
 Edit O.K.
 <prompt>Principal name:</prompt>		   &lt;---- null entry here will cause an exit</screen>
-	  </informalexample>
+	  
 	</sect2>
 	
 	<sect2>
@@ -717,7 +717,7 @@ Edit O.K.
 	    automagically get what they need from the
 	    <filename>/etc/kerberosIV</filename> directory.</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>kerberos &amp;</userinput>
 Kerberos server starting
 Sleep forever on error
@@ -736,33 +736,33 @@ regular kill instead
 Current Kerberos master key version is 1.
 
 Master key entered.  BEWARE!</screen>
-	  </informalexample>
+	  
 	  
 	  <para>Now we can try using the <command>kinit</command>
 	    command to get a ticket for the id <username>jane</username> that we created above:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>kinit jane</userinput>
 MIT Project Athena (grunt.grondar.za)
 Kerberos Initialization for "jane"
 <prompt>Password:</prompt> </screen>
-	  </informalexample>
+	  
 	  
 	  <para>Try listing the tokens using <command>klist</command> to see if we really have them:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>klist</userinput>
 Ticket file:    /tmp/tkt245
 Principal:      jane@GRONDAR.ZA
 
   Issued           Expires          Principal
 Apr 30 11:23:22  Apr 30 19:23:22  krbtgt.GRONDAR.ZA@GRONDAR.ZA</screen>
-	  </informalexample>
+	  
 	  
 	  <para>Now try changing the password using <command>passwd</command> to check if the kpasswd daemon can
 	    get authorization to the Kerberos database:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>passwd</userinput>
 realm GRONDAR.ZA
 <prompt>Old password for jane:</prompt>
@@ -770,7 +770,7 @@ realm GRONDAR.ZA
 Verifying password
 <prompt>New Password for jane:</prompt>
 Password changed.</screen>
-	  </informalexample>
+	  
 	</sect2>
 	
 	<sect2>
@@ -784,7 +784,7 @@ Password changed.</screen>
 	    entry <literal>jane.root</literal> in the Kerberos
 	    database:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>kdb_edit</userinput>
 Opening database...
 
@@ -813,42 +813,42 @@ Principal's new key version = 1
 <prompt>Attributes [ 0 ] ?</prompt>
 Edit O.K.
 <prompt>Principal name:</prompt>		         &lt;---- null entry here will cause an exit</screen>
-	  </informalexample>
+	  
 	  
 	  <para>Now try getting tokens for it to make sure it works:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>kinit jane.root</userinput>
 MIT Project Athena (grunt.grondar.za)
 Kerberos Initialization for "jane.root"
 <prompt>Password:</prompt></screen>
-	  </informalexample>
+	  
 	  
 	  <para>Now we need to add the user to root's
 	    <filename>.klogin</filename> file:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cat /root/.klogin</userinput>
 jane.root@GRONDAR.ZA</screen>
-	  </informalexample>
+	  
 	  	  
 	  <para>Now try doing the <command>su</command>:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <prompt>su</prompt>
 <prompt>Password:</prompt></screen>
-	  </informalexample>
+	  
 	  
 	  <para>and take a look at what tokens we have:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; klist
 Ticket file:	/tmp/tkt_root_245
 Principal:      jane.root@GRONDAR.ZA
 
   Issued           Expires          Principal
 May  2 20:43:12  May  3 04:43:12  krbtgt.GRONDAR.ZA@GRONDAR.ZA</screen>
-	  </informalexample>
+	  
 	</sect2>
 	
 	<sect2>
@@ -862,19 +862,19 @@ May  2 20:43:12  May  3 04:43:12  krbtgt.GRONDAR.ZA@GRONDAR.ZA</screen>
 	    <literal>&lt;username&gt;</literal> to <command>su</command> to root if the necessary entries are in
 	    the <filename>.klogin</filename> file in <username>root</username>'s home directory:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>cat /root/.klogin</userinput>
 jane.root@GRONDAR.ZA</screen>
-	  </informalexample>
+	  
 	  
 	  <para>Likewise, if a user has in their own home directory lines of
 	    the form:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>cat ~/.klogin</userinput>
 jane@GRONDAR.ZA
 jack@GRONDAR.ZA</screen>
-	  </informalexample>
+	  
 	  
 	  <para>This allows anyone in the <filename>GRONDAR.ZA</filename>
 	    realm who has authenticated themselves to
@@ -888,7 +888,7 @@ jack@GRONDAR.ZA</screen>
 	  <para>For example, Jane now logs into another system, using
 	    Kerberos:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>kinit</userinput>
 MIT Project Athena (grunt.grondar.za)
 <prompt>Password:</prompt>
@@ -898,14 +898,14 @@ Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
         The Regents of the University of California.   All rights reserved.
 
 FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
-	  </informalexample>
+	  
 	  
 	  <para>Or Jack logs into Jane's account on the same machine (Jane
 	    having set up the <filename>.klogin</filename> file as above, and
 	    the person in charge of Kerberos having set up principal
 	    <emphasis>jack</emphasis> with a null instance:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.user; <userinput>kinit</userinput>
 &prompt.user; <userinput>rlogin grunt -l jane</userinput>
 MIT Project Athena (grunt.grondar.za)
@@ -914,7 +914,7 @@ Last login: Mon May  1 21:16:55 from grumble
 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
         The Regents of the University of California.   All rights reserved.
 FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
-	  </informalexample>
+	  
 	</sect2>
       </sect1>
       
@@ -1113,9 +1113,9 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
 		    counter using the <citerefentry><refentrytitle>ipfw</refentrytitle><manvolnum>8</manvolnum></citerefentry>
 		    utility:</para>
 		  
-		  <informalexample>
+		  
 		    <screen>&prompt.root; <userinput>ipfw zero 4500</userinput></screen>
-		  </informalexample>
+		  
 		  
 		  <para>Where 4500 is the chain entry you wish to continue
 		    logging.</para>
@@ -1319,21 +1319,21 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
 	    <para>The syntax used to specify an
 	      <replaceable>address/mask</replaceable> is:
 	      
-	      <informalexample>
+	      
 		<screen><replaceable>address</replaceable></screen>
-	      </informalexample>
+	      
 
 	      or
 	      
-	      <informalexample>
+	      
 		<screen><replaceable>address</replaceable>/<replaceable>mask-bits</replaceable></screen>
-	      </informalexample>
+	      
 	      
 	      or
 
-	      <informalexample>
+	      
 		<screen><replaceable>address</replaceable>:<replaceable>mask-pattern</replaceable></screen>
-	      </informalexample></para>
+	      </para>
 	    
 	    <para>A valid hostname may be specified in place of the IP
 	      address. <option><replaceable>mask-bits</replaceable></option> is a decimal
@@ -1539,42 +1539,42 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
 	    host <hostid role="fqdn">nice.people.org</hostid> by being forwarded by
 	    the router:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root <userinput>ipfw add deny tcp from evil.crackers.org to nice.people.org 23</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>The next example denies and logs any TCP traffic from the
 	    entire <hostid role="domainname">crackers.org</hostid> network (a class C) to the
 	    <hostid role="fqdn">nice.people.org</hostid> machine (any port).</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>ipfw add deny log tcp from evil.crackers.org/24 to nice.people.org</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>If you do not want people sending X sessions to your internal
 	    network (a subnet of a class C), the following command will do the
 	    necessary filtering:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>ipfw add deny tcp from any to my.org/28 6000 setup</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>To see the accounting records:
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>ipfw -a list</userinput></screen>
-	    </informalexample> or in the short form
+	     or in the short form
+	    
 	    
-	    <informalexample>
 	      <screen>&prompt.root; <userinput>ipfw -a l</userinput></screen>
-	    </informalexample></para>
+	    </para>
 
 	  <para>You can also see the last time a chain entry
 	    was matched with:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>ipfw -at l</userinput></screen>
-	    </informalexample>
+	    
 	  
 	</sect2>
 	
@@ -1623,9 +1623,9 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
 	    you. There is currently no support in the <command>ipfw</command> utility for loading multiple rules in
 	    the one command. The system I use is to use the command:</para>
 	  
-	  <informalexample>
+	  
 	    <screen>&prompt.root; <userinput>ipfw list</userinput></screen>
-	  </informalexample>
+	  
 	  
 	  <para>to write a list of the current rules out to a file, and then
 	    use a text editor to prepend <literal>ipfw
diff --git a/en/handbook/serialcomms/chapter.sgml b/en/handbook/serialcomms/chapter.sgml
index f2d114ce25..d6b6a4415c 100644
--- a/en/handbook/serialcomms/chapter.sgml
+++ b/en/handbook/serialcomms/chapter.sgml
@@ -17,9 +17,9 @@
 	  default set of terminal I/O settings. You can see these settings
 	  with the command</para>
 
-	  <informalexample>
+	  
             <screen>&prompt.root; <userinput>stty -a -f /dev/ttyd1</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>When you change the settings to this device, the settings are in
 	  effect until the device is closed. When it is reopened, it goes
@@ -28,9 +28,9 @@
 	  For example, to turn on <acronym>CLOCAL</acronym> mode, 8 bits, and
 	  <emphasis>XON/XOFF</emphasis> flow control by default for ttyd5, do:</para>
 
-	  <informalexample>
+	  
             <screen>&prompt.root; <userinput>stty -f /dev/ttyid5 clocal cs8 ixon ixoff</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>A good place to do this is in
 	  <filename>/etc/rc.serial</filename>. Now, an application will have
@@ -42,9 +42,9 @@
 	  example, to lock the speed of <filename>ttyd5</filename> to 57600
 	  bps, do</para>
 
-	  <informalexample>
+	  
             <screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
-	  </informalexample>
+	  
 	
 	<para>Now, an application that opens <filename>ttyd5</filename> and
 	  tries to change the speed of the port will be stuck with 57600
@@ -665,9 +665,9 @@ ttyd5   "/usr/libexec/getty std.19200"   vt100 on insecure # Guest bathroom</pro
 	    
 	    <para>So, after you have saved your changes to
 	      <filename>/etc/ttys</filename>, send <literal>SIGHUP</literal> to <command>init</command> by typing:</para>
-	      <informalexample>
+	      
 		<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
-	      </informalexample>
+	      
 
 	    <para>(The <command>init</command>
 	      process <emphasis>always</emphasis> has process ID 1.)</para>
@@ -708,14 +708,14 @@ ttyd5   "/usr/libexec/getty std.19200"   vt100 on insecure # Guest bathroom</pro
 		  <para>Make sure that a <command>getty</command>
 		    process is running and serving the terminal. Type
 		  
-		    <informalexample>
+		    
 		      <screen>&prompt.root; <userinput>ps -axww|grep getty</userinput></screen>
-		    </informalexample> to get a list of running <command>getty</command> processes. You should see an
+		     to get a list of running <command>getty</command> processes. You should see an
 		    entry for the terminal. For example, the display
 		  
-		    <informalexample>
+		    
 		      <screen>22189  d1  Is+    0:00.03 /usr/libexec/getty std.38400 ttyd1</screen>
-		    </informalexample> shows that a <command>getty</command> is running on the second
+		     shows that a <command>getty</command> is running on the second
 		    serial port <literal>ttyd1</literal> and is
 		    using the <literal>std.38400</literal> entry in
 		    <filename>/etc/gettytab</filename>.</para>
@@ -995,9 +995,9 @@ ttyd5   "/usr/libexec/getty std.19200"   vt100 on insecure # Guest bathroom</pro
 	    show this:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen> 4850 ??  I      0:00.09 /usr/libexec/getty V19200 ttyd0</screen>
-	    </informalexample>
+	    
 	  
 	  <para>When a user dials the modem's line and the modems connect, the
 	    <acronym>CD</acronym> line is asserted by the modem. The kernel
@@ -1041,15 +1041,15 @@ ttyd5   "/usr/libexec/getty std.19200"   vt100 on insecure # Guest bathroom</pro
 	    to view just the messages that have the word <literal>sio</literal>, use the command:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>/sbin/dmesg | grep 'sio'</userinput></screen>
-	    </informalexample>
+	    
 	  
 	  <para>For example, on a system with four serial ports, these are the
 	    serial-port specific kernel boot messages:</para>
 	  
 	  
-	    <informalexample>
+	    
 	      <screen>sio0 at 0x3f8-0x3ff irq 4 on isa
 sio0: type 16550A
 sio1 at 0x2f8-0x2ff irq 3 on isa
@@ -1058,7 +1058,7 @@ sio2 at 0x3e8-0x3ef irq 5 on isa
 sio2: type 16550A
 sio3 at 0x2e8-0x2ef irq 9 on isa
 sio3: type 16550A</screen>
-	    </informalexample>
+	    
 	  
 	  <para>If your kernel does not recognize all of your serial ports,
 	    you will probably need to configure a custom FreeBSD kernel for
@@ -1171,11 +1171,11 @@ device		sio3    at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
 	      permissions on the <filename>/dev/cua*</filename> files should
 	      be sufficient:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>crw-rw----    1 uucp     dialer    28, 129 Feb 15 14:38 /dev/cua01
 crw-rw----    1 uucp     dialer    28, 161 Feb 15 14:38 /dev/cuai01
 crw-rw----    1 uucp     dialer    28, 193 Feb 15 14:38 /dev/cual01</screen>
-	    </informalexample>
+	    
 	    
 	    <para>These permissions allow the user <username>uucp</username>
 	      and users in the group <username>dialer</username> to use the call-out devices.</para>
@@ -1390,9 +1390,9 @@ ttyd0   "/usr/libexec/getty xxx"   dialup on</programlisting>
 	      <filename>/etc/ttys</filename>, you may send the <command>init</command> process a <acronym>HUP</acronym>
 	      signal to re-read the file. You can use the command
 	    
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>kill -1 1</userinput></screen>
-	    </informalexample>
+	    
 	    
 	    to send the signal. If this is your first time setting up
 	      the system, though, you may want to wait until your modem(s) are
@@ -1667,16 +1667,16 @@ AT&amp;B2&amp;W</programlisting>
 	      You should see a lines like this among the processes
 	      displayed:</para>
 	    
-	    <informalexample>
+	    
 	      <screen>  114 ??  I      0:00.10 /usr/libexec/getty V19200 ttyd0
   115 ??  I      0:00.10 /usr/libexec/getty V19200 ttyd1</screen>
-	    </informalexample>
+	    
 	    
 	    <para>If you see something different, like this:
 	    
-	    <informalexample>
+	    
 	      <screen>  114 d0  I      0:00.10 /usr/libexec/getty V19200 ttyd0</screen>
-	    </informalexample>
+	    
 	    
 	    and the modem has not accepted a call yet, this means that
 	      <command>getty</command> has completed its open on
@@ -1806,9 +1806,9 @@ AT&amp;B2&amp;W</programlisting>
 	  <para>Alternatively, you can let everyone on your system run
 	    <command>tip</command> and <command>cu</command> by typing:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>chmod 4511 /usr/bin/tip</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>You do not have to run
 	    this command for <command>cu</command>, since <command>cu</command> is just a hard link to <command>tip</command>.</para>
@@ -1869,16 +1869,16 @@ cuaa0:dv=/dev/cuaa0:br#19200:pa=none</programlisting>
 	  <para>If there is no <filename>/dev/cuaa0</filename> on your system,
 	    do this:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>MAKEDEV cuaa0</userinput></screen>
-	    </informalexample>
+	    
 	  
 	  <para>Or use cu as root with the following command:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
-	    </informalexample>
+	    
 
 	  <para><replaceable>line</replaceable> is the
 	    serial port (e.g.<filename>/dev/cuaa0</filename>) and <replaceable>speed</replaceable> is
@@ -1917,9 +1917,9 @@ tip57600|Dial any phone number at 57600 bps:\
 	  
 	  <para>Then you can things like:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>tip -115200 5551234</userinput></screen>
-	    </informalexample>
+	    
 
 	  <para>If you prefer <command>cu</command> over <command>tip</command>,
 	    use a generic cu entry:
@@ -1929,9 +1929,9 @@ cu115200|Use cu to dial any number at 115200bps:\
         :dv=/dev/cuaa1:br#57600:at=hayes:pa=none:du:</programlisting>
 	    and type:</para>
 
-	    <informalexample>
+	    
 	      <screen>&prompt.root; <userinput>cu 5551234 -s 115200</userinput></screen>
-	    </informalexample>
+	    
 	</sect2>
 	
 	<sect2>