summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorBrad Fitzpatrick <brad@danga.com>2023-01-03 17:36:19 +0100
committerBrad Fitzpatrick <brad@danga.com>2023-01-03 17:37:02 +0100
commitb9b6011c11450e292e4d233a444d776cca8fd86e (patch)
tree681b23382f3a2ef2b23c1d44ce8f7f9be4fc844a /doc
parentMerge pull request #49606 from zdover23/wip-doc-2023-01-01-start-documenting-... (diff)
downloadceph-b9b6011c11450e292e4d233a444d776cca8fd86e.tar.xz
ceph-b9b6011c11450e292e4d233a444d776cca8fd86e.zip
doc: fix a couple grammatical things
Signed-off-by: Brad Fitzpatrick <brad@danga.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/rados/operations/crush-map-edits.rst4
-rw-r--r--doc/rados/operations/crush-map.rst2
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/rados/operations/crush-map-edits.rst b/doc/rados/operations/crush-map-edits.rst
index 608473eb0da..88ac45705a6 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 d0eea6c6fa6..b8e5da9de62 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.