From: wangxinyu Date: Thu, 2 Sep 2021 05:08:21 +0000 (+0800) Subject: doc: fix typos X-Git-Tag: v17.1.0~938^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=a59059b87f845bcd714f764c590b3f5742a4f5d6;p=ceph.git doc: fix typos Signed-off-by: wangxinyu --- diff --git a/doc/cephfs/dynamic-metadata-management.rst b/doc/cephfs/dynamic-metadata-management.rst index 5ef8d3ee7b1..4408be7bfbf 100644 --- a/doc/cephfs/dynamic-metadata-management.rst +++ b/doc/cephfs/dynamic-metadata-management.rst @@ -86,5 +86,5 @@ stray expiration notices, the exporter unfreezes the subtree, cleans up its migration-related state, and sends a final MExportFinish to the importer. Upon receipt, the importer logs an EImportFinish(true) (noting locally that the export was indeed a success), unfreezes its -subtree, processes any queued cache expierations, and cleans up its +subtree, processes any queued cache expirations, and cleans up its state. diff --git a/doc/rados/operations/crush-map.rst b/doc/rados/operations/crush-map.rst index 68c12d1d5f7..5a51cd2ccab 100644 --- a/doc/rados/operations/crush-map.rst +++ b/doc/rados/operations/crush-map.rst @@ -714,7 +714,7 @@ The ``bobtail`` tunable profile fixes a few key misbehaviors: * For large clusters, some small percentages of PGs map to fewer than the desired number of OSDs. This is more prevalent when there are - mutiple hierarchy layers in use (e.g., ``row``, ``rack``, ``host``, ``osd``). + multiple hierarchy layers in use (e.g., ``row``, ``rack``, ``host``, ``osd``). * When some OSDs are marked out, the data tends to get redistributed to nearby OSDs instead of across the entire hierarchy. diff --git a/doc/rados/operations/health-checks.rst b/doc/rados/operations/health-checks.rst index 5b8f759b113..08c05b55363 100644 --- a/doc/rados/operations/health-checks.rst +++ b/doc/rados/operations/health-checks.rst @@ -47,7 +47,7 @@ their initial connection to the cluster as they may need to try more addresses before they reach an operating monitor. The down monitor daemon should generally be restarted as soon as -possible to reduce the risk of a subsequen monitor failure leading to +possible to reduce the risk of a subsequent monitor failure leading to a service outage. MON_CLOCK_SKEW @@ -759,7 +759,7 @@ Detailed information about which PGs are affected is available from:: ceph health detail In most cases the root cause is that one or more OSDs is currently -down; see the dicussion for ``OSD_DOWN`` above. +down; see the discussion for ``OSD_DOWN`` above. The state of specific problematic PGs can be queried with:: diff --git a/src/doc/caching.txt b/src/doc/caching.txt index f623824cb73..1713ca46079 100644 --- a/src/doc/caching.txt +++ b/src/doc/caching.txt @@ -292,7 +292,7 @@ stray expiration notices, the exporter unfreezes the subtree, cleans up its migration-related state, and sends a final MExportFinish to the importer. Upon receipt, the importer logs an EImportFinish(true) (noting locally that the export was indeed a success), unfreezes its -subtree, processes any queued cache expierations, and cleans up its +subtree, processes any queued cache expirations, and cleans up its state.