summaryrefslogtreecommitdiff
path: root/docs-xml
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2011-05-27 08:42:30 +0200
committerVolker Lendecke <vl@samba.org>2011-05-27 08:43:47 +0200
commit127d417e8ebc967572df7a75b342897a6a8fb71e (patch)
tree1ee14851f9960cffabb82e1b74dae49731e66c31 /docs-xml
parente05c9cdcb6bf710ddb7d683916ca26857a3bce18 (diff)
downloadsamba-127d417e8ebc967572df7a75b342897a6a8fb71e.tar.gz
samba-127d417e8ebc967572df7a75b342897a6a8fb71e.tar.bz2
samba-127d417e8ebc967572df7a75b342897a6a8fb71e.zip
s3: Fix a typo
Thanks to Samba-JP oota <ribbon@samba.gr.jp>
Diffstat (limited to 'docs-xml')
-rw-r--r--docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml b/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml
index 945070393c..dca43df429 100644
--- a/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml
+++ b/docs-xml/manpages-3/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. Ultimativly, if the module uses
+ uses features only implemented in the newer subrelease. Ultimatively, 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.