doc: fix a couple grammatical things

Signed-off-by: Brad Fitzpatrick <brad@danga.com>

diff --git a/doc/rados/operations/crush-map-edits.rst b/doc/rados/operations/crush-map-edits.rst
index 608473eb0dab8ad7de3509ff55cea1051cfe9c37..88ac45705a6a61fa47b20d8bd24ef0b1f34b29d8 100644 (file)
--- 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 d0eea6c6fa6dba052ca1381baa2104085df663f3..b8e5da9de62594a97266742c479e465efe306791 100644 (file)
--- 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.