summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJohn Terpstra <jht@samba.org>2007-01-27 01:13:46 +0000
committerGerald W. Carter <jerry@samba.org>2008-04-23 08:47:24 -0500
commit19fb5806e487f7b939a86a55360df1d07b96f22f (patch)
tree5609fb4766bbb3e5f4ee1cb80dc821c42d4f6264 /docs
parentf1eee655861457174a0382b76e8fd718ae932494 (diff)
downloadsamba-19fb5806e487f7b939a86a55360df1d07b96f22f.tar.gz
samba-19fb5806e487f7b939a86a55360df1d07b96f22f.tar.bz2
samba-19fb5806e487f7b939a86a55360df1d07b96f22f.zip
Fix typos reported in Bug#4358
(This used to be commit 2bbb60984e7194a5f5f60339ff3f34e72c414368)
Diffstat (limited to 'docs')
-rw-r--r--docs/smbdotconf/security/encryptpasswords.xml2
-rw-r--r--docs/smbdotconf/security/lanmanauth.xml2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/smbdotconf/security/encryptpasswords.xml b/docs/smbdotconf/security/encryptpasswords.xml
index 8d2b86cb8c..1a631fd098 100644
--- a/docs/smbdotconf/security/encryptpasswords.xml
+++ b/docs/smbdotconf/security/encryptpasswords.xml
@@ -14,7 +14,7 @@
<para>
MS Windows clients that expect Microsoft encrypted passwords and that
do not have plain text password support enabled will be able to
- connect only to a Samba server that has encypted password support
+ connect only to a Samba server that has encrypted password support
enabled and for which the user accounts have a valid encrypted password.
Refer to the smbpasswd command man page for information regarding the
creation of encrypted passwords for user accounts.
diff --git a/docs/smbdotconf/security/lanmanauth.xml b/docs/smbdotconf/security/lanmanauth.xml
index c0b5e52af0..056cdc8bd2 100644
--- a/docs/smbdotconf/security/lanmanauth.xml
+++ b/docs/smbdotconf/security/lanmanauth.xml
@@ -17,7 +17,7 @@
without Windows 95/98/ME or MS DOS clients are advised to disable
this option. </para>
- <para>Unlike the <command moreinfo="none">encypt
+ <para>Unlike the <command moreinfo="none">encrypt
passwords</command> option, this parameter cannot alter client
behaviour, and the LANMAN response will still be sent over the
network. See the <command moreinfo="none">client lanman