Mark VSS support non-experimental

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

diff --git a/doc/man1/wimlib-imagex-capture.1 b/doc/man1/wimlib-imagex-capture.1
index 05197006d0083fa069c02f75df67a09a138ef4f8..5e5353ecd976f074cd08310a0b57d92a0e90928e 100644 (file)
--- a/doc/man1/wimlib-imagex-capture.1
+++ b/doc/man1/wimlib-imagex-capture.1
@@ -1,4 +1,4 @@
-.TH WIMLIB-IMAGEX "1" "November 2015" "wimlib 1.8.3" "User Commands"
+.TH WIMLIB-IMAGEX "1" "January 2016" "wimlib 1.9.0" "User Commands"
 .SH NAME
 wimlib-imagex-capture, wimlib-imagex-append \- Create or append a WIM image
 .SH SYNOPSIS
@@ -578,11 +578,11 @@ however, this may still be overridden through the \fB--config\fR parameter.
 See the documentation for this option in \fBwimlib-imagex-optimize\fR (1).
 .TP
 \fB--snapshot\fR
-EXPERIMENTAL: create a temporary filesystem snapshot of the source directory and
-capture the files from it.  Currently, this option is only supported on Windows,
-where it uses the Volume Shadow Copy Service (VSS).  Using this option, you can
-create a consistent backup of the system volume of a running Windows system
-without running into problems with locked files.  For the VSS snapshot to be
+Create a temporary filesystem snapshot of the source directory and capture the
+files from it.  Currently, this option is only supported on Windows, where it
+uses the Volume Shadow Copy Service (VSS).  Using this option, you can create a
+consistent backup of the system volume of a running Windows system without
+running into problems with locked files.  For the VSS snapshot to be
 successfully created, \fBwimlib-imagex\fR must be run as an Administrator, and
 it cannot be run in WoW64 mode (i.e. if Windows is 64-bit, then
 \fBwimlib-imagex\fR must be 64-bit as well).