anchor.diff:  After the connector starts, it completes the following actions:
   
   * xref:{link-mongodb-connector}#mongodb-performing-a-snapshot[Performs a consistent snapshot] of the collections in your MongoDB replica sets.
  -* Reads the oplogs/change streams for the replica sets.
  +* Reads the change streams for the replica sets.
   * Produces change events for every inserted, updated, and deleted document.
   * Streams change event records to Kafka topics.
   
  
positive.code: * Names of the collection and database that contain the new document.
  * If the event was part of a snapshot.
  * Timestamp for when the change was made in the database and ordinal of the event within the timestamp.
  * Unique identifier of the MongoDB operation, which depends on the version of MongoDB. It is either the `h` field in the oplog event, or a field named `stxnid`, which represents the `lsid` and `txnNumber` fields from the oplog event (oplog capture mode only).
  * Unique identifiers of the MongoDB session `lsid` and transaction number `txnNumber` in case the change was executed inside a transaction (change streams capture mode only).
  
  |8
  
negative.code: The {prodname} connector watches the stream and delivers the changes downstream.
  And, when the connector sees a replica set for the first time, it looks at the oplog to get the last recorded transaction and then performs a snapshot of the primary's databases and collections.
  When all the data is copied, the connector then creates a change stream from the position it read earlier from the oplog.
  
  As the MongoDB connector processes changes, it periodically records the position in the oplog/stream where the event originated.
  When the connector stops, it records the last oplog/stream position that it processed, so that upon restart it simply begins streaming from that position.
  