Spelling correction: exlusive -> exclusive and semantincs -> semantics

Signed-off-by: Paul Wayper <paulway@redhat.com>
Reviewed-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Volker Lendecke <vl@samba.org>
Autobuild-User(master): Volker Lendecke <vl@samba.org>
Autobuild-Date(master): Wed Jul  8 15:54:15 CEST 2015 on sn-devel-104

diff --git a/ctdb/doc/readonlyrecords.txt b/ctdb/doc/readonlyrecords.txt
index d108ffde36adc7a40035819be25ebfa378c06968..5374a855ddfecb74950e106a1a16eecf56a48afa 100644 (file)
--- a/ctdb/doc/readonlyrecords.txt
+++ b/ctdb/doc/readonlyrecords.txt
@@ -12,7 +12,7 @@ rapidly bounce between nodes and acts as a scalability limitation.
 This primarily affects locking.tdb and brlock.tdb, two databases where record access is 
 read-mostly and where writes are semi-rare.
 
-For the common case, if CTDB provided shared non-exlusive Read-Only lock semantincs
+For the common case, if CTDB provided shared non-exclusive Read-Only lock semantics
 this would greatly improve scaling for these workloads.