You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by zw...@apache.org on 2020/05/11 13:54:15 UTC
[trafficserver] branch 9.0.x updated: Cleans up doubled words in
documentation
This is an automated email from the ASF dual-hosted git repository.
zwoop pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git
The following commit(s) were added to refs/heads/9.0.x by this push:
new ff896de Cleans up doubled words in documentation
ff896de is described below
commit ff896de98333cc25283923aeccaf5961f829bbbc
Author: Randall Meyer <rr...@apache.org>
AuthorDate: Wed May 6 08:33:12 2020 -0700
Cleans up doubled words in documentation
(cherry picked from commit da238c09fb6fffe8609526945e1538c44904b83c)
---
doc/Doxyfile | 2 +-
doc/admin-guide/configuration/transparent-proxy/build.en.rst | 2 +-
doc/admin-guide/files/cache.config.en.rst | 2 +-
doc/admin-guide/files/records.config.en.rst | 2 +-
doc/admin-guide/logging/formatting.en.rst | 2 +-
doc/admin-guide/plugins/access_control.en.rst | 2 +-
doc/admin-guide/plugins/cachekey.en.rst | 6 +++---
doc/admin-guide/plugins/esi.en.rst | 4 ++--
doc/admin-guide/plugins/geoip_acl.en.rst | 2 +-
doc/admin-guide/plugins/header_rewrite.en.rst | 2 +-
doc/admin-guide/plugins/lua.en.rst | 2 +-
doc/admin-guide/plugins/prefetch.en.rst | 4 ++--
doc/admin-guide/plugins/slice.en.rst | 2 +-
doc/admin-guide/storage/index.en.rst | 4 ++--
doc/appendices/glossary.en.rst | 2 +-
doc/developer-guide/api/functions/TSHttpTxnMilestoneGet.en.rst | 2 +-
doc/developer-guide/api/functions/TSIOBufferReader.en.rst | 2 +-
doc/developer-guide/api/functions/TSRemap.en.rst | 2 +-
doc/developer-guide/api/functions/TSTypes.en.rst | 2 +-
doc/developer-guide/cache-architecture/architecture.en.rst | 2 +-
doc/developer-guide/cache-architecture/data-structures.en.rst | 2 +-
doc/developer-guide/client-session-architecture.en.rst | 2 +-
doc/developer-guide/core-architecture/heap.en.rst | 2 +-
doc/developer-guide/internal-libraries/TextView.en.rst | 4 ++--
doc/developer-guide/internal-libraries/scalar.en.rst | 4 ++--
doc/developer-guide/plugins/remap-plugins.en.rst | 2 +-
doc/uml/Makefile.am | 2 +-
27 files changed, 34 insertions(+), 34 deletions(-)
diff --git a/doc/Doxyfile b/doc/Doxyfile
index 39aca55..083f1d0 100644
--- a/doc/Doxyfile
+++ b/doc/Doxyfile
@@ -646,7 +646,7 @@ SHOW_NAMESPACES = YES
# The FILE_VERSION_FILTER tag can be used to specify a program or script that
# doxygen should invoke to get the current version for each file (typically from
# the version control system). Doxygen will invoke the program by executing (via
-# popen()) the command command input-file, where command is the value of the
+# popen()) the command input-file, where command is the value of the
# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
# by doxygen. Whatever the program writes to standard output is used as the file
# version. For an example see the documentation.
diff --git a/doc/admin-guide/configuration/transparent-proxy/build.en.rst b/doc/admin-guide/configuration/transparent-proxy/build.en.rst
index 10337a3..0f9dbf2 100644
--- a/doc/admin-guide/configuration/transparent-proxy/build.en.rst
+++ b/doc/admin-guide/configuration/transparent-proxy/build.en.rst
@@ -37,7 +37,7 @@ may need to twiddle the ``configure`` options.
Enable TPROXY support, which is the Linux kernel feature used for
transparency. This should be present in the base installation, there
is no package associated with it. \* ``auto`` Do automatic checks
- for the the TPROXY header file (``linux/in.h``) and enable TPROXY
+ for the TPROXY header file (``linux/in.h``) and enable TPROXY
support if the ``IP_TRANSPARENT`` definition is present. This is the
default if this option is not specified or ``value`` is omitted. \*
``no`` Do not check for TPROXY support, disable support for it. \*
diff --git a/doc/admin-guide/files/cache.config.en.rst b/doc/admin-guide/files/cache.config.en.rst
index 4662992..c75fcaf 100644
--- a/doc/admin-guide/files/cache.config.en.rst
+++ b/doc/admin-guide/files/cache.config.en.rst
@@ -198,7 +198,7 @@ specifiers of the rule in question.
.. _cache-config-format-revalidate:
``revalidate``
- For objects that are in cache, overrides the the amount of time the object(s)
+ For objects that are in cache, overrides the amount of time the object(s)
are to be considered fresh. Use the same time formats as ``pin-in-cache``.
.. _cache-config-format-ttl-in-cache:
diff --git a/doc/admin-guide/files/records.config.en.rst b/doc/admin-guide/files/records.config.en.rst
index 85c5d89..edb8344 100644
--- a/doc/admin-guide/files/records.config.en.rst
+++ b/doc/admin-guide/files/records.config.en.rst
@@ -336,7 +336,7 @@ Thread Variables
.. ts:cv:: CONFIG proxy.config.system.file_max_pct FLOAT 0.9
- Set the maximum number of file handles for the traffic_server process as a percentage of the the fs.file-max proc value in Linux. The default is 90%.
+ Set the maximum number of file handles for the traffic_server process as a percentage of the fs.file-max proc value in Linux. The default is 90%.
.. ts:cv:: CONFIG proxy.config.crash_log_helper STRING traffic_crashlog
diff --git a/doc/admin-guide/logging/formatting.en.rst b/doc/admin-guide/logging/formatting.en.rst
index 242afe2..5b98f0b 100644
--- a/doc/admin-guide/logging/formatting.en.rst
+++ b/doc/admin-guide/logging/formatting.en.rst
@@ -341,7 +341,7 @@ cssh ecssh
============== ===================
It is also possible to log all of the headers in a transaction message with a
-single field. For each original original field, there is a variant which ends in
+single field. For each original field, there is a variant which ends in
``ah`` rather than ``h``, as shown here:
============== ===================
diff --git a/doc/admin-guide/plugins/access_control.en.rst b/doc/admin-guide/plugins/access_control.en.rst
index 2aefafb..6a001c6 100644
--- a/doc/admin-guide/plugins/access_control.en.rst
+++ b/doc/admin-guide/plugins/access_control.en.rst
@@ -237,7 +237,7 @@ Query-Param-Style Named Claim format
* ``iat`` for `issued at time`_, `optional`
* ``tid`` for `token id`_, `optional`
* ``ver`` for `version`_, `optional`, defaults to ``ver=1`` if not specified.
- * ``scope`` for `scope`_, `optional`, ignored by by the current version of the plugin, still not finalized (more applications and their use cases need to be studied to finalize the format)
+ * ``scope`` for `scope`_, `optional`, ignored by the current version of the plugin, still not finalized (more applications and their use cases need to be studied to finalize the format)
* ``kid`` for `key id`_, `required` (tokens to be always signed)
* ``st`` for `signature type`_, `optional` (default would be ``SHA-256`` if not specified)
* ``md`` for `message digest`_ - this claim is `required` and expected to be always the last claim.
diff --git a/doc/admin-guide/plugins/cachekey.en.rst b/doc/admin-guide/plugins/cachekey.en.rst
index 3945a43..9abf9ed 100644
--- a/doc/admin-guide/plugins/cachekey.en.rst
+++ b/doc/admin-guide/plugins/cachekey.en.rst
@@ -482,7 +482,7 @@ and if the request URI is the following ::
http://test_prefix_123.example.com/path/to/object?a=1&b=2&c=3
-the the `cache key` will be prefixed with ``/test_prefix_object`` instead of ``test_prefix_123.example.com:80`` when ``--capture-prefix-uri`` is not used.
+the `cache key` will be prefixed with ``/test_prefix_object`` instead of ``test_prefix_123.example.com:80`` when ``--capture-prefix-uri`` is not used.
Combining prefix plugin parameters, i.e. --static-prefix and --capture-prefix
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
@@ -525,7 +525,7 @@ and the request URI is the following ::
http://test_path_123.example.com/path/to/object?a=1&b=2&c=3
-the the `cache key` will have ``/test_path_object`` in the path section of the `cache key` instead of ``/path/to/object`` when either ``--capture-path`` nor ``--capture-path-uri`` are used.
+the `cache key` will have ``/test_path_object`` in the path section of the `cache key` instead of ``/path/to/object`` when either ``--capture-path`` nor ``--capture-path-uri`` are used.
Combining path plugin parameters --capture-path and --capture-path-uri
@@ -541,7 +541,7 @@ and the request URI is the following ::
http://test_path_123.example.com/path/to/object?a=1&b=2&c=3
-the the `cache key` will have ``/test_path_object/const_path_object`` in the path section of the `cache key` instead of ``/path/to/object`` when either ``--capture-path`` nor ``--capture-path-uri`` are used.
+the `cache key` will have ``/test_path_object/const_path_object`` in the path section of the `cache key` instead of ``/path/to/object`` when either ``--capture-path`` nor ``--capture-path-uri`` are used.
User-Agent capturing, replacement and classification
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
diff --git a/doc/admin-guide/plugins/esi.en.rst b/doc/admin-guide/plugins/esi.en.rst
index 0a8b521..4ea0a77 100644
--- a/doc/admin-guide/plugins/esi.en.rst
+++ b/doc/admin-guide/plugins/esi.en.rst
@@ -152,8 +152,8 @@ Useful Note
1. You can provide proper cache control header and the ESI response and ESI include response can be cached separately.
It is extremely useful for rendering page with multiple modules. The page layout can be a ESI response with multiple
- ESI include include, each for different module. The page layout ESI response can be cached and each individual ESI
- include can also be cached with different duration.
+ ESI includes, each for a different module. The page layout ESI response can be cached and each individual ESI
+ included can also be cached with a different duration.
2. You should run the plugin without using "packed node support" because it is not fully tested.
diff --git a/doc/admin-guide/plugins/geoip_acl.en.rst b/doc/admin-guide/plugins/geoip_acl.en.rst
index 13d3368..9444163 100644
--- a/doc/admin-guide/plugins/geoip_acl.en.rst
+++ b/doc/admin-guide/plugins/geoip_acl.en.rst
@@ -22,7 +22,7 @@ GeoIP ACLs Plugin
This is a simple ATS plugin for denying (or allowing) requests based on
the source IP geo-location. Currently only the Maxmind APIs are
-supported, but we'd be happy to other other (open) APIs if you let us
+supported, but we'd be happy to other (open) APIs if you let us
know. This plugin comes with the standard distribution of Apache Traffic
Server, and should be installed as part of the normal build process.
diff --git a/doc/admin-guide/plugins/header_rewrite.en.rst b/doc/admin-guide/plugins/header_rewrite.en.rst
index 93f134d..17980de 100644
--- a/doc/admin-guide/plugins/header_rewrite.en.rst
+++ b/doc/admin-guide/plugins/header_rewrite.en.rst
@@ -193,7 +193,7 @@ COOKIE
cond %{COOKIE:<name>} <operand>
-Value of of the cookie ``<name>``. This does not expose or match against a
+Value of the cookie ``<name>``. This does not expose or match against a
cookie's expiration, the domain(s) on which it is valid, whether it is protocol
restricted, or any of the other metadata; simply the current value of the
cookie as presented by the client.
diff --git a/doc/admin-guide/plugins/lua.en.rst b/doc/admin-guide/plugins/lua.en.rst
index a76cf44..c686b17 100644
--- a/doc/admin-guide/plugins/lua.en.rst
+++ b/doc/admin-guide/plugins/lua.en.rst
@@ -904,7 +904,7 @@ Here is an example:
ts.debug(url_port)
end
-Then Then ``GET /liuyurou.txt HTTP/1.1\r\nHost: 192.168.231.129:8080\r\n...`` will yield the output:
+Then ``GET /liuyurou.txt HTTP/1.1\r\nHost: 192.168.231.129:8080\r\n...`` will yield the output:
``8080``
diff --git a/doc/admin-guide/plugins/prefetch.en.rst b/doc/admin-guide/plugins/prefetch.en.rst
index b958392..7a30b64 100644
--- a/doc/admin-guide/plugins/prefetch.en.rst
+++ b/doc/admin-guide/plugins/prefetch.en.rst
@@ -153,7 +153,7 @@ If the "incoming" URL is ::
http://example.com/path/file-104.mov?a=a&b=b
-the the following URLs will be requested to be prefetched ::
+the following URLs will be requested to be prefetched ::
http://example-seed.com/path/file-106.mov?a=a&b=b
http://example-seed.com/path/file-108.mov?a=a&b=b
@@ -203,7 +203,7 @@ compromises:
requests which would result in using the same **cache key** are not considered as
separate requests (which could bloat/dilute the LRU cache
if not normalized)
-* **Check if the the fetch request is unique**. A ``simple`` prefetching policy is
+* **Check if the fetch request is unique**. A ``simple`` prefetching policy is
always used to make sure prefetches for the same object (same cache key) are
never triggered simultaneously.
* **Check if already cached**. Before triggering the prefetch request to the
diff --git a/doc/admin-guide/plugins/slice.en.rst b/doc/admin-guide/plugins/slice.en.rst
index b131178..f035e82 100644
--- a/doc/admin-guide/plugins/slice.en.rst
+++ b/doc/admin-guide/plugins/slice.en.rst
@@ -185,7 +185,7 @@ block header and sends its bytes to the client until the client
request is satisfied.
Any extra bytes at the end of the last block are consumed by
-the the Slice plugin to allow cache_range_requests to finish
+the Slice plugin to allow cache_range_requests to finish
the block fetch to ensure the block is cached.
Important Notes
diff --git a/doc/admin-guide/storage/index.en.rst b/doc/admin-guide/storage/index.en.rst
index 50e1e63..cdd3cc9 100644
--- a/doc/admin-guide/storage/index.en.rst
+++ b/doc/admin-guide/storage/index.en.rst
@@ -307,7 +307,7 @@ Pushing an Object into the Cache
================================
Traffic Server accepts the custom HTTP request method ``PUSH`` to put an object
-into the the cache. If the object is successfully written to the cache, then
+into the cache. If the object is successfully written to the cache, then
Traffic Server responds with a ``200 OK`` HTTP message; otherwise a
``400 Malformed Pushed Response Header`` message is returned.
@@ -357,7 +357,7 @@ To access the Cache Inspector utility:
map http://yourhost.com/myCI/ http://{cache} @action=allow @src_ip=172.28.56.1-172.28.56.254
#. Reload the Traffic Server configuration by running :option:`traffic_ctl config reload`.
-#. Open your web browser and go to the the following URL::
+#. Open your web browser and go to the following URL::
http://yourhost/myCI/
diff --git a/doc/appendices/glossary.en.rst b/doc/appendices/glossary.en.rst
index 02318ae..85dc499 100644
--- a/doc/appendices/glossary.en.rst
+++ b/doc/appendices/glossary.en.rst
@@ -26,7 +26,7 @@ Glossary
:sorted:
continuation
- A callable object that contains state. These are are mechanism used by
+ A callable object that contains state. This is a mechanism used by
|TS| to implement callbacks and continued computations. Continued
computations are critical to efficient processing of traffic because by
avoiding any blocking operations that wait on external events. In any
diff --git a/doc/developer-guide/api/functions/TSHttpTxnMilestoneGet.en.rst b/doc/developer-guide/api/functions/TSHttpTxnMilestoneGet.en.rst
index d7bf321..2cebf10 100644
--- a/doc/developer-guide/api/functions/TSHttpTxnMilestoneGet.en.rst
+++ b/doc/developer-guide/api/functions/TSHttpTxnMilestoneGet.en.rst
@@ -84,7 +84,7 @@ is successful.
.. macro:: TS_MILESTONE_SERVER_FIRST_CONNECT
- First time origin server connect attempted or shared shared session attached.
+ First time origin server connect attempted or shared session attached.
.. macro:: TS_MILESTONE_SERVER_CONNECT
diff --git a/doc/developer-guide/api/functions/TSIOBufferReader.en.rst b/doc/developer-guide/api/functions/TSIOBufferReader.en.rst
index e3b0f10..d06e8fb 100644
--- a/doc/developer-guide/api/functions/TSIOBufferReader.en.rst
+++ b/doc/developer-guide/api/functions/TSIOBufferReader.en.rst
@@ -69,7 +69,7 @@ time. Reader allocation is fast and cheap until this maximum is reached at which
This also effectively consumes (see :func:`TSIOBufferReaderConsume`) all data for :arg:`reader`.
:func:`TSIOBufferReaderConsume` consume data from :arg:`reader`.
- This advances the position of :arg:`reader` in its IO buffer by the the smaller of :arg:`nbytes`
+ This advances the position of :arg:`reader` in its IO buffer by the smaller of :arg:`nbytes`
and the maximum available in the buffer. This is required to release the buffer memory - when
data has been consumed by all readers, it is discarded.
diff --git a/doc/developer-guide/api/functions/TSRemap.en.rst b/doc/developer-guide/api/functions/TSRemap.en.rst
index c541f20..1d7e52a 100644
--- a/doc/developer-guide/api/functions/TSRemap.en.rst
+++ b/doc/developer-guide/api/functions/TSRemap.en.rst
@@ -72,7 +72,7 @@ the HTTP transaction.
to notify plugins of the coming configuration reload. It is called on all already loaded plugins,
invoked by current and all previous still used configurations. This is an optional entry point.
-:func:`TSRemapPostConfigReload` is called to indicate the end of the the new remap configuration
+:func:`TSRemapPostConfigReload` is called to indicate the end of the new remap configuration
load. It is called on the newly and previously loaded plugins, invoked by the new, current and
previous still used configurations. It also indicates whether the configuration reload was successful
by passing :macro:`TSREMAP_CONFIG_RELOAD_FAILURE` in case of failure and to notify the plugins if they
diff --git a/doc/developer-guide/api/functions/TSTypes.en.rst b/doc/developer-guide/api/functions/TSTypes.en.rst
index a63c5fb..ef90987 100644
--- a/doc/developer-guide/api/functions/TSTypes.en.rst
+++ b/doc/developer-guide/api/functions/TSTypes.en.rst
@@ -102,7 +102,7 @@ more widely. Those are described on this page.
.. type:: TSMBuffer
- Internally, data for a transaction is stored in one more more :term:`header heap`\s. These are
+ Internally, data for a transaction is stored in one or more :term:`header heap`\s. These are
storage local to the transaction, and generally each HTTP header is stored in a separate one.
This type is a handle to a header heap, and is provided or required by functions that locate HTTP
header related data.
diff --git a/doc/developer-guide/cache-architecture/architecture.en.rst b/doc/developer-guide/cache-architecture/architecture.en.rst
index 3abad2b..0f04102 100644
--- a/doc/developer-guide/cache-architecture/architecture.en.rst
+++ b/doc/developer-guide/cache-architecture/architecture.en.rst
@@ -990,7 +990,7 @@ evacuated.
There are two types of evacuations: *reader based* and *forced*. The
``EvacuationBlock`` has a reader count to track this. If the reader count is
-zero, then it is a forced evacuation and the the target, if it exists, will be
+zero, then it is a forced evacuation and the target, if it exists, will be
evacuated when the write cursor gets close. If the reader value is non-zero
then it is a count of entities that are currently expecting to be able to read
the object. Readers increment the count when they require read access to the
diff --git a/doc/developer-guide/cache-architecture/data-structures.en.rst b/doc/developer-guide/cache-architecture/data-structures.en.rst
index 3974eb7..d360c1d 100644
--- a/doc/developer-guide/cache-architecture/data-structures.en.rst
+++ b/doc/developer-guide/cache-architecture/data-structures.en.rst
@@ -160,7 +160,7 @@ Data Structures
.. member:: DLL<EvacuationBlock> evacuate
- Array of of :class:`EvacuationBlock` buckets. This is sized so there
+ Array of :class:`EvacuationBlock` buckets. This is sized so there
is one bucket for every evacuation span.
.. member:: off_t len
diff --git a/doc/developer-guide/client-session-architecture.en.rst b/doc/developer-guide/client-session-architecture.en.rst
index 65696df..22e0c0f 100644
--- a/doc/developer-guide/client-session-architecture.en.rst
+++ b/doc/developer-guide/client-session-architecture.en.rst
@@ -93,7 +93,7 @@ HTTP/2 Objects
This diagram shows the relationships between objects created as part of a HTTP/2 session. It is very similar
to the HTTP/1.x case. The Http2ClientSession object interacts with the NetVC. The Http2Stream object creates
-a HttpSM object object when :code:`ProxyClient::new_transaction()` is called.
+a HttpSM object when :code:`ProxyClient::new_transaction()` is called.
One difference is that the Http/2 protocol allows for multiple simultaneous transactions, so the Http2ClientSession
object must be able to manage multiple streams. From the HttpSM perspective it is interacting with a
diff --git a/doc/developer-guide/core-architecture/heap.en.rst b/doc/developer-guide/core-architecture/heap.en.rst
index 31bee10..2f0140a 100644
--- a/doc/developer-guide/core-architecture/heap.en.rst
+++ b/doc/developer-guide/core-architecture/heap.en.rst
@@ -150,7 +150,7 @@ Implementation
String Coalescence
------------------
-String heaps do do not maintain lists of internal free space. Strings that are released are left in
+String heaps do not maintain lists of internal free space. Strings that are released are left in
place, creating dead space in the heap. For this reason it can become necessary to do a garbage
collection operation on the writeable string heap in the header heap by calling
:func:`HdrHeap::coalesce_str_heaps`. This is done when
diff --git a/doc/developer-guide/internal-libraries/TextView.en.rst b/doc/developer-guide/internal-libraries/TextView.en.rst
index f3dc72e..0951ef6 100644
--- a/doc/developer-guide/internal-libraries/TextView.en.rst
+++ b/doc/developer-guide/internal-libraries/TextView.en.rst
@@ -151,8 +151,8 @@ History
The first attempt at this functionality was in the TSConfig library in the :code:`ts::Buffer` and
:code:`ts::ConstBuffer` classes. Originally intended just as raw memory views,
:code:`ts::ConstBuffer` in particular was repeated enhanced to provide better support for strings.
-The header was eventually moved from :literal:`lib/tsconfig` to :literal:`lib/ts` and was used in in
-various part of the |TS| core.
+The header was eventually moved from :literal:`lib/tsconfig` to :literal:`lib/ts` and was used in
+various parts of the |TS| core.
There was then a proposal to make these classes available to plugin writers as they proved handy in
the core. A suggested alternative was `Boost.StringRef
diff --git a/doc/developer-guide/internal-libraries/scalar.en.rst b/doc/developer-guide/internal-libraries/scalar.en.rst
index f1f4cca..185fe06 100644
--- a/doc/developer-guide/internal-libraries/scalar.en.rst
+++ b/doc/developer-guide/internal-libraries/scalar.en.rst
@@ -255,10 +255,10 @@ the library user. The increment / decrement and compound assignment operators we
similar to pointer arithmetic to be unsurprising in this context. This was further influenced by the
fact that, in general, these operators are useless in the value context. E.g. if a scalar has a
scale greater than 1 (the common case) then increment and decrement of the value is always a null
-operation. Once those operators are used on the count is is least surprising that the compound
+operation. Once those operators are used on the count is least surprising that the compound
operators act in the same way. The next step, to arithmetic operators, is not so clear and so those
require explicit scale indicators, such as :code:`round_down` or explicit constructors. It was a
design goal to avoid, as much as possible, the requirement that the library user keep track of the
scale of specific variables. This has proved very useful in practice, but at the same time when
-doing arithmetic is is almost always the case that either the values are both scalars (making the
+doing arithmetic is almost always the case that either the values are both scalars (making the
arithmetic unambiguous) or the scale of the literal is known (e.g., "add 6 kilobytes").
diff --git a/doc/developer-guide/plugins/remap-plugins.en.rst b/doc/developer-guide/plugins/remap-plugins.en.rst
index bd4addf..2bab288 100644
--- a/doc/developer-guide/plugins/remap-plugins.en.rst
+++ b/doc/developer-guide/plugins/remap-plugins.en.rst
@@ -114,7 +114,7 @@ the reload attempt, regardless of whether a plugin is part of the new configurat
to notify plugins of the coming configuration reload. It is called on all already loaded plugins,
invoked by current and all previous still used configurations. This is an optional entry point.
-:func:`TSRemapPostConfigReload` is called to indicate the end of the the new remap configuration
+:func:`TSRemapPostConfigReload` is called to indicate the end of the new remap configuration
load. It is called on the newly and previously loaded plugins, invoked by the new, current and
previous still used configurations. It also indicates whether the configuration reload was successful
by passing :macro:`TSREMAP_CONFIG_RELOAD_FAILURE` in case of failure and to notify the plugins if they
diff --git a/doc/uml/Makefile.am b/doc/uml/Makefile.am
index 2a9fa76..050d91e 100644
--- a/doc/uml/Makefile.am
+++ b/doc/uml/Makefile.am
@@ -24,7 +24,7 @@ PLANTUML_JAR := $(shell ../ext/plantuml_fetch.sh | tail -1)
all-am: jar-check $(images)
endif
-# These are handle when the make target comes from the the base doc makefile.
+# These are handle when the make target comes from the base doc makefile.
# In cases the .SVG files are built.
html-local: all-am