doc: Fix Spelling Error of Rados Operations

Signed-off-by: Li Bingyang <li.bingyang1@zte.com.cn>

diff --git a/doc/rados/operations/add-or-rm-osds.rst b/doc/rados/operations/add-or-rm-osds.rst
index 89d16f9f5a113c526ee17eaa192557289ba100be..9e6682f4570b35fd45a63ea22168d1ebf5099a52 100644 (file)
--- a/doc/rados/operations/add-or-rm-osds.rst
+++ b/doc/rados/operations/add-or-rm-osds.rst
@@ -135,7 +135,7 @@ weight).
 Replacing an OSD
 ----------------
 
-When disks fail, or if an admnistrator wants to reprovision OSDs with a new
+When disks fail, or if an administrator wants to reprovision OSDs with a new
 backend, for instance, for switching from FileStore to BlueStore, OSDs need to
 be replaced. Unlike `Removing the OSD`_, replaced OSD's id and CRUSH map entry
 need to be keep intact after the OSD is destroyed for replacement.

diff --git a/doc/rados/operations/bluestore-migration.rst b/doc/rados/operations/bluestore-migration.rst
index 56ecce196ebd9b8c7773398381eed11d1d83c6c9..91a64c9314e7dec94c2cf5a958414d7cc2320b18 100644 (file)
--- a/doc/rados/operations/bluestore-migration.rst
+++ b/doc/rados/operations/bluestore-migration.rst
@@ -32,7 +32,7 @@ Mark out and replace
 --------------------
 
 The simplest approach is to mark out each device in turn, wait for the
-data to rereplicate across the cluster, reprovision the OSD, and mark
+data to replicate across the cluster, reprovision the OSD, and mark
 it back in again.  It is simple and easy to automate.  However, it requires
 more data migration than should be necessary, so it is not optimal.