Capitalize "Windows Overlay Filesystem" consistently

[wimlib] / doc / man1 / wimlib-imagex-apply.1

diff --git a/doc/man1/wimlib-imagex-apply.1 b/doc/man1/wimlib-imagex-apply.1
index 1245b7ba4865f93c23293fffc705078d64af459e..0fad8dd41fbda7a1aad0e210272391e58fe6bc55 100644 (file)
--- a/doc/man1/wimlib-imagex-apply.1
+++ b/doc/man1/wimlib-imagex-apply.1
@@ -1,4 +1,4 @@
-.TH WIMLIB-IMAGEX "1" "January 2016" "wimlib 1.9.0" "User Commands"
+.TH WIMLIB-IMAGEX "1" "March 2016" "wimlib 1.9.1" "User Commands"
 .SH NAME
 wimlib-imagex-apply \- Extract one image, or all images, from a WIM archive
 .SH SYNOPSIS
@@ -365,9 +365,8 @@ target volume is NTFS or another filesystem that supports reparse points.
 .IP ""
 In addition, this option works best when running on Windows 8.1 Update 1 or
 later, since that is the first version of Windows that contains the Windows
-Overlay File System Filter Driver ("WOF").  If the WOF driver is detected,
-wimlib will create the WIMBoot "pointer files" using documented ioctls provided
-by WOF.
+Overlay Filesystem filter driver ("WOF").  If the WOF driver is detected, wimlib
+will create the WIMBoot "pointer files" using documented ioctls provided by WOF.
 .IP ""
 Otherwise, if the WOF driver is not detected, wimlib will create the reparse
 points and edit the file "\\System Volume Information\\WimOverlay.dat" on the
@@ -456,7 +455,7 @@ wimlib-imagex apply install.wim 1 /dev/sda2
 .PP
 Note that before running either of the above commands, an NTFS filesystem may
 need to be created on the partition, for example with format.exe on Windows or
-\fBmkntfs\fR(8) (part of NTFS-3g) on UNIX-like systems.  For example, you might
+\fBmkntfs\fR(8) (part of NTFS-3G) on UNIX-like systems.  For example, you might
 run:
 .RS
 .PP