Correct "acheive" typos.

Signed-off-by: Chris Lamb <chris@chris-lamb.co.uk>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Garming Sam <garming@catalyst.net.nz>

diff --git a/ctdb/doc/ctdb.7.xml b/ctdb/doc/ctdb.7.xml
index c8b124d537b6fadfc7bba7c3d667e4a20a619e52..db0a627984c1a8479117ac22825ff1dba012ecea 100644 (file)
--- a/ctdb/doc/ctdb.7.xml
+++ b/ctdb/doc/ctdb.7.xml
@@ -543,7 +543,7 @@ Node 3:/usr/local/etc/ctdb/public_addresses
       requests are going through the LVSMASTER bottleneck and the
       majority of the traffic volume (the data in the read replies)
       goes straight from the processing node back to the clients. For
-      read-intensive i/o patterns you can acheive very high throughput
+      read-intensive i/o patterns you can achieve very high throughput
       rates in this mode.
     </para>
 

diff --git a/python/samba/tests/kcc/__init__.py b/python/samba/tests/kcc/__init__.py
index 5cf6a253b7b4aed16fb14f61e99273befd02d3bb..2597388c167e8ef4a7f6a79f8435971aead8707a 100644 (file)
--- a/python/samba/tests/kcc/__init__.py
+++ b/python/samba/tests/kcc/__init__.py
@@ -69,7 +69,7 @@ class KCCTests(samba.tests.TestCase):
 
     def test_verify(self):
         """check that the KCC generates graphs that pass its own verify
-        option. This is not a spectacular acheivement when there are
+        option. This is not a spectacular achievement when there are
         only a couple of nodes to connect, but it shows something.
         """
         my_kcc = kcc.KCC(unix_now, readonly=True, verify=True,