Gobs of small tweaks and cleanups.

Submitted by:	Philippe Charnier <charnier@lirmm.fr>

handbook/dialup.sgml

@@ -1,6 +1,6 @@
 <!-- This is an SGML document in the linuxdoc DTD of the Tutorial for
      Configuring a FreeBSD for Dialup Services by Guy Helmer.
-     $Id: dialup.sgml,v 1.3 1995-08-29 01:42:35 jfieber Exp $
+     $Id: dialup.sgml,v 1.4 1995-12-04 17:58:37 jfieber Exp $
 
 <!DOCTYPE linuxdoc PUBLIC "-//Linux//DTD linuxdoc//EN">
 
@@ -208,7 +208,7 @@ messages while the kernel is booting, or use the
 <tt>/sbin/dmesg</tt> command to replay the kernel's boot messages.  In
 particular, look for messages that start with the characters <tt/sio/.
 Hint: to view just the messages that have the word <tt/sio/, use the
-command 
+command: 
 
 <tscreen><verb>
 /usr/sbin/dmesg | grep 'sio'
@@ -247,7 +247,7 @@ already) by <tt/cd/ing to <tt>/sys/i386/conf</tt>.  Then, if you are
 creating a new custom configuration file, copy the file GENERICAH (or
 GENERICBT, if you have a BusTek SCSI controller on FreeBSD 1.x) to
 <em/YOURSYS/, where <em/YOURSYS/ is the name of your system, but in
-upper-case letters.  Edit the file, and change the device lines
+upper-case letters.  Edit the file, and change the device lines:
 
 <tscreen><verb>
 device		sio0	at isa? port "IO_COM1" tty irq 4 vector siointr
@@ -790,9 +790,10 @@ the <tt/DTR/ line is asserted by checking the modem's indicator lights
 
 If you've gone over everything several times and it still doesn't work,
 take a break and come back to it later.  If it still doesn't work,
-perhaps you can send an electronic mail message to
+perhaps you can send an electronic mail message to <tt><htmlurl
-<tt>FreeBSD-Questions@freebsd.org</tt> describing your modem and your
+url="mailto:questions@freebsd.org" name="questions@FreeBSD.ORG"></tt>
-problem, and the good folks on the list will try to help.
+describing your modem and your problem, and the good folks on the list will
+try to help.
 
 <sect1><heading>Acknowledgements</heading>
 <p>

handbook/esdi.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: esdi.sgml,v 1.3 1995-11-25 20:00:45 jkh Exp $ -->
+<!-- $Id: esdi.sgml,v 1.4 1995-12-04 17:58:38 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -276,7 +276,7 @@
 	these bad blocks, it writes a table with the offending block
 	numbers to the end of the FreeBSD slice. 
 
-	When the disk is in operation, the diskaccesses are checked 
+	When the disk is in operation, the disk accesses are checked 
 	against the table read from the disk. Whenever a blocknumber
 	is requested that is in the bad144 list, a replacement block
 	(also from the end of the FreeBSD slice) is used.

handbook/install.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: install.sgml,v 1.19 1995-11-29 09:45:13 tg Exp $ -->
+<!-- $Id: install.sgml,v 1.20 1995-12-04 17:58:40 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -349,7 +349,7 @@ Boot:
 	  boot into the CD installation directly from DOS using Walnut Creek's
 	  supplied ``install.bat'' batch file or you can make a boot floppy with
 	  the ``makeflp.bat'' command [NOTE: If you're using an IDE CDROM, use
-	  the inst_ide.bat or atapiflp.bat batch files instead].
+	  the inst&lowbar;ide.bat or atapiflp.bat batch files instead].
 
 	  For the easiest interface of all (from DOS), type
 	  ``view''.  This will bring up a DOS menu utility that

handbook/kernelconfig.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: kernelconfig.sgml,v 1.3 1995-12-04 13:39:32 jfieber Exp $ -->
+<!-- $Id: kernelconfig.sgml,v 1.4 1995-12-04 17:58:41 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 <!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
   <chapt><heading>Configuring the FreeBSD Kernel<label id="kernelconfig"></heading>
@@ -107,6 +107,7 @@
 <tscreen><verb>
 # /usr/sbin/config MYKERNEL
 # cd ../../compile/MYKERNEL
