chore: comments

Co-authored-by: Daria Pardue <[email protected]>

Author: nbbeeken

src/mongo_client.ts

@@ -516,7 +516,7 @@ export class MongoClient extends TypedEventEmitter<MongoClientEvents> implements
    * @remarks
    * Calling `connect` is optional since the first operation you perform will call `connect` if it's needed.
    * `timeoutMS` specified at the client-level will bound the time any operation can take before throwing a timeout error.
-   * However, when the operation being run is automatically connecting your `MongoClient` the timeoutMS will only be used for the operation portion of task.
+   * However, when the operation being run is automatically connecting your `MongoClient` the `timeoutMS` will only be used for the operation portion of task.
    * This means the time to setup the `MongoClient` does not count against `timeoutMS`.
    * If you are using `timeoutMS` we recommend connecting your client explicitly in advance of any operation to avoid this inconsistent execution time.
    *
@@ -719,7 +719,7 @@ export class MongoClient extends TypedEventEmitter<MongoClientEvents> implements
    * @remarks
    * Calling `connect` is optional since the first operation you perform will call `connect` if it's needed.
    * `timeoutMS` specified at the client-level will bound the time any operation can take before throwing a timeout error.
-   * However, when the operation being run is automatically connecting your `MongoClient` the timeoutMS will only be used for the operation portion of task.
+   * However, when the operation being run is automatically connecting your `MongoClient` the `timeoutMS` will only be used for the operation portion of task.
    * This means the time to setup the `MongoClient` does not count against `timeoutMS`.
    * If you are using `timeoutMS` we recommend connecting your client explicitly in advance of any operation to avoid this inconsistent execution time.
    *