doc: fix some broken link specifications

[openafs.git] / doc / man-pages / pod1 / fs_mkmount.pod

diff --git a/doc/man-pages/pod1/fs_mkmount.pod b/doc/man-pages/pod1/fs_mkmount.pod
index fd74d9b..7f4a6a7 100644 (file)
--- a/doc/man-pages/pod1/fs_mkmount.pod
+++ b/doc/man-pages/pod1/fs_mkmount.pod
@@ -73,7 +73,7 @@ F</afs/I<cellname>> directories, respectively.
 
 If a mount point resides in a read/write volume and the volume name does
 not have a C<.readonly> or a C<.backup> extension, the Cache Manager
-attempts to access only the a read/write version of the volume. The access
+attempts to access only the read/write version of the volume. The access
 attempt fails with an error if the read/write version is inaccessible,
 even if a read-only version is accessible. In this situation the Cache
 Manager is said to be on a I<read/write path> and cannot switch back to
@@ -110,8 +110,8 @@ To create a read/write mount point, include the B<-rw> flag on the B<fs
 mkmount> command. It is conventional to create only one read/write mount
 point in a cell's filespace, using it to mount the cell's C<root.cell>
 volume just below the AFS filespace root (by convention,
-F</afs/.I<cellname>>). See the I<IBM AFS Quick Beginnings> for
-instructions and the chapter about volume management in the I<IBM AFS
+F</afs/.I<cellname>>). See the I<OpenAFS Quick Start Guide> for
+instructions and the chapter about volume management in the I<OpenAFS
 Administration Guide> for further discussion.
 
 Creating a read/write mount point for a read-only or backup volume is
@@ -161,7 +161,7 @@ results from attempting to create a new mount point in a read-only
 volume. By convention, the read/write path is indicated by placing a
 period before the cell name at the pathname's second level (for example,
 F</afs/.abc.com>). For further discussion of the concept of read/write and
-read-only paths through the filespace, see L<DESCRIPTION>.
+read-only paths through the filespace, see L</DESCRIPTION>.
 
 =item B<-vol> <I<volume name>>