From: 李丙洋 10208981 Date: Thu, 20 Sep 2018 02:07:25 +0000 (+0800) Subject: doc: fix typos in doc/releases X-Git-Tag: v14.0.1~38^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=c4d0114a8a60b283a87186fec4403937e6332495;p=ceph.git doc: fix typos in doc/releases Signed-off-by: Li Bingyang --- diff --git a/doc/releases/cuttlefish.rst b/doc/releases/cuttlefish.rst index a9e28c983356..7204efefbce8 100644 --- a/doc/releases/cuttlefish.rst +++ b/doc/releases/cuttlefish.rst @@ -103,7 +103,7 @@ v0.61.5 "Cuttlefish" ==================== This release most improves stability of the monitor and fixes a few -bugs with the ceph-disk utility (used by ceph-deploy). We recommand +bugs with the ceph-disk utility (used by ceph-deploy). We recommend that all v0.61.x users upgrade. Upgrading @@ -337,7 +337,7 @@ Please see `Upgrading from Bobtail to Cuttlefish`_ for details. * radosgw-admin now uses the term zone instead of cluster to describe each instance of the radosgw data store (and corresponding collection of radosgw daemons). The usage for the radosgw-admin - command and the 'rgw zone root pool' config optoins have changed + command and the 'rgw zone root pool' config options have changed accordingly. * rbd progress indicators now go to standard error instead of standard @@ -354,7 +354,7 @@ Please see `Upgrading from Bobtail to Cuttlefish`_ for details. * The sysvinit script now uses the ceph.conf file on the remote host when starting remote daemons via the '-a' option. Note that if '-a' - is used in conjuction with '-c path', the path must also be present + is used in conjunction with '-c path', the path must also be present on the remote host (it is not copied to a temporary file, as it was previously). @@ -382,7 +382,7 @@ Please see `Upgrading from Bobtail to Cuttlefish`_ for details. * The 'ceph osd pool delete ' and 'rados rmpool ' now have safety interlocks with loud warnings that make you confirm - pool removal. Any scripts curenty rely on these functions zapping + pool removal. Any scripts currently rely on these functions zapping data without confirmation need to be adjusted accordingly. @@ -685,7 +685,7 @@ Upgrading * The 'ceph osd pool delete ' and 'rados rmpool ' now have safety interlocks with loud warnings that make you confirm - pool removal. Any scripts curenty rely on these functions zapping + pool removal. Any scripts currently rely on these functions zapping data without confirmation need to be adjusted accordingly. Notable Changes diff --git a/doc/releases/dumpling.rst b/doc/releases/dumpling.rst index f5cfc08dbcbc..32febd677810 100644 --- a/doc/releases/dumpling.rst +++ b/doc/releases/dumpling.rst @@ -404,7 +404,7 @@ For more detailed information, see :download:`the complete changelog <../changel v0.67.2 "Dumpling" ================== -This is an imporant point release for Dumpling. Most notably, it +This is an important point release for Dumpling. Most notably, it fixes a problem when upgrading directly from v0.56.x Bobtail to v0.67.x Dumpling (without stopping at v0.61.x Cuttlefish along the way). It also fixes a problem with the CLI parsing of the CEPH_ARGS @@ -543,7 +543,7 @@ Upgrading from v0.66 * ceph-osd now requires a max file descriptor limit (e.g., ``ulimit -n ...``) of at least filestore_wbthrottle_(xfs|btrfs)_inodes_hard_limit (5000 by default) - in order to accomodate the new write back throttle system. On + in order to accommodate the new write back throttle system. On Ubuntu, upstart now sets the fd limit to 32k. On other platforms, the sysvinit script will set it to 32k by default (still overrideable via max_open_files). If this field has been customized @@ -860,7 +860,7 @@ Upgrading introduced in v0.59 and Linux kernel version v3.9. If you wish to access the cluster from an older kernel, set the 'osd pool default flag hashpspool = false' option in your ceph.conf prior to creating - the cluster or creating new pools. Note that the presense of any + the cluster or creating new pools. Note that the presence of any pool in the cluster with the flag enabled will make the OSD require support from all clients. diff --git a/doc/releases/emperor.rst b/doc/releases/emperor.rst index ee5c19d6e6af..20823f51f801 100644 --- a/doc/releases/emperor.rst +++ b/doc/releases/emperor.rst @@ -22,7 +22,7 @@ v0.72.2 Emperor This is the second bugfix release for the v0.72.x Emperor series. We have fixed a hang in radosgw, and fixed (again) a problem with monitor -CLI compatiblity with mixed version monitors. (In the future this +CLI compatibility with mixed version monitors. (In the future this will no longer be a problem.) Upgrading diff --git a/doc/releases/firefly.rst b/doc/releases/firefly.rst index c6977197ec9c..5847bd1b9e52 100644 --- a/doc/releases/firefly.rst +++ b/doc/releases/firefly.rst @@ -274,7 +274,7 @@ v0.80.8 Firefly =============== This is a long-awaited bugfix release for firefly. It has several -imporant (but relatively rare) OSD peering fixes, performance issues +important (but relatively rare) OSD peering fixes, performance issues when snapshots are trimmed, several RGW fixes, a paxos corner case fix, and some packaging updates. @@ -525,7 +525,7 @@ This is the third Firefly point release. It includes a single fix for a radosgw regression that was discovered in v0.80.2 right after it was released. -We recommand that all v0.80.x Firefly users upgrade. +We recommend that all v0.80.x Firefly users upgrade. Notable Changes --------------- @@ -667,7 +667,7 @@ Upgrade Sequencing upgrading to v0.80 Firefly. Please refer to the :ref:`dumpling-upgrade` documentation. -* We recommand adding the following to the [mon] section of your +* We recommend adding the following to the [mon] section of your ceph.conf prior to upgrade:: mon warn on legacy crush tunables = false diff --git a/doc/releases/giant.rst b/doc/releases/giant.rst index 000b624fbd61..d6ee8c097d83 100644 --- a/doc/releases/giant.rst +++ b/doc/releases/giant.rst @@ -161,7 +161,7 @@ v0.87.x. Highlights for Giant include: performance of single-MDS systems is vastly improved in Giant. Although we do not yet recommend CephFS for production deployments, we do encourage testing for non-critical workloads so that we can - better guage the feature, usability, performance, and stability + better gauge the feature, usability, performance, and stability gaps. * *Local Recovery Codes*: the OSDs now support an erasure-coding scheme that stores some additional data blocks to reduce the IO required to @@ -705,7 +705,7 @@ Major items include: * LTTNG tracing framework, with initial tracepoints in librados, librbd, and the OSD FileStore backend * separate monitor audit log for all administrative commands -* asynchronos monitor transaction commits to reduce the impact on +* asynchronous monitor transaction commits to reduce the impact on monitor read requests while processing updates * low-level tool for working with individual OSD data stores for debugging, recovery, and testing diff --git a/doc/releases/hammer.rst b/doc/releases/hammer.rst index 3700730164fe..06dd17c9bf64 100644 --- a/doc/releases/hammer.rst +++ b/doc/releases/hammer.rst @@ -711,7 +711,7 @@ Highlights since Giant include: vastly improved in Giant, and more improvements have been made now in Hammer. Although we still recommend caution when storing important data in CephFS, we do encourage testing for non-critical - workloads so that we can better guage the feature, usability, + workloads so that we can better gauge the feature, usability, performance, and stability gaps. * *CRUSH improvements*: We have added a new straw2 bucket algorithm that reduces the amount of data migration required when changes are @@ -737,7 +737,7 @@ Other highlights since Firefly include: performance of single-MDS systems is vastly improved in Giant. Although we do not yet recommend CephFS for production deployments, we do encourage testing for non-critical workloads so that we can - better guage the feature, usability, performance, and stability + better gauge the feature, usability, performance, and stability gaps. * *Local Recovery Codes*: the OSDs now support an erasure-coding scheme that stores some additional data blocks to reduce the IO required to @@ -843,7 +843,7 @@ Upgrading from v0.87.x Giant that it is untested and may destroy data, you need to add the following to your ceph.conf:: - enable experimental unrecoverable data corrupting featuers = keyvaluestore + enable experimental unrecoverable data corrupting features = keyvaluestore * The following librados C API function calls take a 'flags' argument whose value is now correctly interpreted: @@ -869,7 +869,7 @@ Upgrading from v0.87.x Giant to track PG stat summations over different categories of objects for use by radosgw. It is no longer has any known users and is prone to abuse because it can lead to a pg_stat_t structure that is unbounded. The librados API calls - that accept this field now ignore it, and the OSD no longers tracks the + that accept this field now ignore it, and the OSD no longer tracks the per-category summations. * The output for 'rados df' has changed. The 'category' level has been @@ -1823,7 +1823,7 @@ Upgrading that it is untested and may destroy data, you need to add the following to your ceph.conf:: - enable experimental unrecoverable data corrupting featuers = keyvaluestore + enable experimental unrecoverable data corrupting features = keyvaluestore * The following librados C API function calls take a 'flags' argument whose value is now correctly interpreted: @@ -1945,7 +1945,7 @@ Upgrading to track PG stat summations over different categories of objects for use by radosgw. It is no longer has any known users and is prone to abuse because it can lead to a pg_stat_t structure that is unbounded. The librados API calls - that accept this field now ignore it, and the OSD no longers tracks the + that accept this field now ignore it, and the OSD no longer tracks the per-category summations. * The output for 'rados df' has changed. The 'category' level has been diff --git a/doc/releases/infernalis.rst b/doc/releases/infernalis.rst index 5990f903c5ff..14b756c0aff4 100644 --- a/doc/releases/infernalis.rst +++ b/doc/releases/infernalis.rst @@ -102,7 +102,7 @@ Major Changes from Hammer * There have been many improvements to low-level repair tooling (ceph-objectstore-tool). * The internal ObjectStore API has been significantly cleaned up in order - to faciliate new storage backends like NewStore. + to facilitate new storage backends like NewStore. - *RGW*: @@ -805,7 +805,7 @@ Major Changes from Hammer * There have been many improvements to low-level repair tooling (ceph-objectstore-tool). * The internal ObjectStore API has been significantly cleaned up in order - to faciliate new storage backends like NewStore. + to facilitate new storage backends like NewStore. - *RGW*: diff --git a/doc/releases/jewel.rst b/doc/releases/jewel.rst index 8cbcbb441f91..6bd0d8c37c74 100644 --- a/doc/releases/jewel.rst +++ b/doc/releases/jewel.rst @@ -1314,7 +1314,7 @@ Major Changes from Hammer * There have been many improvements to low-level repair tooling (ceph-objectstore-tool). * The internal ObjectStore API has been significantly cleaned up in order - to faciliate new storage backends like BlueStore. + to facilitate new storage backends like BlueStore. - *RGW*: diff --git a/doc/releases/kraken.rst b/doc/releases/kraken.rst index 6ec08fc96859..3e6774e7ab65 100644 --- a/doc/releases/kraken.rst +++ b/doc/releases/kraken.rst @@ -37,7 +37,7 @@ Notable Changes * This release greatly improves control and throttling of the snap trimmer. It introduces the "osd max trimming pgs" option (defaulting to 2), which limits how many PGs on an OSD can be trimming snapshots at a time. And it restores - the safe use of the "osd snap trim sleep" option, wihch defaults to 0 but + the safe use of the "osd snap trim sleep" option, which defaults to 0 but otherwise adds the given number of seconds in delay between every dispatch of trim operations to the underlying system. @@ -459,7 +459,7 @@ Upgrade notes * The 'rgw rest getusage op compat' config option allows you to dump (or not dump) the description of user stats in the S3 GetUsage API. This option defaults to false. If the value is true, the - reponse data for GetUsage looks like:: + response data for GetUsage looks like:: "stats": { "TotalBytes": 516, @@ -467,7 +467,7 @@ Upgrade notes "TotalEntries": 1 } - If the value is false, the reponse for GetUsage looks as it did before:: + If the value is false, the response for GetUsage looks as it did before:: { 516, diff --git a/doc/releases/luminous.rst b/doc/releases/luminous.rst index 992bc8676198..f14fe09eeaa9 100644 --- a/doc/releases/luminous.rst +++ b/doc/releases/luminous.rst @@ -40,7 +40,7 @@ Notable Changes mitigate data sync getting blocked during network issues * Option `rgw s3 auth order` configurable added which takes a comma - seperated list of order to try for s3 authentication when external + separated list of order to try for s3 authentication when external engines are involved. Changelog @@ -426,7 +426,7 @@ v12.2.5 Luminous This is the fifth bugfix release of Luminous v12.2.x long term stable release series. This release contains a range of bug fixes across all -compoenents of Ceph. We recommend all the users of 12.2.x series to +components of Ceph. We recommend all the users of 12.2.x series to update. Notable Changes @@ -1513,7 +1513,7 @@ Upgrade from Jewel or Kraken # ceph osd set sortbitwise #. Make sure your cluster is stable and healthy (no down or - recoverying OSDs). (Optional, but recommended.) + recovering OSDs). (Optional, but recommended.) #. Do not create any new erasure-code pools while upgrading the monitors. @@ -1651,7 +1651,7 @@ upgrades from Jewel to Luminous. * The 'rgw rest getusage op compat' config option allows you to dump (or not dump) the description of user stats in the S3 GetUsage API. This option defaults to false. If the value is true, the - reponse data for GetUsage looks like:: + response data for GetUsage looks like:: "stats": { "TotalBytes": 516, @@ -1659,7 +1659,7 @@ upgrades from Jewel to Luminous. "TotalEntries": 1 } - If the value is false, the reponse for GetUsage looks as it did before:: + If the value is false, the response for GetUsage looks as it did before:: { 516,