+# make depend
 # make
 # make install
 </verb></tscreen>

handbook/nfs.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: nfs.sgml,v 1.3 1995-09-27 00:46:23 jmz Exp $ -->
+<!-- $Id: nfs.sgml,v 1.4 1995-12-04 17:58:42 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>NFS<label id="nfs"></heading>
@@ -39,13 +39,13 @@ system.  In all cases, note that additional options, such as "hard" or
 "soft" and "bg" may be desirable in your application.
 
 Examples for the FreeBSD system ("freebox") as the client:
-    in /etc/fstab on freebox:
+    in <tt>/etc/fstab</tt> on freebox:
 fastws:/sharedfs /project nfs rw,rsize=1024 0 0
     as a manual mount command on freebox:
 mount -t nfs -o rsize=1024 fastws:/sharedfs /project
 
 Examples for the FreeBSD system as the server:
-    in /etc/fstab on fastws:
+    in <tt>/etc/fstab</tt> on fastws:
 freebox:/sharedfs /project nfs rw,wsize=1024 0 0
     as a manual mount command on fastws:
 mount -t nfs -o wsize=1024 freebox:/sharedfs /project

handbook/porting.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: porting.sgml,v 1.9 1995-12-04 08:11:58 asami Exp $ -->
+<!-- $Id: porting.sgml,v 1.10 1995-12-04 17:58:44 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Porting applications<label id="porting"></heading>
@@ -16,7 +16,7 @@
 	that file for more details.
 
     <sect1>
-      <heading>Before Starting the Port</heading>
+      <heading>Before Starting the Port<label id="porting:starting"></heading>
 
       <p>Note: Only a fraction of the overridable variables are
 	mentioned in this document. Most (if not all) are documented
@@ -125,7 +125,7 @@
  # Date created:		5 December 1994
  # Whom:			asami
  #
- # $Id: porting.sgml,v 1.9 1995-12-04 08:11:58 asami Exp $
+ # $Id: porting.sgml,v 1.10 1995-12-04 17:58:44 jfieber Exp $
  #
  
  DISTNAME=	oneko-1.1b
@@ -411,7 +411,7 @@ ftp://freefall.freebsd.org/pub/FreeBSD/LOCAL_PORTS/
 	  the directory your port's tarball unpacks itself into, that
 	  being where the make is done).  To make fixes and upgrades
 	  easier you should avoid having more than one patch fix the
-	  same file (e.g., patch-ab and patch-ab both changing
+	  same file (e.g., patch-aa and patch-ab both changing
 	  <tt>&dollar;{WRKSRC}</tt>/foobar.c).
 
       <sect2>
@@ -880,7 +880,7 @@ lib/libtcl.so.7.3
   person who wrote this Makefile]
  # Whom:			Satoshi Asami <asami@FreeBSD.ORG>
  #
- # $Id: porting.sgml,v 1.9 1995-12-04 08:11:58 asami Exp $
+ # $Id: porting.sgml,v 1.10 1995-12-04 17:58:44 jfieber Exp $
  [ ^^^^ don't worry about this...it will be automatically filled in by CVS when 
   it is committed to our repository]
  #

handbook/ports.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: ports.sgml,v 1.7 1995-09-27 00:46:26 jmz Exp $ -->
+<!-- $Id: ports.sgml,v 1.8 1995-12-04 17:58:45 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>The Ports collection<label id="ports"></heading>
@@ -32,7 +32,7 @@ those shell scripts, Makefiles and source code ``diffs'' that are
 necessary to configure and compile the program under FreeBSD.  This
 keeps the entire system down to a manageable size, with the current
 system having over 300 ports in the master source tree and yet taking
-up less than ten megabytes.
+up less than twenty megabytes.
 
 
 <sect1><heading>How does the system compile with no source code?</heading>
@@ -134,10 +134,8 @@ going to the top of the tree and typing ``make fetch''.
 
 <sect1><heading>I've ported a program and I want to make a port out of it. What now?</heading>
 
-<p>   See the file GUIDELINES, in:
+<p>   See the <ref id="porting:starting" name="guidelines"> that
-	   ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/GUIDELINES
+      contain details of the procedure and structure involved.
-   This contains details of the procedure and structure involved.
-
 
 <sect1><heading>I've got a good port, what now?</heading>
 

