apache · randall · Jul 28, 2020 · Jul 27, 2020
diff --git a/configs/strategies.yaml.default b/configs/strategies.yaml.default
@@ -108,7 +108,7 @@
 #         - 404
 #         - 502
 #         - 503
-#       health_check: # specifies the list of healthchecks that should be considered for failover. A list of enums: 'passive' or 'active'
+#       health_check: # specifies the list of health checks that should be considered for failover. A list of enums: 'passive' or 'active'
 #         - passive
 #         - active
 #   - strategy: 'mid-tier-south'

diff --git a/doc/admin-guide/files/records.config.en.rst b/doc/admin-guide/files/records.config.en.rst
@@ -971,7 +971,7 @@ mptcp
 
    The setting must contain at least one of ``ip``, ``host``, ``hostonly`` or ``both``
    for session reuse to operate.  The other values may be used for greater control
-   with TLS sessoin reuse.
+   with TLS session reuse.
 
 .. note::
 
@@ -3475,7 +3475,7 @@ SSL Termination
   Lowering this setting to ``1`` can be interesting when ``proxy.config.ssl.session_cache`` is enabled because
   otherwise for every new TLSv1.3 connection two session IDs will be inserted in the session cache.
   On the other hand, if ``proxy.config.ssl.session_cache``  is disabled, using the default value is recommended.
-  In those scenarios, increasing the number of tickets could be potentially benefitial for clients performing
+  In those scenarios, increasing the number of tickets could be potentially beneficial for clients performing
   multiple requests over concurrent TLS connections as per RFC 8446 clients SHOULDN'T reuse TLS Tickets.
 
   For more information see https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_num_tickets.html

diff --git a/doc/admin-guide/files/volume.config.en.rst b/doc/admin-guide/files/volume.config.en.rst
@@ -81,7 +81,7 @@ occupy span `/dev/disk1` taking each 50% of its space and `volume 3` takes 100%
 storage.config::
 
       /dev/disk1
-      /dev/disk2 volume=3 # <- exclusinve span
+      /dev/disk2 volume=3 # <- exclusive span
 
 volume.config::
 

diff --git a/doc/admin-guide/logging/formatting.en.rst b/doc/admin-guide/logging/formatting.en.rst
@@ -505,7 +505,7 @@ shi   Origin Server  IP address resolved via DNS by |TS| for the origin server.
 shn   Origin Server  Host name of the origin server.
 nhi   Origin Server  Destination IP address of next hop
 nhp   Origin Server  Destination port of next hop
-ppv   Proxy Protocol Proxy Protocol Version used (if any) between the Loadbalancer
+ppv   Proxy Protocol Proxy Protocol Version used (if any) between the Load Balancer
       Version        and |TS|
 pps   Proxy Protocol Source IP received via Proxy Protocol context from the LB to
       Source IP      the |TS|

diff --git a/doc/admin-guide/monitoring/statistics/core/origin.en.rst b/doc/admin-guide/monitoring/statistics/core/origin.en.rst
@@ -114,7 +114,7 @@ Origin Server
    :type counter
    :units bytes
 
-.. ts:stat:: global proxy.process.http.origin_shutdown.release_invalid_repsonse integer
+.. ts:stat:: global proxy.process.http.origin_shutdown.release_invalid_response integer
    :type counter
    :units bytes
 

diff --git a/doc/admin-guide/plugins/maxmind_acl.en.rst b/doc/admin-guide/plugins/maxmind_acl.en.rst
@@ -62,7 +62,7 @@ Rules
 You can mix and match the allow rules and deny rules, however deny rules will always take precedence so in the above case ``127.0.0.1`` would be denied.
 The IP rules can take either single IPs or cidr formatted rules. It will also accept IPv6 IP and ranges.
 
