X-Git-Url: https://wimlib.net/git/?a=blobdiff_plain;f=doc%2Fimagex-split.1.in;h=eff44184177f071d148476458d6653fb7ca635c5;hb=75616449d7d57594867e785eba40d8594411c9d2;hp=270d4bb24151b618c446e93837a379056222da3e;hpb=4f9947253f6a08f4a922d3efe0880e3039b3eb5e;p=wimlib

diff --git a/doc/imagex-split.1.in b/doc/imagex-split.1.in
index 270d4bb2..eff44184 100644
--- a/doc/imagex-split.1.in
+++ b/doc/imagex-split.1.in
@@ -1,4 +1,4 @@
-.TH IMAGEX "1" "May 2012" "imagex (wimlib) wimlib @VERSION@" "User Commands"
+.TH IMAGEX "1" "September 2012" "imagex (wimlib) wimlib @VERSION@" "User Commands"
 .SH NAME
 imagex split \- Split a WIM into multiple parts
 
@@ -8,7 +8,7 @@ imagex split \- Split a WIM into multiple parts
 .SH DESCRIPTION
 .PP
 
-Splits \fIWIMFILE\fR into parts with size at most \fIPART_SIZE\fR megabytes,
+Splits \fIWIMFILE\fR into parts with size at most \fIPART_SIZE\fR mebibytes,
 with the first part having the name \fISPLIT_WIMFILE\fR and the other parts
 having names numbered in order of the parts.
 
@@ -34,8 +34,8 @@ This is impossible to avoid and Microsoft's program has this problem as well
 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
-least one part that is 100 MiB in size to contain that file.  If the WIM
-resources are compressed then less space would be needed.
+least one part that is 100 MiB in size to contain that file.  However, if the
+WIM resources are compressed then less space would be needed.
 
 .SH SEE ALSO
 .BR imagex (1)