Standardize wording: "since wimlib vX.X.X"

diff --git a/doc/man1/wimlib-imagex-apply.1 b/doc/man1/wimlib-imagex-apply.1
index ac50318f8453540c9ccf9b38b49b00b3bbfb6dbe..1680a9448465c0824ef44086619e63e5bc115339 100644 (file)
--- a/doc/man1/wimlib-imagex-apply.1
+++ b/doc/man1/wimlib-imagex-apply.1
@@ -254,13 +254,13 @@ option is unneeded; instead you must ensure that all the split WIM parts are
 concatenated together on standard input.  They can be provided in any order,
 with the exception of the first part, which must be first.
 .SH PIPABLE WIMS
-As of wimlib 1.5.0, \fBwimlib-imagex apply\fR supports applying a WIM from a
+Since wimlib v1.5.0, \fBwimlib-imagex apply\fR supports applying a WIM from a
 nonseekable file, such as a pipe, provided that the WIM was captured with
-\fB--pipable\fR (see \fBwimlib-imagex capture\fR(1)).  To use standard input
-as the WIM, specify "-" as \fIWIMFILE\fR.  A useful use of this ability is to
-apply an image from a WIM while streaming it from a server.  For example, to
-apply the first image from a WIM file available on a HTTP server to an NTFS
-volume on /dev/sda1, run something like:
+\fB--pipable\fR (see \fBwimlib-imagex capture\fR(1)).  To use standard input as
+the WIM, specify "-" as \fIWIMFILE\fR.  A useful use of this ability is to apply
+an image from a WIM while streaming it from a server.  For example, to apply the
+first image from a WIM file available on a HTTP server to an NTFS volume on
+/dev/sda1, run something like:
 .PP
 .RS
 wget -O - http://myserver/mywim.wim | wimapply - 1 /dev/sda1
@@ -305,11 +305,10 @@ UNIX-like systems.
 .TP
 \fB--unix-data\fR
 (UNIX-like systems only)  Restore UNIX owners, groups, modes, and device IDs
-(major and minor numbers) that were captured by \fBwimlib-imagex capture\fR
-with the \fB--unix-data\fR option.  As of wimlib v1.7.0, you can backup and
-restore not only the standard UNIX file permission information, but also
-character device nodes, block device nodes, named pipes (FIFOs), and UNIX domain
-sockets.
+(major and minor numbers) that were captured by \fBwimlib-imagex capture\fR with
+the \fB--unix-data\fR option.  Since wimlib v1.7.0, you can backup and restore
+not only the standard UNIX file permission information, but also character
+device nodes, block device nodes, named pipes (FIFOs), and UNIX domain sockets.
 .TP
 \fB--no-acls\fR
 Do not restore security descriptors on extracted files and directories.

diff --git a/doc/man1/wimlib-imagex-capture.1 b/doc/man1/wimlib-imagex-capture.1
index 31dc74c9c7673a68744ef762d123dec4190723fb..c8fae9496fe6ab896c723dd2dd32677ab57aea00 100644 (file)
--- a/doc/man1/wimlib-imagex-capture.1
+++ b/doc/man1/wimlib-imagex-capture.1
@@ -361,7 +361,7 @@ that may be present on the filesystem.
 .TP
 \fB--unix-data\fR
 (UNIX-like systems only) Store the UNIX owner, group, mode, and device ID (major
-and minor number) of each captured file.  As of wimlib v1.7.0, you can backup
+and minor number) of each captured file.  Since wimlib v1.7.0, you can backup
 and restore not only the standard UNIX file permission information, but also
 character device nodes, block device nodes, named pipes (FIFOs), and UNIX domain
 sockets.

diff --git a/include/wimlib.h b/include/wimlib.h
index 02b1ce9f08688c0fe22aa69d784bffb00cdc7cef..cd341e694cc73c0898c48a3126922110a596d913 100644 (file)
--- a/include/wimlib.h
+++ b/include/wimlib.h
@@ -16,8 +16,7 @@
  * Windows Imaging Format.  This documentation is intended for developers only.
  * If you have installed wimlib and want to know how to use the @b wimlib-imagex
  * program, please see the manual pages and also the <a
- * href="https://wimlib.net/gitlist/wimlib/blob/master/README">README
- * file</a>.
+ * href="https://wimlib.net/gitlist/wimlib/blob/master/README">README file</a>.
  *
  * @section sec_installing Installing
  *
@@ -346,10 +345,10 @@
  * such as wimlib_join(), also take the progress function directly using an
  * extended version of the function, such as wimlib_join_with_progress().
  *
- * In wimlib v1.7.0 and later, progress functions are no longer just
- * unidirectional.  You can now return ::WIMLIB_PROGRESS_STATUS_ABORT to cause
- * the current operation to be aborted.  wimlib v1.7.0 also added the third
- * argument to ::wimlib_progress_func_t, which is a user-supplied context.
+ * Since wimlib v1.7.0, progress functions are no longer just unidirectional.
+ * You can now return ::WIMLIB_PROGRESS_STATUS_ABORT to cause the current
+ * operation to be aborted.  wimlib v1.7.0 also added the third argument to
+ * ::wimlib_progress_func_t, which is a user-supplied context.
  */
 
 /** @defgroup G_writing_and_overwriting_wims Writing and Overwriting WIMs
@@ -1063,8 +1062,8 @@ union wimlib_progress_info {
 
                /** Name of the split WIM part that is about to be started
                 * (::WIMLIB_PROGRESS_MSG_SPLIT_BEGIN_PART) or has just been
-                * finished (::WIMLIB_PROGRESS_MSG_SPLIT_END_PART).
-                * As of wimlib v1.7.0, the library user may change this when
+                * finished (::WIMLIB_PROGRESS_MSG_SPLIT_END_PART).  Since
+                * wimlib v1.7.0, the library user may change this when
                 * receiving ::WIMLIB_PROGRESS_MSG_SPLIT_BEGIN_PART in order to
                 * cause the next split WIM part to be written to a different
                 * location.  */
@@ -1461,8 +1460,8 @@ struct wimlib_stream_entry {
 };
 
 /**
- * An object ID, which is an extra piece of metadata that may be associated with
- * a file on NTFS filesystems.  See:
+ * Since wimlib v1.9.1: an object ID, which is an extra piece of metadata that
+ * may be associated with a file on NTFS filesystems.  See:
  * https://msdn.microsoft.com/en-us/library/windows/desktop/aa363997(v=vs.85).aspx
  */
 struct wimlib_object_id {