fixes table error (#1400)

Author: terakilobyte

source/reference/change-events.txt

@@ -86,7 +86,7 @@ following table describes each field in the change stream response document:
        <view-fcv>` at the time of the change stream's
        opening/resumption. See :ref:`change-stream-resume-token` for the
        full list of ``_data`` types.
-       
+
        See :ref:`change-stream-resume` for an example of resuming a
        change stream by ``resumeToken``.
 
@@ -170,7 +170,6 @@ following table describes each field in the change stream response document:
    * - ``to.db``
      - string
      - The new name of the database.
-     - 
 
    * - ``to.coll``
      - string
@@ -315,7 +314,7 @@ following table describes each field in the change stream response document:
    * - ``operationDescription.to.db``
      - string
      - Indicates the new dataname name of the renamed collection.
-     
+
        .. versionadded:: 6.0
 
    * - ``operationDescription.to.coll``
@@ -356,7 +355,7 @@ following table describes each field in the change stream response document:
        transaction </core/transactions>`, the associated change stream
        notifications will have the same ``clusterTime`` value, namely
        the time when the transaction was committed.
-       
+
        On a sharded cluster, events that occur on different shards can
        have the same ``clusterTime`` but be associated with different
        transactions or even not be associated with any transaction. To
@@ -375,7 +374,7 @@ following table describes each field in the change stream response document:
 
        .. versionadded:: 6.0
 
-   * - ``txnNumber`` 
+   * - ``txnNumber``
      - NumberLong
 
      - The transaction number.
@@ -409,15 +408,15 @@ The following example illustrates an ``insert`` event:
       clusterTime: <Timestamp>,
       wallTime: <ISODate>,
       ns: {
-         db: 'engineering', 
+         db: 'engineering',
          coll: 'users'
       },
       documentKey: {
-         userName: 'alice123', 
+         userName: 'alice123',
          _id: ObjectId("599af247bb69cd89961c986d")
       },
       fullDocument: {
-         _id: ObjectId("599af247bb69cd89961c986d"), 
+         _id: ObjectId("599af247bb69cd89961c986d"),
          userName: 'alice123',
          name: 'Alice'
       }
@@ -444,8 +443,8 @@ The following example illustrates an ``update`` event:
       operationType: 'update',
       clusterTime: <Timestamp>,
       wallTime: <ISODate>,
-      ns: { 
-         db: 'engineering', 
+      ns: {
+         db: 'engineering',
          coll: 'users'
       },
       documentKey: {
@@ -473,8 +472,8 @@ opened with the ``fullDocument : updateLookup`` option:
       operationType: 'update',
       clusterTime: <Timestamp>,
       wallTime: <ISODate>,
-      ns: { 
-         db: 'engineering', 
+      ns: {
+         db: 'engineering',
          coll: 'users'
       },
       documentKey: {
@@ -490,7 +489,7 @@ opened with the ``fullDocument : updateLookup`` option:
             "newSize" : 36
          } ]
       },
-      fullDocument: { 
+      fullDocument: {
          _id: ObjectId("58a4eb4a30c75625e00d2820"),
          name: 'Alice',
          userName: 'alice123',
@@ -522,19 +521,19 @@ The following example illustrates a ``replace`` event:
       clusterTime: <Timestamp>,
       wallTime: <ISODate>,
       ns: {
-         db: 'engineering', 
+         db: 'engineering',
          coll: 'users'
       },
-      documentKey: { 
+      documentKey: {
          _id: ObjectId("599af247bb69cd89961c986d")
       },
       fullDocument: {
-         _id: ObjectId("599af247bb69cd89961c986d"), 
+         _id: ObjectId("599af247bb69cd89961c986d"),
          userName: 'alice123',
          name: 'Alice'
       }
    }
-   
+
 A ``replace`` operation uses the update command, and consists of two stages:
 
 - Delete the original document with the ``documentKey`` and