DOCSP-17224 fix typos in log message docs

Author: ajhuh-mdb

source/reference/log-messages.txt

@@ -196,7 +196,7 @@ specific instance of its subfield ``_id`` that triggered truncation
 printed without data as ``{"_id":{}}``. The remainder of the ``request``
 attribute is then omitted.
 
-Log entires containing one or more truncated attributes include a
+Log entries containing one or more truncated attributes include a
 ``truncated`` object which provides the following information for each
 truncated attribute in the log entry:
 
@@ -240,7 +240,7 @@ Pretty Printing
 
 .. include:: /includes/fact-use-jq-with-structured-logging.rst
 
-You can use ``jq`` to pretty-print log entires as follows:
+You can use ``jq`` to pretty-print log entries as follows:
 
 - Pretty-print the entire log file:
 
@@ -683,7 +683,7 @@ the the amount of log messages MongoDB outputs. Verbosity levels can be
 adjusted for all components together, or for specific
 :ref:`named components <log-message-components>` individually.
 
-Verbosity affects log entires in the :ref:`severity
+Verbosity affects log entries in the :ref:`severity
 <log-severity-levels>` categories **Informational** and **Debug** only.
 Severity categories above these levels are always shown.
 
@@ -1017,7 +1017,7 @@ showing a client connection followed by a disconnection:
    {"t":{"$date":"2020-06-01T13:06:59.027-0500"},"s":"I", "c":"NETWORK", "id":22943,"ctx":"listener","msg":"connection accepted from {session_remote} #{session_id} ({connectionCount}{word} now open)","attr":{"session_remote":"127.0.0.1:61298","session_id":164,"connectionCount":11,"word":" connections"}}
    {"t":{"$date":"2020-06-01T13:07:03.490-0500"},"s":"I", "c":"NETWORK", "id":22944,"ctx":"conn157","msg":"end connection {remote} ({connectionCount}{word} now open)","attr":{"remote":"127.0.0.1:61298","connectionCount":10,"word":" connections"}}
 
-The log IDs for these two entires are ``22943`` and ``22944``
+The log IDs for these two entries are ``22943`` and ``22944``
 respectively. You could then filter your log output to show only these
 log IDs, effectively showing only client connection activity, using the
 following ``jq`` syntax:
@@ -1035,7 +1035,7 @@ Filtering by Date Range
 ```````````````````````
 
 Log output can be further refined by filtering on the timestamp field,
-limiting log entires returned to a specific date range. For example, 
+limiting log entries returned to a specific date range. For example, 
 the following returns all log entries that occurred on April 15th, 2020:
 
 .. code-block:: bash