Fix the duplicated words issue like "the the "

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

View File

@ -42,8 +42,8 @@ don't work - or at least fail in frequently common enough scenarios to
be considered "horribly broken". A comment in our review that says
roughly "I ran this on my machine and observed ``description of
behavior change is supposed to achieve``" is the most powerful defense
we have against the terrible terrible scorn from our fellow Swift
developers and operators when we accidentally merge bad code.
we have against the terrible scorn from our fellow Swift developers
and operators when we accidentally merge bad code.
If you're doing a fair amount of reviews - you will participate in
merging a change that will break my clusters - it's cool - I'll do it

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

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.

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>

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::

View File

@ -428,7 +428,7 @@ class Replicator(Daemon):
Make an http_connection using ReplConnection
:param node: node dictionary from the ring
:param partition: partition partition to send in the url
:param partition: partition to send in the url
:param db_file: DB file
:returns: ReplConnection object

View File

@ -1988,7 +1988,7 @@ class ContainerBroker(DatabaseBroker):
def set_sharding_sysmeta(self, key, value):
"""
Updates the broker's metadata metadata stored under the given key
Updates the broker's metadata stored under the given key
prefixed with a sharding specific namespace.
:param key: metadata key in the sharding metadata namespace.

View File

@ -3317,7 +3317,7 @@ class ECDiskFileManager(BaseDiskFileManager):
"""
Returns timestamp(s) and other info extracted from a policy specific
file name. For EC policy the data file name includes a fragment index
and possibly a durable marker, both of which which must be stripped off
and possibly a durable marker, both of which must be stripped off
to retrieve the timestamp.
:param filename: the file name including extension

View File

@ -688,7 +688,7 @@ class ObjectReconstructor(Daemon):
handoffs.
To avoid conflicts placing frags we'll skip through the handoffs and
only yield back those that are offset equal to to the given primary
only yield back those that are offset equal to the given primary
node index.
Nodes returned from this iterator will have 'backend_index' set.