docs: Bump version in meta data up to 4.1.

[amitay/samba.git] / docs-xml / manpages / vfs_smb_traffic_analyzer.8.xml

diff --git a/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml b/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml
index 0daafc62a365ad55b7c690276b0ab6fae37a8d91..ef3ca074f3d4b6665a352fe6da00f5bda1848e73 100644 (file)
--- a/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml
+++ b/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml
@@ -7,7 +7,7 @@
        <manvolnum>8</manvolnum>
        <refmiscinfo class="source">Samba</refmiscinfo>
        <refmiscinfo class="manual">System Administration tools</refmiscinfo>
-       <refmiscinfo class="version">4.0</refmiscinfo>
+       <refmiscinfo class="version">4.1</refmiscinfo>
 </refmeta>
 
 
@@ -139,7 +139,7 @@
                The module now can identify itself against the receiver with a sub-release number, where
                the receiver may run with a different sub-release number than the module. However, as
                long as both run on the V2.x protocol, the receiver will not crash, even if the module
-               uses features only implemented in the newer subrelease. Ultimatively, if the module uses
+               uses features only implemented in the newer subrelease. Ultimately, if the module uses
                a new feature from a newer subrelease, and the receiver runs an older protocol, it is just
                ignoring the functionality. Of course it is best to have both the receiver and the module
                running the same subrelease of the protocol.