docs(changes): fix grammar, markup in newsfragments; aggregate contributors (#2621)

* chore(authors): aggregate 4.3.0 contributors so far

* docs(changes): fix grammar and markup in 4.3.0 newsfragments

Author: vytas7

AUTHORS

@@ -224,6 +224,9 @@ listed below by date of first contribution:
 * granuels
 * George Spyropoulos (gespyrop)
 * edvatar (toroleapinc)
+* rikka0612 (ReinerBRO)
+* tuanaiseo
+* Het Patel (CuriousHet)
 
 (et al.)
 

docs/_newsfragments/2071.newandimproved.rst

@@ -1,6 +1,6 @@
 A new router option, :attr:`~.CompiledRouterOptions.default_to_on_request`, was
-added for providing a default responder by implementing ``on_request()`` on
-resources (the new option is disabled by default). When enabled,
+added to allow resources to provide a default responder via ``on_request()``
+(disabled by default). When enabled,
 ``on_request()`` is used as the default responder for every unimplemented HTTP
 verb except ``on_options()`` (and the special ``on_websocket`` handler).
 

docs/_newsfragments/2538.newandimproved.rst

@@ -1,5 +1,5 @@
 The :meth:`req.get_param_as_list <falcon.Request.get_param_as_list>` method now
-supports a new argument, `delimiter`, for splitting of values.
+supports a new argument, `delimiter`, for splitting values.
 In line with the OpenAPI v3 parameter specification, the supported delimiters
 currently include the ``'pipeDelimited'`` and ``'spaceDelimited'`` symbolic
 constants, as well as the literal ``','``, ``'|'``, and ``' '`` characters.

docs/_newsfragments/2583.bugfix.rst

@@ -1,9 +1,9 @@
-Due to the differences in interpretation of the ASGI specification, Uvicorn
-could set `client` in the HTTP connection scope in a way that broke
+Due to differences in interpretation of the ASGI specification, Uvicorn
+could set ``client`` in the HTTP connection scope in a way that broke
 :attr:`req.access_route <falcon.asgi.Request.access_route>` and
 :attr:`req.remote_addr <falcon.asgi.Request.remote_addr>` when the app server
 was bound to a Unix domain socket.
 
 This discrepancy was addressed, and Falcon should now fall back to the same
-default value (``'127.0.0.1'``) in this case as if `client` was missing
+default value (``'127.0.0.1'``) in this case as if ``client`` was missing
 altogether.

docs/_newsfragments/2594.misc.rst

@@ -1,4 +1,4 @@
 Falcon no longer adds an instance of :class:`logging.NullHandler` to the
-``falcon`` logger, so ASGI application tracebacks may still reach
+``falcon`` logger, so ASGI application tracebacks may now reach
 ``sys.stderr`` via the :any:`logging.lastResort` handler in the absence of
 configuration (see also: :ref:`debugging_asgi_applications`).

docs/changes/4.3.0.rst

@@ -24,11 +24,14 @@ Many thanks to all of our talented and stylish contributors for this release!
 
 - `0x1618 <https://github.com/0x1618>`__
 - `0xMattB <https://github.com/0xMattB>`__
+- `CuriousHet <https://github.com/CuriousHet>`__
 - `gespyrop <https://github.com/gespyrop>`__
 - `granuels <https://github.com/granuels>`__
 - `jap <https://github.com/jap>`__
+- `ReinerBRO <https://github.com/ReinerBRO>`__
 - `rushevich <https://github.com/rushevich>`__
 - `thisisrick25 <https://github.com/thisisrick25>`__
 - `toroleapinc <https://github.com/toroleapinc>`__
+- `tuanaiseo <https://github.com/tuanaiseo>`__
 - `TudorGR <https://github.com/TudorGR>`__
 - `vytas7 <https://github.com/vytas7>`__