Updated description

Signed-off-by: Dj Walker-Morgan <[email protected]>

Author: djw-m

product_docs/docs/pgd/6/reference/tables-views-functions/catalogs-visible.mdx

@@ -33,12 +33,12 @@ Catalog storing all possible commit scopes that you can use for
 
 #### `bdr.commit_scopes`  columns
 
-|          Name                  | Type | Description                              |
-|--------------------------------|------|----------------------------------------- |
-| commit_scope_id                | oid  | ID of the scope to be referenced         |
-| commit_scope_name              | name | Name of the scope to be referenced       |
+| Name                           | Type | Description                                             |
+|--------------------------------|------|---------------------------------------------------------|
+| commit_scope_id                | oid  | ID of the scope to be referenced                        |
+| commit_scope_name              | name | Name of the scope to be referenced                      |
 | commit_scope_origin_node_group | oid  | Node group for which the rule applies, referenced by ID |
-| sync_scope_rule                | text | Definition of the scope                  |
+| sync_scope_rule                | text | Definition of the scope                                 |
 
 
 ### `bdr.conflict_history`
@@ -77,7 +77,7 @@ For details, see [Logging conflicts to a table](/pgd/latest/reference/conflict-m
 | apply_tuple             | json                     | Json representation of the resulting (the one that has been applied) row                                                                                                              |
 | local_tuple_xmin        | xid                      | Transaction that produced the local conflicting row (if `local_tuple` is set and the row isn't frozen)                                                                                |
 | local_tuple_node_id     | oid                      | Node that produced the local conflicting row (if `local_tuple` is set and the row isn't frozen)                                                                                       |
-| local_tuple_commit_time | timestamp with time zone | Last-known-change timestamp of the local conflicting row (if `local_tuple` is set and the row isn't frozen)                                                                           |
+| local_tuple_commit_time | timestamp with time zone | Last-known-change timestamp of the local conflicting row (if `local_tuple` is set and the row isn't frozen). This commit timestamp belongs to the node that produced this tuple.                                                                          |
 
 ### `bdr.conflict_history_summary`