-The regex portion can be added to both the allow and deny sections for creating allowable or denyable regexes. Each regex takes a country code first and a regex second.
+The regex portion can be added to both the allow and deny sections for creating allowable or deniable regexes. Each regex takes a country code first and a regex second.
 In the above example all requests from the US would be allowed except for those on ``txt`` and ``mp3`` files. More rules should be added as pairs, not as additions to existing lists.
 
 Currently the only rules available are ``country``, ``ip``, and ``regex``, though more can easily be added if needed. Each config file does require a top level

diff --git a/doc/admin-guide/plugins/memory_profile.en.rst b/doc/admin-guide/plugins/memory_profile.en.rst
@@ -19,7 +19,7 @@ Memory_profile Plugin
   under the License.
 
 
-This plugin listens for plugin msgs and invokes jemalloc control
+This plugin listens for plugin messages and invokes jemalloc control
 operations.
 
 Installation
@@ -45,7 +45,7 @@ restart to pick up.
 Plugin Messages
 ===============
 
-The plugin responds to the following mesages sent via traffic_ctl.
+The plugin responds to the following messages sent via traffic_ctl.
 
 Message    Action
 ========== ===================================================================================
@@ -89,11 +89,11 @@ to get text output or graphs. Details of how to use jeprof are in the man pages
 You may want to send the dump message periodically to analyze how the |TS| memory allocation changes over time.  This periodic dump can also be achieved by setting the
 ``lg_prof_interval`` option in the run time configuration string.
 
-If the profiling is taking a significating amount of processing time and affecting |TS| performance, send the deactivate message to turn off profiling.::
+If the profiling is taking a significant amount of processing time and affecting |TS| performance, send the deactivate message to turn off profiling.::
 
     traffic_ctl plugin msg memory_profile deactivate
 
-Send the stats message to cause detailed jemalloc stats to be printed in traffic.out.  These stats represent actvitiy since the start of the |TS| process.::
+Send the stats message to cause detailed jemalloc stats to be printed in traffic.out.  These stats represent activity since the start of the |TS| process.::
 
     traffic_ctl plugin msg memory_profile stats
 

diff --git a/doc/admin-guide/plugins/stats_over_http.en.rst b/doc/admin-guide/plugins/stats_over_http.en.rst
@@ -88,7 +88,7 @@ This sets the path value for stats
 
 .. option:: allow_ip=
 
-A comma separated white list of ipv4 addresses allowed to accesss the endpoint
+A comma separated white list of ipv4 addresses allowed to access the endpoint
 
 .. option:: allow_ip6=
 

diff --git a/doc/admin-guide/plugins/traffic_dump.en.rst b/doc/admin-guide/plugins/traffic_dump.en.rst
@@ -48,7 +48,7 @@ Plugin Configuration
 
    .. option:: --sensitive-fields <field1,field2,...,fieldn>
 
-   (`optional`) - a comma seperatated list of HTTP case-insensitive field names whose values are considered sensitive information. Traffic Dump will not dump the incoming field values for any of these fields but will instead dump a generic value for them of the same length as the original. If this option is not used, a default list of "Cookie,Set-Cookie" is used. Providing this option overwrites that default list with whatever values the user provides. Pass a quoted empty string as the argument to specify that no fields are sensitive,
+   (`optional`) - a comma separated list of HTTP case-insensitive field names whose values are considered sensitive information. Traffic Dump will not dump the incoming field values for any of these fields but will instead dump a generic value for them of the same length as the original. If this option is not used, a default list of "Cookie,Set-Cookie" is used. Providing this option overwrites that default list with whatever values the user provides. Pass a quoted empty string as the argument to specify that no fields are sensitive,
 
    .. option:: --sni-filter <SNI_Name>
 

diff --git a/doc/developer-guide/api/functions/TSPluginDSOReloadEnable.en.rst b/doc/developer-guide/api/functions/TSPluginDSOReloadEnable.en.rst
@@ -21,7 +21,7 @@
 TSPluginDSOReloadEnable
 *************************
 
-Control whether this plugin will take part in the remap dynamic reload preocess (remap.config)
+Control whether this plugin will take part in the remap dynamic reload process (remap.config)
 
 Synopsis
 ========