diff --git a/distrib/notes/next68k/hardware b/distrib/notes/next68k/hardware
index 8c2abb07e65f..e1dcf6955ef9 100644
--- a/distrib/notes/next68k/hardware
+++ b/distrib/notes/next68k/hardware
@@ -1,10 +1,11 @@
-.\"	$NetBSD: hardware,v 1.5 2002/05/03 03:59:30 mbw Exp $
+.\"	$NetBSD: hardware,v 1.6 2002/06/30 12:07:35 lukem Exp $
 .
 .Nx*M
 \*V will run on the 25 MHz 68040-based
 .Tn NeXT
-workstations.  The Turbo (33 MHz) models are not supported.  The 68030
-model is not supported.
+workstations.
+The Turbo (33 MHz) models are not supported.
+The 68030 model is not supported.
 .Nx*M
 \*V does not
 have any local disk support, so you must netboot and run diskless.
@@ -12,8 +13,8 @@ have any local disk support, so you must netboot and run diskless.
 The minimum configuration requires 4 MB of RAM and a network server
 capable of netbooting
 .Nx*M .
-Serial consoles are poorly supported by the hardware, see the FAQ for
-help.  Typically it is just easier to use the NeXT monitor and keyboard.
+Serial consoles are poorly supported by the hardware, see the FAQ for help.
+Typically it is just easier to use the NeXT monitor and keyboard.
 .Lk http://www.netbsd.org/Ports/next68k/faq.html
 .
 .Ss2 Supported hardware
diff --git a/distrib/notes/next68k/install b/distrib/notes/next68k/install
index a9066be0448f..6c3900225087 100644
--- a/distrib/notes/next68k/install
+++ b/distrib/notes/next68k/install
@@ -1,35 +1,3 @@
-.\"	$NetBSD: install,v 1.5 2002/05/03 05:21:39 mbw Exp $
-.\"
-.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\"    notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\"    notice, this list of conditions and the following disclaimer in the
-.\"    documentation and/or other materials provided with the distribution.
-.\" 3. All advertising materials mentioning features or use of this software
-.\"    must display the following acknowledgement:
-.\"        This product includes software developed by the NetBSD
-.\"        Foundation, Inc. and its contributors.
-.\" 4. Neither the name of The NetBSD Foundation nor the names of its
-.\"    contributors may be used to endorse or promote products derived
-.\"    from this software without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
-.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
-.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-.\" PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
-.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-.\" POSSIBILITY OF SUCH DAMAGE.
-.\"
-.Pp
+.\"	$NetBSD: install,v 1.6 2002/06/30 12:07:35 lukem Exp $
+.
 .so ../common/netboot
diff --git a/distrib/notes/next68k/prep b/distrib/notes/next68k/prep
index 331713c370aa..2980e77abf54 100644
--- a/distrib/notes/next68k/prep
+++ b/distrib/notes/next68k/prep
@@ -1,9 +1,9 @@
-.\"	$NetBSD: prep,v 1.4 2002/05/03 03:59:55 mbw Exp $
+.\"	$NetBSD: prep,v 1.5 2002/06/30 12:07:35 lukem Exp $
 .
 .Ss2 Get to the ROM Monitor prompt
 .
 After the system performs its power-on self test, and while it tries to
