X-Git-Url: https://wimlib.net/git/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fman1%2Fimagex-split.1.in;h=681751bb8f286bc17b204309d2a9f1756e40b61d;hb=5b6eaafbaab217fc69946685862a09afa28b30cb;hp=8e7d3c0e3e375abe3ad74a44860153fe89f33d59;hpb=c07877105822d01725b36b011c93609559164b06;p=wimlib

diff --git a/doc/man1/imagex-split.1.in b/doc/man1/imagex-split.1.in
index 8e7d3c0e..681751bb 100644
--- a/doc/man1/imagex-split.1.in
+++ b/doc/man1/imagex-split.1.in
@@ -1,4 +1,4 @@
-.TH WIMLIB-IMAGEX "1" "March 2014" "@IMAGEX_PROGNAME@ @VERSION@" "User Commands"
+.TH WIMLIB-IMAGEX "1" "October 2014" "@IMAGEX_PROGNAME@ @VERSION@" "User Commands"
 .SH NAME
 @IMAGEX_PROGNAME@-split \- Split a WIM into multiple parts
 .SH SYNOPSIS
@@ -26,8 +26,8 @@ etc. where each part is at most 100 MiB:
 @IMAGEX_PROGNAME@ split windows.wim windows.swm 100
 .RE
 .SH LIMITATIONS
-It it possible for the size of the parts to exceed the \fIPART_SIZE\fR given.
-This is impossible to avoid and Microsoft's program has this problem as well
+It is possible for the size of the parts to exceed the \fIPART_SIZE\fR given.
+This is impossible to avoid
 because the WIM file format provides no way to divide a single file resource in
 the WIM among multiple split WIM parts.  So if you, for example, have a file
 inside the WIM that is 100 MiB, then an uncompressed split WIM will have at