Fix markup.

external/gpl2/lvm2/dist/man/vgrename.8

@@ -1,4 +1,4 @@
-.\"    $NetBSD: vgrename.8,v 1.2 2009/02/18 12:16:13 haad Exp $
+.\"    $NetBSD: vgrename.8,v 1.3 2009/10/15 00:59:01 joerg Exp $
 .\"
 .TH VGRENAME 8 "LVM TOOLS 2.02.44-cvs (02-17-09)" "Sistina Software UK" \" -*- nroff -*-
 .SH NAME
@@ -24,18 +24,18 @@ See \fBlvm\fP for common options.
 .SH Examples
 "vgrename /dev/vg02 /dev/my_volume_group" renames existing
 volume group "vg02" to "my_volume_group".
-.TP
+.PP
 "vgrename vg02 my_volume_group" does the same.
-.TP
+.PP
 "vgrename Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 VolGroup00_tmp"
 changes the name of the Volume Group with UUID
 Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 to 
 "VolGroup00_tmp".
-
+.PP
 All the Volume Groups visible to a system need to have different
 names.  Otherwise many LVM2 commands will refuse to run or give
 warning messages.
-
+.PP
 This situation could arise when disks are moved between machines.  If
 a disk is connected and it contains a Volume Group with the same name
 as the Volume Group containing your root filesystem the machine might
@@ -43,7 +43,6 @@ not even boot correctly.  However, the two Volume Groups should have
 different UUIDs (unless the disk was cloned) so you can rename
 one of the conflicting Volume Groups with
 \fBvgrename\fP.
-.TP
 .SH SEE ALSO
 .BR lvm (8),
 .BR vgchange (8),

usr.sbin/ntp/ntpq/ntpq.8

@@ -96,9 +96,7 @@ requests being sent to a server.
 These are described following.
 .sp
 .IR "? [command_keyword]"
-.sp 1x help [command_keyword]
-A
-.Ql \&?
+A `\&?'
 by itself will print a list of all the command
 keywords known to this incarnation of
 [= prog-name =] .