From: 李丙洋 10208981 Date: Tue, 4 Sep 2018 01:17:18 +0000 (+0800) Subject: doc: Fix Spelling Error of Rados Operations X-Git-Tag: v14.0.1~425^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=refs%2Fpull%2F23900%2Fhead;p=ceph.git doc: Fix Spelling Error of Rados Operations Signed-off-by: Li Bingyang --- diff --git a/doc/rados/operations/crush-map-edits.rst b/doc/rados/operations/crush-map-edits.rst index 8218451c01b7..f1939ddcdcd7 100644 --- a/doc/rados/operations/crush-map-edits.rst +++ b/doc/rados/operations/crush-map-edits.rst @@ -73,7 +73,7 @@ There are six main sections to a CRUSH Map. #. **buckets:** Once you define bucket types, you must define each node in the hierarchy, its type, and which devices or other nodes it - containes. + contains. #. **rules:** Rules define policy about how data is distributed across devices in the hierarchy. @@ -95,7 +95,7 @@ cluster. Devices are identified by an id (a non-negative integer) and a name, normally ``osd.N`` where ``N`` is the device id. Devices may also have a *device class* associated with them (e.g., -``hdd`` or ``ssd``), allowing them to be conveniently targetted by a +``hdd`` or ``ssd``), allowing them to be conveniently targeted by a crush rule. :: diff --git a/doc/rados/operations/crush-map.rst b/doc/rados/operations/crush-map.rst index 7a2edd62d2b1..638c17f64cd8 100644 --- a/doc/rados/operations/crush-map.rst +++ b/doc/rados/operations/crush-map.rst @@ -122,7 +122,7 @@ cluster. Devices are identified by an id (a non-negative integer) and a name, normally ``osd.N`` where ``N`` is the device id. Devices may also have a *device class* associated with them (e.g., -``hdd`` or ``ssd``), allowing them to be conveniently targetted by a +``hdd`` or ``ssd``), allowing them to be conveniently targeted by a crush rule. Types and Buckets diff --git a/doc/rados/operations/placement-groups.rst b/doc/rados/operations/placement-groups.rst index dcff42bc5caf..6d94ccac2516 100644 --- a/doc/rados/operations/placement-groups.rst +++ b/doc/rados/operations/placement-groups.rst @@ -25,7 +25,7 @@ calculated automatically. Here are a few values commonly used: - For calculating ``pg_num`` value by yourself please take help of `pgcalc`_ tool -As the number of OSDs increases, chosing the right value for pg_num +As the number of OSDs increases, choosing the right value for pg_num becomes more important because it has a significant influence on the behavior of the cluster as well as the durability of the data when something goes wrong (i.e. the probability that a catastrophic event