-boot an operating system, press the 
+boot an operating system, press the
 .Key COMMAND-`
 keys (the backquote is above 7 on the keypad on the right of the keyboard).
 You should see a prompt like this:
@@ -17,8 +17,8 @@ Memory size 40 MB
 NeXT\*>
 .disp)
 .Pp
-Write down the ethernet address.  You will need this later to configure
-the netboot server for your 
+Write down the ethernet address.
+You will need this later to configure the netboot server for your
 .Nx*M
 system.
 .
@@ -26,28 +26,30 @@ system.
 .
 Press the
 .Key p
-key to modify the configuration parameters.  You will need to change the
+key to modify the configuration parameters.
+You will need to change the
 .Li "boot command"
-to 
+to
 .Li "en()netbsd"
-which is to boot from the 
+which is to boot from the
 .Li "en()"
 ethernet device the kernel named
 .Li netbsd .
-You should wite down what the original 
+You should wite down what the original
 .Li "boot command"
-was in case you wish to boot 
+was in case you wish to boot
 .Tn NEXTSTEP
-in the future.  It will probably be
+in the future.
+It will probably be
 .Li "sd()" .
 While modifying the parameters, you may wish to set the system to use
 .Li "verbose test mode"
 which will print detailed messages while it is attempting to load the
-kernel, as opposed to the normal graphic of a network cable.  You
-should not set the
+kernel, as opposed to the normal graphic of a network cable.
+You should not set the
 .Li "extended diagnostics"
-as the system will try to boot a diagnostic kernel.  Here is an
-example configuration session:
+as the system will try to boot a diagnostic kernel.
+Here is an example configuration session:
 .(disp
 .No "NeXT\*>" Ic p
 .No "boot command: sd()?" Ic "en()netbsd"
@@ -65,8 +67,8 @@ example configuration session:
 .No "enable parity cehcking if parity memory is present:  no?" Ic "no"
 .disp)
 .Pp
-Now, whenever you reset or power on your system, it will attempt to
-netboot.  From the ROM Monitor prompt, you can simply type
+Now, whenever you reset or power on your system, it will attempt to netboot.
+From the ROM Monitor prompt, you can simply type
 .Key b
-to netboot.  You can also press the power key (above the arrows) to turn
-off the system.
+to netboot.
+You can also press the power key (above the arrows) to turn off the system.
diff --git a/distrib/notes/next68k/upgrade b/distrib/notes/next68k/upgrade
index 4aa38ddb9d0d..b51077a6cfd9 100644
--- a/distrib/notes/next68k/upgrade
+++ b/distrib/notes/next68k/upgrade
@@ -1,6 +1,6 @@
-.\"	$NetBSD: upgrade,v 1.3 2000/10/29 14:08:08 lukem Exp $
+.\"	$NetBSD: upgrade,v 1.4 2002/06/30 12:07:35 lukem Exp $
 .\"
-.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
+.\" Copyright (c) 1999-2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
diff --git a/distrib/notes/next68k/xfer b/distrib/notes/next68k/xfer
index 7173bf7ae2b6..4b53e766c091 100644
--- a/distrib/notes/next68k/xfer
+++ b/distrib/notes/next68k/xfer
@@ -1,4 +1,4 @@
-.\"	$NetBSD: xfer,v 1.3 2000/10/29 14:08:09 lukem Exp $
+.\"	$NetBSD: xfer,v 1.4 2002/06/30 12:07:35 lukem Exp $
 .\"
 .\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -35,12 +35,13 @@
 Because
 .Nx*M
 must run diskless, the distribution must be
-installed to a remote machine that NFS exports to the NeXT machine.  As
-a result, there is no automated install procedure.  Begin by retrieving
-the
+installed to a remote machine that NFS exports to the NeXT machine.
+As a result, there is no automated install procedure.
+Begin by retrieving the
 .Nx
-set files onto the serving machine.  These can be found at
-ftp.netbsd.org.  You may want to keep the following information handy:
+set files onto the serving machine.
+These can be found at ftp.netbsd.org.
+You may want to keep the following information handy:
 .(disp
 IP Address: ftp.netbsd.org
 Login: anonymous
diff --git a/distrib/notes/pc532/hardware b/distrib/notes/pc532/hardware
index 9541095d7a67..89aaaf194405 100644
--- a/distrib/notes/pc532/hardware
+++ b/distrib/notes/pc532/hardware
@@ -1,11 +1,13 @@
-.\"	$NetBSD: hardware,v 1.8 2000/10/29 14:08:09 lukem Exp $
+.\"	$NetBSD: hardware,v 1.9 2002/06/30 12:15:13 lukem Exp $
 .
 .Nx*M
 \*V runs on a
 .Tn PC532
-computer. It supports a subset of the
+computer.
+It supports a subset of the
 .Dq standard
-hardware to date. This is defined as:
+hardware to date.
+This is defined as:
 .(bullet -offset indent
 4 MB of memory
 .It
@@ -26,7 +28,8 @@ The Matthias Pfaller Parallel Port.
 .Nx*M
 currently expects the ROM monitor to be the
 .Dq autoboot monitor
-of Oct/Nov 1991. It includes support to set up auto booting of
+of Oct/Nov 1991.
+It includes support to set up auto booting of
 .Nx ,
 including a secondary boot program that the autoboot monitor
 will load that in turn loads the
@@ -39,6 +42,5 @@ Source and ROM images of the autoboot monitor are located at
 .Pp
 Most of the \*M specific development of
 .Nx*M
-was done on a
-machine with 8 MB of memory. It should run with 4 MB of memory
-although it may be slower.
+was done on a machine with 8 MB of memory.
+It should run with 4 MB of memory although it may be slower.
diff --git a/distrib/notes/pc532/install b/distrib/notes/pc532/install
index 75f263c80a33..142053c301ea 100644
--- a/distrib/notes/pc532/install
+++ b/distrib/notes/pc532/install
@@ -1,6 +1,6 @@
-.\"	$NetBSD: install,v 1.16 2001/06/11 01:50:50 wiz Exp $
+.\"	$NetBSD: install,v 1.17 2002/06/30 12:15:13 lukem Exp $
 .\"
-.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
+.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
@@ -46,8 +46,9 @@ First,
 the SCSI devices.
 .Pa floppy-144.fs
 has only
-support for disks configured into the kernel. Starting the search at
-SCSI address 0, lun 0 and increasing, the first disk found will be
+support for disks configured into the kernel.
+Starting the search at SCSI address 0, lun 0 and increasing,
+the first disk found will be
 .Li sd0
 regardless of the address, the second will be sd1.
 .Tn KLONDIKE
@@ -76,34 +77,35 @@ are supported by the
 .Pa floppy-144.fs
 kernel.
 .Pp
-Next you need to know what the install script wants to do. This install
-is script on the ram disk root that can do most of the work of configuring
-your disk.
+Next you need to know what the install script wants to do.
+This install is script on the ram disk root that can do most of
+the work of configuring your disk.
 .(enum
 The script assumes your are using the first n sectors of your
-disk, where you can specify n. It will allow you to create
-up to 5 file system partitions, one swap partition and one
-boot partition.
+disk, where you can specify n.
+It will allow you to create up to 5 file system partitions,
+one swap partition and one boot partition.
 .It
-You should know how many total sectors are on your disk. The
-configure will report a head, track, and cylinder count, but
+You should know how many total sectors are on your disk.
+The configure will report a head, track, and cylinder count, but
 we have found that on some of our disks, it reports something that
 makes a smaller disk than we really had.
 .It
 It is possible to have the install script make a partition
 over your save area AND not make a new file system, thus
-preserving what is there. Then, later you can make a new
-file system after you no longer need the stuff there. You
-will need to do only one boot to get things working from
-the disk.
+preserving what is there.
+Then, later you can make a new file system after you no longer need
+the stuff there.
+You will need to do only one boot to get things working from the disk.
 .enum)
 .
 .Ss2 The install procedure
 .(enum
 Adjust your console device settings.
 The floppy-144.fs kernel will come up with 9600 baud, 7 bits,
-even parity and one stop bit. Adjust your terminal to match
-these settings. The monitor's baud rate can be changed with
+even parity and one stop bit.
+Adjust your terminal to match these settings.
+The monitor's baud rate can be changed with
 .Ic "baud d'9600" .
 .
 .It
@@ -113,16 +115,18 @@ Get floppy-144.fs and boot the kernel from...
 .It Em Floppy
 From Floppy: (and using the autoboot monitor)
 If you have a 1.44 meg SCSI floppy drive, you can put floppy-144.fs
-onto a 3.5" floppy disk. Insert the disk into your floppy
-drive and use the monitor's boot command to boot the default
-image from the floppy. The image booted will ask you for a
-kernel to load. Answer
+onto a 3.5" floppy disk.
+Insert the disk into your floppy drive and use the monitor's boot
+command to boot the default image from the floppy.
+The image booted will ask you for a kernel to load.
+Answer
 .Pp
 .Dl Ic "sd" Ns Ar X Ns Ic "a:/netbsd"
 .Pp
 Replace
 .Ar X
-with your drive number. For KLONDIKE,
+with your drive number.
+For KLONDIKE,
 .Ar X
 would be
 .Ic 2 .
@@ -142,7 +146,8 @@ run at
 .Li 0x3BE020
 .enum)
 .Pp
-The boot program will ask you now for a kernel to load. Answer
+The boot program will ask you now for a kernel to load.
+Answer
 .Li md0a:/netbsd.gz
 .
 .It Em Serial Line
@@ -153,8 +158,8 @@ This program when used as
 .Dq "download file"
 will read the contents of the file and
 output to standard output a byte sequence used by the \*M
-ROM monitor to download a binary file into RAM. Using this
-program on a computer connected to the \*M, one can
+ROM monitor to download a binary file into RAM.
+Using this program on a computer connected to the \*M, one can
 load a copy of
 .Pa floppy-144.fs
 into RAM at
@@ -166,25 +171,24 @@ The
 .Pa floppy-144.fs
 will run the new
 .Ic sysinst
-utility as the standard
-setup. It assumes a VT100 compatible terminal. If you don't want
-to try using
+utility as the standard setup.
+It assumes a VT100 compatible terminal.
+If you don't want to try using
 .Ic sysinst
 or you don't have a VT100, type f followed by
-the return. Then following these instructions for installation.
+the return.
+Then following these instructions for installation.
 If you want to use
 .Ic sysinst ,
-read the i386 INSTALL instructions to
-learn about
+read the i386 INSTALL instructions to learn about
 .Ic sysinst .
 .(Note
 .Ic sysinst
-does not support SLIP or PPP
-connections.
+does not support SLIP or PPP connections.
 .Note)
 .It
-Choose a disk geometry. For me, the reported geometry left
-some sectors
+Choose a disk geometry.
+For me, the reported geometry left some sectors
 .Sq "unallocated" .
 That is, the autoconfig message
 said the disk had 2428 cylinders, 9 heads, and 93 sectors/track.
@@ -227,8 +231,8 @@ geometry.
 .It
 Run
 .Ic install ;
-it will ask you for the disk geometry and other
-questions. It will ask you for the geometry and then ask you
+it will ask you for the disk geometry and other questions.
+It will ask you for the geometry and then ask you
 how many of those sectors you want to use for
 .Nx .
 It also
@@ -236,10 +240,11 @@ wants to know the size of your boot partition (to be used with
 the auto-boot monitor), your root partition
 .Pq Pa / ,
 your swap partition,
-and then any other partitions you may want. For the
+and then any other partitions you may want.
+For the
 .Sq other
-partitions, it will ask for a mount point. The mount point will
-be
+partitions, it will ask for a mount point.
+The mount point will be
 .Dq "relative to /"
 and should not include the leading
 .Sq / .
@@ -256,7 +261,8 @@ It will enter the partition into the disklabel.
 look around, if you want ... and then halt
 .Nx .
 .It
-reboot the machine. Using the autoboot monitor, all you should have
+reboot the machine.
+Using the autoboot monitor, all you should have
 to do is give the ROM monitor command
 .Ic boot .
 The secondary
@@ -271,7 +277,8 @@ and manually load the
 boot loader from the disk using
 the
 .Ic read
-command. If you would rather use the autoboot monitor
+command.
+If you would rather use the autoboot monitor
 you can get source and ROM images from the URL
 .Lk ftp://ftp.cs.wwu.edu/pub/\*M/mon.auto.tar.gz
 .It
@@ -280,8 +287,8 @@ You can do this via -
 .(bullet
 a TCP/IP link (slip, ppp or plip)
 you have ifconfig, slattach, route, netstat,
-hostname and ftp on the mini-root. You can even
-use nfs...
+hostname and ftp on the mini-root.
+You can even use nfs...
 Plip is only an option if you have installed a
 centronics port in your \*M.
 You do have access to vi to edit your network
@@ -303,22 +310,24 @@ Get the .tgz files from the cd-rom
 .It
 Use the ROM compatible
 .Ic download
-program. The program
-download is included in the initial installation and
-can be used as the receive end of the download by
-using it as
+program.
+The program download is included in the initial installation and
+can be used as the receive end of the download by using it as
 .Ic "download -r file_to_write" .
-If the CRC is correct, the file is retained. If the CRC is not
-correct, the file is deleted.
+If the CRC is correct, the file is retained.
+If the CRC is not correct, the file is deleted.
 .bullet)
 .It
-Load the .tgz files. Choose a place to put them. We suggest making
-a directory
+Load the .tgz files.
+Choose a place to put them.
+We suggest making a directory
 .Pa /gz.files
-and put them there. If you are
+and put them there.
+If you are
 .Dq short on space,
 you might want to load them and extract them one
-at a time. A minimum installation is
+at a time.
+A minimum installation is
 .Sy base
 and
 .Sy etc .
@@ -343,7 +352,8 @@ The
 .Ic --unlink
 is to make sure that the install versions
 of sh, init, ... are replaced by their proper versons
-in base.tgz. We think it is wise to include the
+in base.tgz.
+We think it is wise to include the
 .Ic --unlink
 for other things.
 .It
@@ -363,7 +373,8 @@ and then extract
 .Sy etc .
 You should extract
 .Sy etc
-for upgrades. For
+for upgrades.
+For
 .Dq full
 installations, extract all files.
 .It
@@ -389,7 +400,8 @@ make sure it includes all partitions you want mounted
 .tag)
 .Pp
 Now you can adjust the kernel's default baud rate to match your
-monitor's default baud rate. Do the following:
+monitor's default baud rate.
+Do the following:
 .Pp
 .Dl # Ic "gdb -w /netbsd"
 .Dl (gdb) Ic "set scndefaultrate = " Em your_baud_rate
@@ -399,12 +411,14 @@ where
 .Ar your_baud_rate No is the actual value, 19200, 38400 or
 something slower than 9600.
 If you set scndefaultrate to something bogus, you'll probably
-not be able to reboot... So be carefull!
+not be able to reboot...
+So be carefull!
 .It
 Reboot the machine and it should come up in multi-user mode
 .Em if
 you got it configured correctly.
 .It
-Enjoy! And help fix bugs and improve
+Enjoy!
+And help fix bugs and improve
 .Nx*M !
 .enum)
diff --git a/distrib/notes/pc532/prep b/distrib/notes/pc532/prep
index e1eceadec5a8..c05f4569d964 100644
--- a/distrib/notes/pc532/prep
+++ b/distrib/notes/pc532/prep
@@ -1,5 +1,5 @@
-.\"	$NetBSD: prep,v 1.5 2000/10/29 14:08:09 lukem Exp $
+.\"	$NetBSD: prep,v 1.6 2002/06/30 12:15:13 lukem Exp $
 .
 The major preparation needed is to make sure you can recover any
-current bits stored on your \*M. If you don't care about your
-data on the disk, you don't need to do anything.
+current bits stored on your \*M.
+If you don't care about your data on the disk, you don't need to do anything.
diff --git a/distrib/notes/pc532/upgrade b/distrib/notes/pc532/upgrade
index b1263bda4425..10697fd04c7e 100644
--- a/distrib/notes/pc532/upgrade
+++ b/distrib/notes/pc532/upgrade
@@ -1,6 +1,6 @@
-.\"	$NetBSD: upgrade,v 1.11 2000/10/29 14:08:09 lukem Exp $
+.\"	$NetBSD: upgrade,v 1.12 2002/06/30 12:15:13 lukem Exp $
 .\"
-.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
+.\" Copyright (c) 1999-2002 The NetBSD Foundation, Inc.
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
@@ -39,23 +39,24 @@ to advance to a later version by recompiling from source due primarily
 to interdependencies in the various components.
 .Pp
 To do the upgrade, you must have at least base.tgz on disk and
-a copy of the proper netbsd.default.  It will require quite a bit
-of disk space to do the upgrade.
+a copy of the proper netbsd.default.
+It will require quite a bit of disk space to do the upgrade.
 .Pp
 Since upgrading involves replacing the kernel, and most of the system
-binaries, it has the potential to cause data loss.  You are strongly
-advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
+binaries, it has the potential to cause data loss.
+You are strongly advised to
+BACK UP ANY IMPORTANT DATA ON YOUR DISK,
+whether on the
 .Nx
 partition or on another operating system's partition, before
 beginning the upgrade process.
 .Pp
 To upgrade your system, follow the following instructions:
 .(bullet
-Assuming you have space, load the .tgz files onto disk
-some place.  Then boot the floppy-144.fs image via the
-method you use.  Under the install system, extract the
-\&.tgz files as mentioned below or read the i386 INSTALL
-notes for how to use sysinst.
+Assuming you have space, load the .tgz files onto disk some place.
+Then boot the floppy-144.fs image via the method you use.
+Under the install system, extract the \&.tgz files as mentioned below
+or read the i386 INSTALL notes for how to use sysinst.
 .It
 Extract the .tgz files.
 For example, to extract
@@ -64,8 +65,8 @@ For example, to extract
 .Dl # Ic "cd /"
 .Dl # Ic "pax -zrvpe -f /gz.files/base.tgz"
 .It
-Extract all the .tgz files you want.  You should carefully
-work at upgrading
+Extract all the .tgz files you want.
+You should carefully work at upgrading
 .Pa /etc .
 There may be changes to file formats depending on what version of
 .Nx*M
@@ -88,9 +89,11 @@ in
 as the file
 .Pa netbsd .
 .It
-Reboot.  (Remember,
+Reboot.
+(Remember,
 .Pa netbsd.default
-is a 9600 console line kernel.  Read the last part of the new installation
+is a 9600 console line kernel.
+Read the last part of the new installation
 part of these notes to find out how to change your default speed.)
 .It
 After reboot, you should make sure you check your new file systems.
diff --git a/distrib/notes/pc532/whatis b/distrib/notes/pc532/whatis
index ce975131b32d..74241f546724 100644
--- a/distrib/notes/pc532/whatis
+++ b/distrib/notes/pc532/whatis
@@ -1,14 +1,16 @@
-.\"	$NetBSD: whatis,v 1.7 2000/10/14 22:27:44 lukem Exp $
+.\"	$NetBSD: whatis,v 1.8 2002/06/30 12:15:13 lukem Exp $
 .
 This is the sixth major release of
 .Nx*M .
 .Pp
-There are a few known problems in the \*M port.  They include:
+There are a few known problems in the \*M port.
+They include:
 .(enum
 .Ic ppp
 reports a lot of input errors on some machines.
 .It
-Some tape drives do not work very well.  Some have hung the system.
+Some tape drives do not work very well.
+Some have hung the system.
 .It
 The serial drivers do not have all the desired features.
 .Ic ( ttyflags
diff --git a/distrib/notes/pc532/xfer b/distrib/notes/pc532/xfer
index 09c95f538254..a533672c5827 100644
--- a/distrib/notes/pc532/xfer
+++ b/distrib/notes/pc532/xfer
@@ -1,4 +1,4 @@
-.\"	$NetBSD: xfer,v 1.7 2001/07/24 18:05:20 nra Exp $
+.\"	$NetBSD: xfer,v 1.8 2002/06/30 12:15:13 lukem Exp $
 .
 The
 .Sq standard
@@ -6,12 +6,13 @@ method of getting
 .Nx*M
 onto your \*M is
 via the console terminal and using the downloading parts of the
-ROM monitor.  As such, usually another computer has the distribution
-on disk and is connected via a serial line to your \*M's console
-port.  A terminal connected to the attached host computer is used
-to access the \*M console via a terminal program.  The source for
-a program called download is part of this distribution.  Download
-sends data to the ROM monitor over the serial line.
+ROM monitor.
+As such, usually another computer has the distribution
+on disk and is connected via a serial line to your \*M's console port.
+A terminal connected to the attached host computer is used
+to access the \*M console via a terminal program.
+The source for a program called download is part of this distribution.
+Download sends data to the ROM monitor over the serial line.
 .Pp
 You may need to find and read the documentation about the ROM monitor
 download command and other low level commands.
@@ -30,7 +31,7 @@ on a hard disk much easier than
 with the ROM monitor.
 .Nx*M
 was developed from Minix/\*M
-until it was self hosting.  You can run
+until it was self hosting.
+You can run
 .Nx
-and Minix or other OS
-off the same disk.
+and Minix or other OS off the same disk.