s3:locking: Fix code spelling

Signed-off-by: Andreas Schneider <asn@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>

diff --git a/source3/locking/brlock.c b/source3/locking/brlock.c
index d065c7fe03e85222c2b8e0fe7e681a311beb544f..905da049c588d50b8670ac8af649980a845c7f55 100644 (file)
--- a/source3/locking/brlock.c
+++ b/source3/locking/brlock.c
@@ -877,7 +877,7 @@ static NTSTATUS brl_lock_posix(struct byte_range_lock *br_lck,
 
        /*
         * Break oplocks while we hold a brl. Since lock() and unlock() calls
-        * are not symetric with POSIX semantics, we cannot guarantee our
+        * are not symmetric with POSIX semantics, we cannot guarantee our
         * contend_level2_oplocks_begin/end calls will be acquired and
         * released one-for-one as with Windows semantics. Therefore we only
         * call contend_level2_oplocks_begin if this is the first POSIX brl on

diff --git a/source3/locking/locking.c b/source3/locking/locking.c
index 5c2613b117cb248e6b1d8d3f7877a3c3023ead66..6ee5987ffda46310777a273976ce557602eac8ab 100644 (file)
--- a/source3/locking/locking.c
+++ b/source3/locking/locking.c
@@ -435,7 +435,7 @@ void locking_close_file(files_struct *fsp,
                /*
                 * Unlocks must trigger dbwrap_watch watchers,
                 * normally in smbd_do_unlocking. Here it's done
-                * implictly, we're closing the file and thus remove a
+                * implicitly, we're closing the file and thus remove a
                 * share mode. This will wake the waiters.
                 */
                brl_close_fnum(br_lck);

diff --git a/source3/locking/posix.c b/source3/locking/posix.c
index ccc9d6276dabc3f0dd42e144e09a0c9af6a9cafb..eedbbc1c58b3a630d47f707587a90f69112abd3f 100644 (file)
--- a/source3/locking/posix.c
+++ b/source3/locking/posix.c
@@ -920,7 +920,7 @@ bool set_posix_lock_windows_flavour(files_struct *fsp,
        }
 
        /*
-        * Windows is very strange. It allows read locks to be overlayed
+        * Windows is very strange. It allows read locks to be overlaid
         * (even over a write lock), but leaves the write lock in force until the first
         * unlock. It also reference counts the locks. This means the following sequence :
         *