X-Git-Url: https://wimlib.net/git/?p=wimlib;a=blobdiff_plain;f=doc%2Fimagex-apply.1.in;h=d60c53d64acbc6386c92b1fca3e2b9e61086b81b;hp=5197f78f8e537c2ec19ace71c7944cfd4ec838af;hb=a381a9e10a60c7790fe33255c949bf55b5872a8d;hpb=b3f9603319e1b9c674460f3d864808d272c11338

diff --git a/doc/imagex-apply.1.in b/doc/imagex-apply.1.in
index 5197f78f..d60c53d6 100644
--- a/doc/imagex-apply.1.in
+++ b/doc/imagex-apply.1.in
@@ -201,8 +201,8 @@ UNIX version.
 
 \fBimagex apply\fR does not have separate "normal" and "NTFS" modes on Windows.
 There is simply one mode, and it uses the Windows API to apply NTFS-specific
-information, including alternate data streams, reparse points, hard link, and
-symbolic links.  So, you essentially get the advantages of the "NTFS mode"
+information, including alternate data streams, reparse points, hard links, and
+file attributes.  So, you essentially get the advantages of the "NTFS mode"
 documented above, but you can apply the WIM image to any directory, not just an
 entire NTFS volume.  This is mostly the same behavior as Microsoft's ImageX.