doc: Fixed a spelling error.

Corrected communicte to communicate

Signed-off-by: Instelligence.io <github@instelligence.io>
(cherry picked from commit c328902e3929d9841f952948b0336ec5b20d36fa)

diff --git a/doc/rados/operations/stretch-mode.rst b/doc/rados/operations/stretch-mode.rst
index 09b6723242d8ab60b89c79d5c463b0fd32697fac..e0fba85e123516bd206be0c6c77d2f43eed0c8af 100644 (file)
--- a/doc/rados/operations/stretch-mode.rst
+++ b/doc/rados/operations/stretch-mode.rst
@@ -63,7 +63,7 @@ you might discover that your cluster does not satisfy those constraints.
 
 The first category of these failures that we will discuss involves inconsistent
 networks. If there is a netsplit (a failure that
-splits the network into two conceptual islands that cannot communicte with
+splits the network into two conceptual islands that cannot communicate with
 each other), Ceph might be unable to mark OSDs ``down``
 and remove them from Placement Group (PG) acting sets. This failure to mark ODSs ``down``
 will occur despite the fact that the primary PG is unable to replicate data (a