handbook/ppp.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: ppp.sgml,v 1.5 1995-09-27 00:46:27 jmz Exp $ -->
+<!-- $Id: ppp.sgml,v 1.6 1995-12-04 17:58:46 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Setting up kernel PPP<label id="ppp"></heading>
@@ -17,17 +17,17 @@ world via PPP serial connection or modem line.
 <item> as a "server" , i.e. your machine is located on the network and
 used to connect other computers using PPP.
 </enum>
-In both cases you will need to set up an options file ( /etc/ppp/options
+In both cases you will need to set up an options file (<tt>/etc/ppp/options</tt>
-or ~/.ppprc if you have more then one user on your machine that uses
+or <tt>~/.ppprc</tt> if you have more then one user on your machine that uses
-PPP ).
+PPP).
 
 You also will need some modem/serial software ( preferably kermit )
 so you can dial and establish connection with remote host.
 
 <sect1><heading>Working as a PPP client</heading>
 
-<p>I used the following /etc/ppp/options to connect to CISCO terminal server PPP
+<p>I used the following <tt>/etc/ppp/options</tt> to connect to CISCO terminal
-line.
+server PPP line.
 <verb>
 crtscts		# enable hardware flow control
 modem		# modem control line
@@ -62,10 +62,10 @@ on the remote host )
 </enum>
 
 Now your computer is connected with PPP. If the connection fails for some
-reasons you can add the "debug" option to the /etc/ppp/options file
+reasons you can add the "debug" option to the <tt>/etc/ppp/options</tt> file
 and check messages on the console to track the problem
 
-Following /etc/ppp/pppup script will make all 3 stages automatically:
+Following <tt>/etc/ppp/pppup</tt> script will make all 3 stages automatically:
 <verb>
 #!/bin/sh 
 ps ax |grep pppd |grep -v grep
@@ -88,11 +88,11 @@ kermit -y /etc/ppp/kermit.dial
 pppd /dev/tty01 19200
 </verb>
 
-/etc/ppp/kermit.dial is kermit script that dials and makes all
+<tt>/etc/ppp/kermit.dial</tt> is kermit script that dials and makes all
 necessary authorization on the remote host.
 ( Example of such script is attached to the end of this document )
 
-Use the following /etc/ppp/pppdown script to disconnect the PPP line:
+Use the following <tt>/etc/ppp/pppdown</tt> script to disconnect the PPP line:
 <verb>
 #!/bin/sh
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
@@ -114,7 +114,7 @@ kermit -y /etc/ppp/kermit.hup
 /etc/ppp/ppptest
 </verb>
 
-Check if PPP is still running (/usr/etc/ppp/ppptest):
+Check if PPP is still running (<tt>/usr/etc/ppp/ppptest</tt>):
 <verb>
 #!/bin/sh
 pid=`ps ax| grep pppd |grep -v grep|awk '{print $1;}'`
@@ -128,7 +128,7 @@ netstat -n -I ppp0
 ifconfig ppp0
 </verb>
 
-Hangs up modem line (/etc/ppp/kermit.hup):
+Hangs up modem line (<tt>/etc/ppp/kermit.hup</tt>):
 <verb>
 set line /dev/tty01	; put your modem device here
 set speed 19200
@@ -152,7 +152,7 @@ exit
 
 <sect1><heading>Working as a PPP server</heading>
 
-<p>/etc/ppp/options:
+<p><tt>/etc/ppp/options</tt>:
 <verb>
 crtscts				# Hardware flow control
 netmask 255.255.255.0		# netmask ( not required )
@@ -167,7 +167,8 @@ passive				# wait for LCP
 modem				# modem line
 </verb>
 
-Following /etc/ppp/pppserv script will enable ppp server on your machine
+Following <tt>/etc/ppp/pppserv</tt> script will enable ppp server on your
+machine
 <verb>
 #!/bin/sh 
 ps ax |grep pppd |grep -v grep
@@ -194,7 +195,7 @@ kermit -y /etc/ppp/kermit.ans
 pppd /dev/tty01 19200
 </verb>
 
-Use this /etc/ppp/pppservdown script to stop ppp server:
+Use this <tt>/etc/ppp/pppservdown</tt> script to stop ppp server:
 <verb>
 #!/bin/sh 
 ps ax |grep pppd |grep -v grep
