From: Brad Fitzpatrick Date: Tue, 3 Jan 2023 16:36:19 +0000 (-0800) Subject: doc: fix a couple grammatical things X-Git-Tag: v16.2.11~17^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=refs%2Fpull%2F49622%2Fhead;p=ceph.git doc: fix a couple grammatical things Signed-off-by: Brad Fitzpatrick (cherry picked from commit b9b6011c11450e292e4d233a444d776cca8fd86e) --- diff --git a/doc/rados/operations/crush-map-edits.rst b/doc/rados/operations/crush-map-edits.rst index e324e6345f60..18553e47d704 100644 --- a/doc/rados/operations/crush-map-edits.rst +++ b/doc/rados/operations/crush-map-edits.rst @@ -211,8 +211,8 @@ distribution units, pods, rows, rooms, and data centers. With the exception of the leaf nodes representing OSDs, the rest of the hierarchy is arbitrary, and you may define it according to your own needs. -We recommend adapting your CRUSH map to your firms's hardware naming conventions -and using instances names that reflect the physical hardware. Your naming +We recommend adapting your CRUSH map to your firm's hardware naming conventions +and using instance names that reflect the physical hardware. Your naming practice can make it easier to administer the cluster and troubleshoot problems when an OSD and/or other hardware malfunctions and the administrator need access to physical hardware. diff --git a/doc/rados/operations/crush-map.rst b/doc/rados/operations/crush-map.rst index 0d5405928dbe..f22ebb24e313 100644 --- a/doc/rados/operations/crush-map.rst +++ b/doc/rados/operations/crush-map.rst @@ -1002,7 +1002,7 @@ sets known as *profiles*. As of the Octopus release these are: * ``firefly``: the values supported by the firefly release * ``hammer``: the values supported by the hammer release * ``jewel``: the values supported by the jewel release - * ``optimal``: the best (ie optimal) values of the current version of Ceph + * ``optimal``: the best (i.e. optimal) values of the current version of Ceph * ``default``: the default values of a new cluster installed from scratch. These values, which depend on the current version of Ceph, are hardcoded and are generally a mix of optimal and legacy values.