Fix the duplicated words issue like "the the "

Code Issues Proposed changes

This is to fix the duplicated words issue, like:
 * "both of which which must be stripped off"
 * "In addition the the values set"
 and so on
Change-Id: Id3d84281f15815b4185c76874575e91a3589981b

This commit is contained in:

zhufl

2020年01月06日 10:34:42 +08:00

parent 7862ec7b8a

commit 47eb78897d

9 changed files with 10 additions and 10 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2
doc/manpages/account-server.conf.5

View File

@@ -394,7 +394,7 @@ reclaim_age. This ensures that once the account-reaper has deleted a

container there is sufficient time for the container-updater to report to the

account before the account DB is removed.

.IP \fBreap_warn_after\fR

If the account fails to be be reaped due to a persistent error, the

If the account fails to be reaped due to a persistent error, the

account reaper will log a message such as:

Account <name> has not been reaped since <date>

You can search logs for this message if space is not being reclaimed

2
doc/source/cors.rst

View File

@@ -28,7 +28,7 @@ The supported headers are,

| | Space separated. |

+------------------------------------------------+------------------------------+

In addition the the values set in container metadata, some cluster-wide values

In addition the values set in container metadata, some cluster-wide values

may also be configured using the ``strict_cors_mode``, ``cors_allow_origin``

and ``cors_expose_headers`` in ``proxy-server.conf``. See

``proxy-server.conf-sample`` for more information.

2
doc/source/deployment_guide.rst

View File

@@ -1748,7 +1748,7 @@ delay_reaping 0 Normally, the reaper begins deleting

time for the container-updater to report

to the account before the account DB is

removed.

reap_warn_after 2892000 If the account fails to be be reaped due

reap_warn_after 2892000 If the account fails to be reaped due

to a persistent error, the account reaper

will log a message such as:

Account <name> has not been reaped since <date>

2
doc/source/overview_container_sharding.rst

View File

@@ -404,7 +404,7 @@ In summary, the DB states that any container replica may be in are:

more shard ranges in addition to its own shard range. The retiring database

has been unlinked.

- COLLAPSED - There is only one database, the fresh database, which has only

its its own shard range and store object records.

its own shard range and store object records.

.. note::