@@ -216,7 +217,7 @@ kermit -y /etc/ppp/kermit.noans
 </verb>
 
 Following kermit script will enable/disable autoanswer mode 
-on your modem (/etc/ppp/kermit.ans):
+on your modem (<tt>/etc/ppp/kermit.ans</tt>):
 <verb>
 set line /dev/tty01
 set speed 19200
@@ -243,8 +244,8 @@ echo \13
 exit
 </verb>
 
-This /etc/ppp/kermit.dial script is used for dialing and authorizing on remote host.
+This <tt>/etc/ppp/kermit.dial</tt> script is used for dialing and authorizing
-You will need to customize it for your needs.
+on remote host. You will need to customize it for your needs.
 Put your login and password in this script , also you'll need
 to change input statement depending on responses from your modem
 and remote host.

handbook/printing.sgml

@@ -1,7 +1,7 @@
 <!-- This is an SGML document in the linuxdoc DTD describing
      Printing with FreeBSD.  By Sean Kelly, 1995.
 
-     $Id: printing.sgml,v 1.2 1995-10-01 22:16:19 jfieber Exp $
+     $Id: printing.sgml,v 1.3 1995-12-04 17:58:47 jfieber Exp $
 
      The FreeBSD Documentation Project
 
@@ -1114,7 +1114,6 @@ exit 2
 !"#$%&ero;'()*+,-./01234
                         "#$%&ero;'()*+,-./012345
                                                 #$%&ero;'()*+,-./0123456
-                                                                        $%&ero;'()*+,-./01234567
 </verb></tscreen>
 		  You've become another victim of the <em/staircase
 		  effect/, caused by conflicting interpretations of
@@ -3208,7 +3207,7 @@ lpr -P bamboo -d sushi-review.dvi
 	    lets you send data to it as if you were using a serial or
 	    parallel port (the cheaper version).  This section tells
 	    how to use the cheaper version.  For the more expensive
-	    version, see the previous section <ref name="Printers
+	    one, see the previous section <ref name="Printers
 	    Installed on Remote Hosts" id="printing:advanced:network:rm">.
 
 	    The format of the <tt>/etc/printcap</tt> file lets you
@@ -3815,7 +3814,7 @@ pac -p1.50
 	there (and work with FreeBSD)?''
 
 	Unfortunately, I've located only <em/two/ alternatives---and
-	they're almost identical to each other!  They are
+	they're almost identical to each other!  They are:
 	<descrip>
 	  <tag/PLP, the Portable Line Printer Spooler System/
 

handbook/scsi.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: scsi.sgml,v 1.9 1995-11-25 20:00:49 jkh Exp $ -->
+<!-- $Id: scsi.sgml,v 1.10 1995-12-04 17:58:50 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -453,7 +453,7 @@
           and, last but not least, have more capacity. You can imagine that
           the value reported by the drive when inquiring about the geometry
           now becomes suspect at best, and nearly always misleading. When
-	  asked fro a geometry , it is nearly always better to supply the
+	  asked for a geometry , it is nearly always better to supply the
 	  geometry used by the BIOS, or <em>if the BIOS is never going to know
 	  about this disk</em>, (e.g. it is not a booting disk) to supply a
 	  ficticious geometry that is convenient.
@@ -569,7 +569,7 @@ device cd0 at scbus?			[the first ever CDROM found, no wiring]
 	  the first SCSI disk it finds to sd0, the second disk to sd1
 	  etc. If you ever removed or added a disk, all other devices
 	  of the same type (disk in this case) would 'move around'.
-	  This implies you have to change /etc/fstab each time.
+	  This implies you have to change <tt>/etc/fstab</tt> each time.
 
 	  Although the old style still works, you 
 	  are <em>strongly</em> recommended to use this new feature.
@@ -579,17 +579,20 @@ device cd0 at scbus?			[the first ever CDROM found, no wiring]
 	  pre-FreeBSD2.0.5.R system check this out.
 
           <verb>
