vmsplice.2: Minor wording fixes

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/vmsplice.2

@@ -65,8 +65,8 @@ structures as defined in
 .in +4n
 .nf
 struct iovec {
-    void  *iov_base;            /* Starting address */
-    size_t iov_len;             /* Number of bytes */
+    void  *iov_base;        /* Starting address */
+    size_t iov_len;         /* Number of bytes */
 };
 .in
 .fi
@@ -99,7 +99,7 @@ but may be implemented in the future; see
 The user pages are a gift to the kernel.
 The application may not modify this memory ever,
 .\" FIXME . Explain the following line in a little more detail:
-or page cache and on-disk data may differ.
+otherwise the page cache and on-disk data may differ.
 Gifting pages to the kernel means that a subsequent
 .BR splice (2)
 .B SPLICE_F_MOVE
@@ -155,12 +155,14 @@ This system call is Linux-specific.
 .SH NOTES
 .BR vmsplice ()
 follows the other vectorized read/write type functions when it comes to
-limitations on number of segments being passed in.
+limitations on the number of segments being passed in.
 This limit is
 .B IOV_MAX
 as defined in
 .IR <limits.h> .
-At the time of this writing, that limit is 1024.
+Currently,
+.\" UIO_MAXIOV in kernel source
+this limit is 1024.
 .SH SEE ALSO
 .BR splice (2),
 .BR tee (2)