From 1ac610998a940763146f8b2508fb7a519ae49de1 Mon Sep 17 00:00:00 2001
From: Karolin Seeger <kseeger@samba.org>
Date: Thu, 12 Sep 2013 09:20:03 +0200
Subject: [PATCH] docs: Fix typos.

This is a follow-up patch for bug #10134 - Samba 4.0 is stricter in checking
acls for "open for execution".

Signed-off-by: Karolin Seeger <kseeger@samba.org>
---
 docs-xml/smbdotconf/protocol/aclallowexecutealways.xml |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs-xml/smbdotconf/protocol/aclallowexecutealways.xml b/docs-xml/smbdotconf/protocol/aclallowexecutealways.xml
index 048c388..49d2c48 100644
--- a/docs-xml/smbdotconf/protocol/aclallowexecutealways.xml
+++ b/docs-xml/smbdotconf/protocol/aclallowexecutealways.xml
@@ -11,15 +11,15 @@
     With Samba 3.6 and older, the execution right in the ACL was not checked, so a client
     could execute a file even if it did not have execute rights on the file. In Samba 4.0,
     this has been fixed, so that by default, i.e. when this parameter is set to "False",
-    open for execution is now denied when execution permissions are not present.
+    "open for execution" is now denied when execution permissions are not present.
     </para>
     <para>
     If this parameter is set to "True", Samba does not check execute permissions on
-    "open for execution, thus re-establishing the behaviour of Samba 3.6.
+    "open for execution", thus re-establishing the behaviour of Samba 3.6.
     This can be useful to smoothen upgrades from older Samba versions to 4.0 and newer.
     This setting is not not meant to be used as a permanent setting, but as a temporary relief:
     It is recommended to fix the permissions in the ACLs and reset this parameter to the
-    default after a ceratain transition period.
+    default after a certain transition period.
     </para>
 </description>
 <value type="default">False</value>
-- 
1.7.10.4