-controller      ahb0    at isa? bio irq 11 vector ahbintr	&lsqb;driver for Adaptec 174x&rsqb;
+&lsqb;driver for Adaptec 174x&rsqb;
-controller      aha0    at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr &lsqb;for Adaptec 154x&rsqb;
+controller      ahb0    at isa? bio irq 11 vector ahbintr
-controller      sea0    at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr &lsqb;for Seagate
+&lsqb;for Adaptec 154x&rsqb;
-ST01/02&rsqb;
+controller      aha0    at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
+&lsqb;for Seagate ST01/02&rsqb;
+controller      sea0    at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr
 controller      scbus0
 
 device          sd0	&lsqb;support for 4 SCSI harddisks, sd0 up sd3&rsqb;
 
 device          st0	&lsqb;support for 2 SCSI tapes&rsqb;
 
-device          cd0     #Only need one of these, the code dynamically grows &lsqb;for the cdrom&rsqb;
+&lsqb;for the cdrom&rsqb;
+device          cd0     #Only need one of these, the code dynamically grows
           </verb>
 
 	
@@ -722,7 +725,8 @@ options        "TUNE_1542"             #dynamic tune of bus DMA speed
 	    and try accessing the device with debugging turned on for
 	    that device. If your device doesn't even probe at startup,
 	    you may have to define the address of the device that
-	    is failing, and the desired debug level in /sys/scsi/scsidebug.h.
+	    is failing, and the desired debug level in
+	    <tt>/sys/scsi/scsidebug.h</tt>.
 	    If it probes but just doesn't work, you can use the
 	    <tt>scsi(8)</tt> command to dynamically set a debug level to
 	    it in a running kernel (if SCSIDEBUG is defined).

handbook/slipc.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: slipc.sgml,v 1.4 1995-10-07 04:31:59 jfieber Exp $ -->
+<!-- $Id: slipc.sgml,v 1.5 1995-12-04 17:58:51 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect><heading>Setting up a SLIP client<label id="slipc"></heading>
@@ -33,7 +33,7 @@ so this won't be a problem unless you deleted it.
 
 <p><enum>
 <item>Add your home machine, the gateway and nameservers to your
-    /etc/hosts file.  Mine looks like this:
+    <tt>/etc/hosts</tt> file.  Mine looks like this:
 <verb>
 127.0.0.1               localhost loghost
 136.152.64.181          silvia.HIP.Berkeley.EDU silvia.HIP silvia
