initrd.4: Various minor wording improvements.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man4/initrd.4 b/man4/initrd.4
index b9980e01b9a8e674503749ff4915d72374ff9841..5dc81407339e7b7ddea7237725ade1b1a5ba8818 100644 (file)
--- a/man4/initrd.4
+++ b/man4/initrd.4
@@ -31,7 +31,7 @@
 .\"    phone: (302)654-5478
 .\"
 .\" $Id: initrd.4,v 0.9 1997/11/07 05:05:32 kallal Exp kallal $
-.TH INITRD 4 2007-11-26 "Linux" "Linux Programmer's Manual"
+.TH INITRD 4 2009-04-04 "Linux" "Linux Programmer's Manual"
 .SH NAME
 initrd \- boot loader initialized RAM disk
 .SH CONFIGURATION
@@ -71,17 +71,14 @@ the RAM disk driver cannot be loaded as a module.
 The special file
 .I /dev/initrd
 is a read-only block device.
-Device
-.I /dev/initrd
-is a RAM disk that is initialized (e.g., loaded) by the boot loader before
-the kernel is started.
-The kernel then can use the block device
+This device is a RAM disk that is initialized (e.g., loaded)
+by the boot loader before the kernel is started.
+The kernel then can use
 .IR /dev/initrd "'s "
-contents for a two phased system boot-up.
+contents for a two-phase system boot-up.
 .PP
 In the first boot-up phase, the kernel starts up
-and mounts an initial root file-system from the contents
-of
+and mounts an initial root file-system from the contents of
 .I /dev/initrd
 (e.g., RAM disk initialized by the boot loader).
 In the second phase, additional drivers or other modules
@@ -109,14 +106,14 @@ onto device
 and then frees the memory used by
 .IR /dev/initrd .
 .IP 3.
-The kernel then read-write mounts device
+The kernel then read-write mounts the device
 .I /dev/ram0
 as the initial root file system.
 .IP 4.
-If the indicated normal root file system is also the initial root file-system
-(e.g.
-.I /dev/ram0
-) then the kernel skips to the last step for the usual boot sequence.
+If the indicated normal root file system is also the initial
+root file-system (e.g.
+.IR /dev/ram0 )
+then the kernel skips to the last step for the usual boot sequence.
 .IP 5.
 If the executable file
 .IR /linuxrc
@@ -142,17 +139,17 @@ file-system, then the behavior of the kernel is
 .BR UNSPECIFIED .
 See the NOTES section for the current kernel behavior.)
 .IP 7.
-If the normal root file system has directory
+If the normal root file system has a directory
 .IR /initrd ,
-device
+the device
 .I /dev/ram0
 is moved from
 .IR /
 to
 .IR /initrd .
-Otherwise if directory
+Otherwise if the directory
 .IR /initrd
-does not exist device
+does not exist, the device
 .I /dev/ram0
 is unmounted.
 (When moved from
@@ -164,7 +161,7 @@ is not unmounted and therefore processes can remain running from
 .IR /dev/ram0 .
 If directory
 .I /initrd
-does not exist on the normal root file-system
+does not exist on the normal root file system
 and any processes remain running from
 .IR /dev/ram0
 when
@@ -180,7 +177,7 @@ is performed on the normal root file system.
 .\"
 .\"
 .SS Options
-The following boot loader options when used with
+The following boot loader options, when used with
 .BR initrd ,
 affect the kernel's boot-up operation:
 .TP
@@ -200,7 +197,7 @@ The filename specified with this
 option will typically be a gzipped file-system image.
 .TP
 .I noinitrd
-This boot time option disables the two phase boot-up operation.
+This boot option disables the two-phase boot-up operation.
 The kernel performs the usual boot sequence as if
 .I /dev/initrd
 was not initialized.
@@ -239,14 +236,14 @@ the kernel's settings
 or compiled into the kernel file),
 or the boot loader option setting
 is used for the normal root file systems.
-For a NFS-mounted normal root file system, one has to use the
+For an NFS-mounted normal root file system, one has to use the
 .B nfs_root_name
 and
 .B nfs_root_addrs
 boot options to give the NFS settings.
 For more information on NFS-mounted root see the kernel documentation file
-.BR nfsroot.txt .
-For more information on setting the root file system also see the
+.BR Documentation/filesystems/nfsroot.txt .
+For more information on setting the root file system see also the
 .BR LILO
 and
 LOADLIN
@@ -272,7 +269,7 @@ For a physical root device, the root device is changed by having
 .I /linuxrc
 write the new root file system device number into
 .IR /proc/sys/kernel/real-root-dev .
-For a NFS root file system, the root device is changed by having
+For an NFS root file system, the root device is changed by having
 .I /linuxrc
 write the NFS setting into files
 .IR /proc/sys/kernel/nfs-root-name
@@ -288,7 +285,7 @@ the normal root device to
     echo 0x365 >/proc/sys/kernel/real-root-dev
 
 .fi
-For a NFS example, the following shell command lines would change the
+For an NFS example, the following shell command lines would change the
 normal root device to the NFS directory
 .I /var/nfsroot
 on a local networked NFS server with IP number 193.8.232.7 for a system with
@@ -336,9 +333,8 @@ The executable
 determines what is needed to (1) mount the normal root file-system
 (i.e., device type, device drivers, file system) and (2) the
 distribution media (e.g., CD-ROM, network, tape, ...).
-This can be
-done by asking the user, by auto-probing, or by using a hybrid
-approach.
+This can be done by asking the user, by auto-probing,
+or by using a hybrid approach.
 .IP 3.
 The executable
 .I /linuxrc