summaryrefslogtreecommitdiff
path: root/ctdb
diff options
context:
space:
mode:
authorBjörn Jacke <bj@sernet.de>2019-10-26 02:41:08 +0200
committerBjoern Jacke <bjacke@samba.org>2019-10-31 00:43:38 +0000
commitcb867b29c9ca2ef7ea7c9f80228f60b32329dd6f (patch)
tree2c31530bb9e6a38c671bfd71ea59c417e823be37 /ctdb
parent93859b3394d87f1521f757111eb8e55633c8cde3 (diff)
downloadsamba-cb867b29c9ca2ef7ea7c9f80228f60b32329dd6f.tar.gz
ctdb/doc/ctdb.1.xml: typo fixes
Signed-off-by: Bjoern Jacke <bjacke@samba.org> Reviewed-by: Martin Schwenke <martin@meltin.net>
Diffstat (limited to 'ctdb')
-rw-r--r--ctdb/doc/ctdb.1.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/ctdb/doc/ctdb.1.xml b/ctdb/doc/ctdb.1.xml
index e355752d1db..a204583b62c 100644
--- a/ctdb/doc/ctdb.1.xml
+++ b/ctdb/doc/ctdb.1.xml
@@ -198,7 +198,7 @@
<varlistentry><term>--usage</term>
<listitem>
<para>
- Print useage information to the screen.
+ Print usage information to the screen.
</para>
</listitem>
</varlistentry>
@@ -1359,7 +1359,7 @@ DB Statistics: locking.tdb
If a PERSISTENT database is not in a healthy state the database
is flagged as UNHEALTHY. If there's at least one completely
healthy node running in the cluster, it's possible that the
- content is restored by a recovery run automaticly. Otherwise an
+ content is restored by a recovery run automatically. Otherwise an
administrator needs to analyze the problem.
</para>
<para>