summaryrefslogtreecommitdiff
path: root/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml')
-rw-r--r--docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml b/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml
index 0daafc62a3..38644e7bc5 100644
--- a/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml
+++ b/docs-xml/manpages/vfs_smb_traffic_analyzer.8.xml
@@ -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.