@@ -45,10 +45,10 @@ so this won't be a problem unless you deleted it.
     By the way, silvia is the name of the car that I had when I was
     back in Japan (it's called 2?0SX here in U.S.).
 
-<item>Make sure you have "hosts" before "bind" in your /etc/host.conf.
+<item>Make sure you have "hosts" before "bind" in your <tt>/etc/host.conf</tt>.
     Otherwise, funny things may happen.
 
-<item>Edit the file /etc/sysconfig.
+<item>Edit the file <tt>/etc/sysconfig</tt>.
 <enum>
 <item>Set your hostname by editing the line that says:
 <verb>
@@ -81,7 +81,7 @@ defaultrouter=slip-gateway
 </verb>
 </enum>
 
-<item>Make a file /etc/resolv.conf which contains:
+<item>Make a file <tt>/etc/resolv.conf</tt> which contains:
 <verb>
 domain HIP.Berkeley.EDU
 nameserver 128.32.136.9
@@ -91,8 +91,8 @@ nameserver 128.32.136.12
     actual domain names and addresses depend on your environment.
 
 <item>Set the password for root and toor (and any other accounts that
-    doesn't have a password).  Use passwd, don't edit the passwd or
+    doesn't have a password).  Use passwd, don't edit the <tt>/etc/passwd</tt>
-    passwd.master files!
+    or <tt>/etc/master.passwd</tt> files!
 
 <item>Reboot your machine and make sure it comes up with the correct
     hostname.
@@ -123,7 +123,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a
     yours).  Then you can just type "slip" from the kermit prompt to
     get connected.
 
-    Note: leaving your password in plain text anywhere in the
+    <bf>Note</bf>: leaving your password in plain text anywhere in the
     filesystem is generally a BAD idea.  Do it at your own risk.  I'm
     just too lazy.
 
@@ -170,8 +170,8 @@ sl0: flags=10<POINTOPOINT>
         inet 136.152.64.181 --> 136.152.64.1 netmask ffffff00
 </verb>
 
-<item>Also, "netstat -r" will give the routing table, in case you get the
+<item>Also, <tt>netstat -r</tt> will give the routing table, in case you get
-"no route to host" messages from ping.  Mine looks like:
+the "no route to host" messages from ping.  Mine looks like:
 <verb>
 silvia# netstat -r
 Routing tables

handbook/userppp.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: userppp.sgml,v 1.3 1995-08-29 01:42:52 jfieber Exp $ -->
+<!-- $Id: userppp.sgml,v 1.4 1995-12-04 17:58:52 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect>Setting up user PPP<label id="userppp">
@@ -105,7 +105,7 @@ pseudo-device	  tun		1
   below to reflect whichever device number you are using.
 
   The easiest way to make sure that the tun0 device is configured correctly is
-  to re-make it. To this end, execute the following commands,
+  to re-make it. To this end, execute the following commands:
 <tscreen><verb>
 # cd /dev
 # ./MAKEDEV tun0
@@ -118,7 +118,7 @@ pseudo-device	  tun		1
   Confusingly, it appears that both user ppp and pppd (the kernel level
   implementation of PPP) both assume configuration files kept in
   /etc/ppp. However, the sample configuration files provided are good for
-  user ppp, so keep them around for reference. The easiest way to do this is,
+  user ppp, so keep them around for reference. The easiest way to do this is:
 <tscreen><verb>
 # cd /etc
 # mv ppp ppp.orig
@@ -140,14 +140,14 @@ pseudo-device	  tun		1
      into hostnames. It can be configured to look for maps that describe IP to
      hostname mappings in one of two places.
 
-     The first is a file called /etc/hosts (``hosts'' in section 5 of the
+     The first is a file called <tt>/etc/hosts</tt> (<tt>man 5 hosts</tt>).
-     manual). The second is the Internet Domain Name Service, a distributed
+     The second is the Internet Domain Name Service, a distributed
      data base, the discussion of which is beyond the realm of this document.
 
      The resolver is a set of system calls that do the mappings,
      and you have to tell them where to get their information
-     from. You do this by editing the file /etc/host.conf. Do
+     from. You do this by editing the file <tt>/etc/host.conf</tt>. Do
-     <bf>not</bf> call this file /etc/hosts.conf (note the extra
+     <bf>not</bf> call this file <tt>/etc/hosts.conf</tt> (note the extra
      ``s'') as the results can be confusing.
 
      This file should contain the following two lines,
@@ -155,12 +155,13 @@ pseudo-device	  tun		1
 hosts
 bind
 </verb></tscreen>
-     which instruct the resolver to look in the file /etc/hosts first, and
+     which instruct the resolver to look in the file <tt>/etc/hosts</tt> first,
-     then to consult the DNS if the name was not found in the /etc/hosts file.
+     and then to consult the DNS if the name was not found in the
+     <tt>/etc/hosts</tt> file.
 
      It's probably a good idea to make sure you are not running the ``named''
-     service. Check your /etc/sysconfig file for the line that refers to
+     service. Check your <tt>/etc/sysconfig</tt> file for the line that refers
-     ``namedflags'', and make sure the line reads
+     to ``namedflags'', and make sure the line reads
 <tscreen><verb>
 namedflags="NO"
 </verb></tscreen>
@@ -170,7 +171,8 @@ namedflags="NO"
 <p>This file should contain the IP addresses and names of machines on your
      network. At a bare minimum it should contain entries for the machine
      which will be running ppp. Assuming that you're machine is called
-     foo.bar.com with the IP address 10.0.0.1, /etc/hosts should contain
+     foo.bar.com with the IP address 10.0.0.1, <tt>/etc/hosts</tt> should
+     contain:
 <tscreen><verb>
 127.0.0.0    localhost
 10.0.0.1     foo.bar.com	       foo
@@ -188,13 +190,13 @@ namedflags="NO"
 
 <sect2><heading>Create the /etc/resolv.conf file</heading>
 
-<p>/etc/resolv.conf contains some extra information required when you are
+<p><tt>/etc/resolv.conf</tt> contains some extra information required when
-     not running a nameserver. It points the resolver routines at real
+     you are not running a nameserver. It points the resolver routines at real
      nameservers, and specifies some other information.
 
-     At the very least, /etc/resolv.conf should contain one line with a
+     At the very least, <tt>/etc/resolv.conf</tt> should contain one line with
-     nameserver which can be queried. You should enter this as an IP
+     a nameserver which can be queried. You should enter this as an IP
-     address. My /etc/resolv.conf contains
+     address. My <tt>/etc/resolv.conf</tt> contains:
 <tscreen><verb>
 nameserver 158.152.1.193
 nameserver 158.152.1.65
@@ -205,13 +207,13 @@ nameserver 158.152.1.65
 <sect1><heading>PPP and static IP addresses</heading>
 
 <p>Probably the easiest to configure for. You will need to create three files
-    in the /etc/ppp directory.
+    in the <tt>/etc/ppp</tt> directory.
 
-    The first of these is ppp.conf. It should look similar to the example
+    The first of these is <tt>ppp.conf</tt>. It should look similar to the
-    below. Note that lines that end in a ``:'' start in column 1, all other
+    example below. Note that lines that end in a ``:'' start in column 1, all
-    lines should be indented as shown.
+    other lines should be indented as shown.
 
-    /etc/ppp/ppp.conf
+    <tt>/etc/ppp/ppp.conf</tt>
 <tscreen><verb>
 1     default:
 2       set device /dev/cuaa0
@@ -233,15 +235,15 @@ nameserver 158.152.1.65
               executed automatically when ppp is run.
 
 <tag/Line 2:/ Identifies the device that has the modem hanging from it.
-              COM1: is /dev/cuaa0 and COM2: is /dev/cuaa1
+              COM1: is <tt>/dev/cuaa0</tt> and COM2: is <tt>/dev/cuaa1</tt>.
 
 <tag/Line 3:/ Sets the speed you want to connect at.
 
 <tag/* Lines 4 and 5:/ Don't know exactly what effect these lines have
 
-<tag/Line 6:/ Dial string commands. user ppp uses the chat(8) language. Check
+<tag/Line 6:/ Dial string commands. user ppp uses the <tt>chat(8)</tt>
-              the manual page for information on the features of this
+              language. Check the manual page for information on the features
-	      language.
+              of this language.
 
 <tag/Line 7:/ Identifies an entry for a provider called ``provider''.
 
@@ -257,7 +259,7 @@ password: bar
 protocol: ppp
 </verb></tscreen>
 	      You will need to alter this script to suit your own needs. It is
-	      written in the chat(8) language.
+	      written in the <tt>chat(8)</tt> language.
 
 <tag/Line 10:/ Sets the default timeout (in seconds) for the connection. So
 	      the connectioned will be closed automatically after 120 seconds
@@ -269,7 +271,7 @@ protocol: ppp
 	      ISP indicated for their gateway.
 </descrip>
 
-    Now you have to edit the file /etc/ppp/ppp.linkup:
+    Now you have to edit the file <tt>/etc/ppp/ppp.linkup</tt>:
 <tscreen><verb>
 x.x.x.x:
   add 0 0 HISADDR
@@ -278,10 +280,10 @@ x.x.x.x:
     automatically add a default route from your ISP (who's address is
     automatically inserted with the HISADDR macro) to you.
 
-    Finally, you can create the file /etc/ppp/ppp.secret, which sets some
+    Finally, you can create the file <tt>/etc/ppp/ppp.secret</tt>, which sets
-    passwords to prevent people messing around with ppp on your system. You
+    some passwords to prevent people messing around with ppp on your system.
-    may or may not want to do this, depending on how many people have access
+    You may or may not want to do this, depending on how many people have
-    to your ppp system.
+    access to your ppp system.
 
 <sect1><heading>PPP and Dynamic IP configuration</heading>
 
@@ -297,7 +299,8 @@ set ifaddr 0 0
 <sect1><heading>Final system configuration</heading>
 
 <p>You now have PPP configured, but there's a few more things to do before
-    it's ready to work. They all involve editing the /etc/sysconfig file.
+    it's ready to work. They all involve editing the <tt>/etc/sysconfig</tt>
+    file.
 
     Working from the top down in this file, make sure the ``hostname='' line
     is set, e.g.,
@@ -356,5 +359,5 @@ inet x.x.x.x --> y.y.y.y netmask 0xffffffff
 <tscreen><verb>
 # ppp -auto provider
 </verb></tscreen>
-    This line could be added to your /etc/rc.local file.
+    This line could be added to your <tt>/etc/rc.local</tt> file.