From 50dc8d0e4ab00ae28a73c52481c37c7574711ab0 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Fri, 27 May 2011 08:42:30 +0200 Subject: [PATCH] s3: Fix a typo Thanks to Samba-JP oota (cherry picked from commit 127d417e8ebc967572df7a75b342897a6a8fb71e) (cherry picked from commit b747545fa4cd8985f4e06a08623d38205fa5d0cf) --- docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 945070393cd..dca43df4298 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. -- 2.11.4.GIT