DOCSP-28396: Removed instances of e.g. (#591)

Author: DBirtolo-mdb

source/fundamentals/connection/connection-options.txt

@@ -35,7 +35,7 @@ parameters of the connection URI to specify the behavior of the client.
        authentication mechanisms.
 
    * - **authMechanismProperties**
-     - comma separated key:value pairs, e.g. "opt1:val1,opt2:val2"
+     - comma separated key:value pairs, for example, "opt1:val1,opt2:val2"
      - ``null``
      - Specifies additional options provided for authentication, such as
        enabling hostname canonicalization for GSSAPI.
@@ -46,7 +46,7 @@ parameters of the connection URI to specify the behavior of the client.
      - Specifies the database that connections should authenticate against.
 
    * - **compressors**
-     - comma separated list of strings, e.g. "snappy,zlib,zstd"
+     - comma separated list of strings, for example, "snappy,zlib,zstd"
      - ``null``
      - Specifies the allowed compression types for wire protocol messages
        sent to or received from the server. See :ref:`node-network-compression`
@@ -156,7 +156,7 @@ parameters of the connection URI to specify the behavior of the client.
      - Specifies the default read preference for the client (excluding tags). See :ref:`read preference <read-preference>` for more information.
 
    * - **readPreferenceTags**
-     - comma-separated key:value pairs (e.g. "dc:ny,rack:1" and "dc:ny)
+     - comma-separated key:value pairs, for example, "dc:ny,rack:1" and "dc:ny
        can be specified multiple times, each instance of this key is a
        separate tag set
      - ``null``

source/fundamentals/crud/query-document.txt

@@ -20,8 +20,8 @@ specifying matching criteria in a **query document**. Query documents contain
 one or more query operators that apply to specific fields which  determine which
 documents to include in the result set.
 
-In a query document, you can match fields against literal values
-(e.g. ``{ title: 'The Room' }``) or you can compose
+In a query document, you can match fields against literal values, such as
+``{ title: 'The Room' }``, or you can compose
 :manual:`query operators </reference/operator/query/>` to express more
 complex matching criteria. In this guide, we cover the following categories
 of query operators in MongoDB and show examples on how to use them:

source/fundamentals/crud/read-operations/text.txt

@@ -19,8 +19,8 @@ Text search, using the ``$text`` query operator, lets you search string
 type fields in your collection for words or phrases. This operator
 performs a logical ``OR`` on each term separated by a space in the search
 string. You can also specify additional options to the operator to
-handle case sensitivity, word stemming (e.g. plural forms, tense) and stop
-words for a supported language. This is particularly useful for
+handle case sensitivity, stop words, and word stemming (such as plural
+forms or other tenses) for a supported language. This is particularly useful for
 unstructured text such as transcripts, essays, or web pages.
 
 The ``$text`` query operator requires that you specify the search field in

source/fundamentals/indexes.txt

@@ -33,7 +33,7 @@ When you execute a query against MongoDB, your query can include three
 parts:
 
 - query criteria that specify field(s) and value(s) you are looking for
-- options that affect the query's execution (e.g. read concern)
+- options that affect the query's execution, such as read concern
 - projection criteria to specify the fields MongoDB should return (optional)
 
 When all the fields specified in the query criteria and projection of a