summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn Wilkins <john.wilkins@inktank.com>2013-04-30 17:39:50 -0700
committerJohn Wilkins <john.wilkins@inktank.com>2013-04-30 17:39:50 -0700
commitbb93ebaaf86cb18b9a5fca17ea0a43c99b7dd500 (patch)
tree507ad68080e079a9dbcbe83bf4b90d777caf092d
parent14ce0ad1772249bf00d4f909f0bfe89f6745ff48 (diff)
downloadceph-bb93ebaaf86cb18b9a5fca17ea0a43c99b7dd500.tar.gz
doc: Fixed a few typos.
Signed-off-by: John Wilkins <john.wilkins@inktank.com>
-rw-r--r--doc/install/upgrading-ceph.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/install/upgrading-ceph.rst b/doc/install/upgrading-ceph.rst
index e1c906e87ce..0cccfd54d95 100644
--- a/doc/install/upgrading-ceph.rst
+++ b/doc/install/upgrading-ceph.rst
@@ -23,7 +23,7 @@ daemons in this order:
As a general rule, we recommend upgrading all the daemons of a specific type
(e.g., all ``ceph-osd`` daemons, all ``ceph-mon`` daemons, etc.) to ensure that
they are all on the same release. We also recommend that you upgrade all the
-daemons in your cluster before you try to exorcise new functionality in a
+daemons in your cluster before you try to exercise new functionality in a
release.
@@ -32,7 +32,7 @@ Release-specific Upgrade Details
Each release of Ceph may have some additional steps. Refer to the following
sections to identify release-specific procedures for your cluster before
-using the updgrade procedures.
+using the upgrade procedures.
Upgrading from Argonaut to Bobtail