Proof

Author: quinntracy

content/en/docs/refguide/modeling/integration/change-data-capture/_index.md

@@ -17,11 +17,11 @@ CDC is intended for developers who need to move Mendix domain model data to exte
 
 A CDC service document in Studio Pro defines which entities the Mendix Runtime should track. On deployment, each tracked entity gets its own Kafka topic. Every time a committed object change occurs (create, update, or delete) the Mendix Runtime publishes an event to the corresponding topic.
 
-Read events are triggered as snapshots during startup or when a stream changes in a way that constitutes a breaking change. Snapshots populate the new topic with the current data of the tracked entity. For more information, see the [Revisions](/refguide/published-cdc-services/#revisions) section below.
+Read events are triggered as snapshots during startup or when a stream changes in a way that constitutes a breaking change. Snapshots populate the new topic with the current data of the tracked entity. For more information, see the [Revisions](/refguide/published-cdc-services/#revisions) section of *Published CDC Services*.
 
 The broker that receives these events is either the [Mendix Event Broker](/appstore/services/event-broker/) or a Bring Your Own Kafka (BYOK) cluster. For BYOK configuration details, see [Mendix Event Broker](/appstore/services/event-broker/).
 
-To move the streamed data to a destination such as Azure Blob Storage or AWS S3, you configure an [Event Broker Bridge](/appstore/services/event-broker/#manage-mx-broker-bridge) separately in the Event Broker Manager after deployment.
+To move the streamed data to a destination (such as Azure Blob Storage or AWS S3), you configure an [Event Broker Bridge](/appstore/services/event-broker/#manage-mx-broker-bridge) separately in the Event Broker Manager after deployment.
 
 ## Prerequisites
 

content/en/docs/refguide/modeling/integration/change-data-capture/published-cdc-services.md

@@ -31,14 +31,15 @@ This is an optional description for the CDC service.
 
 The **Entities to track** table lists the entities whose object changes are published to Kafka.
 
-{{< figure src="/attachments/refguide/modeling/integration/change-data-capture/published-cdc-service.png" alt="Published CDC Service document showing the Entities to track table with columns for Exposed name, Modification, Revision, and Topic" >}}
-
 Use the toolbar to manage tracked entities:
 
 * {{% icon name="add-filled" %}} **Add** – add an entity from the domain model
 * {{% icon name="subtract-circle" %}} **Remove** – stop tracking a selected entity
 * {{% icon name="refresh" %}} **Accept changes** – lock in the current [Revision](#revisions) numbers after reviewing modifications 
 
+
+{{< figure src="/attachments/refguide/modeling/integration/change-data-capture/published-cdc-service.png" alt="Published CDC Service document showing the Entities to track table with columns for Exposed name, Modification, Revision, and Topic" >}}
+
 ### Entities
 
 The **Entities** column refers to the domain model entity being tracked. Expand the row to view and select individual attributes and associations.
@@ -72,8 +73,8 @@ Each tracked entity has a **Revision** number that identifies the schema of its
 
 Studio Pro manages revisions automatically. When you modify the tracked configuration of an entity, Studio Pro marks it as **Changed** and calculates the new revision based on whether the change is breaking or non-breaking:
 
-* **Major revision** (for example, `1.0` → `2.0`) — a breaking change such as removing an attribute, renaming an entity's exposed name, or removing an entity from tracking. Consumers must be updated to use the new topic.
-* **Minor revision** (for example, `1.0` → `1.1`) — a non-breaking change such as adding a new attribute. Existing consumers can continue reading the topic without modification.
+* **Major revision** (for example, `1.0` → `2.0`) – a breaking change such as removing an attribute, renaming an entity's exposed name, or removing an entity from tracking. Consumers must be updated to use the new topic.
+* **Minor revision** (for example, `1.0` → `1.1`) – a non-breaking change such as adding a new attribute. Existing consumers can continue reading the topic without modification.
 
 {{< figure src="/attachments/refguide/modeling/integration/change-data-capture/published-cdc-service-changes.png" alt="Published CDC Service document showing entities with Changed and Removed modification states and updated revision numbers" >}}