Signed-off-by: Li Bingyang <li.bingyang1@zte.com.cn>
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.
--------------------
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.