Fix links

ecfan · ecfan · commit c8221b42147a · 2025-03-04T11:41:58.000-08:00
diff --git a/articles/logic-apps/monitor-track-b2b-transactions-standard.md b/articles/logic-apps/monitor-track-b2b-transactions-standard.md
@@ -134,31 +134,7 @@ For tracking to work correctly, make sure that all the following conditions are
 
    :::image type="content" source="media/monitor-track-b2b-transactions/example-x12-message-details.png" alt-text="Screenshot shows Premium integration account with B2B tracking selected, and a table with details about collected X12 messages.":::
 
-
-
-For more information about the JSON schema for these properties, see [Table schemas for tracking B2B transactions](tracking-table-schemas-standard.md).
-
-### X12 message properties
-
-| Column name | Expanded name |
-|-------------|---------------|
-| **AgreementName**| Agreement name |
-| **SenderParternerName** | Sender partner |
-| **ReceiverPartnerName** | Receiver partner |
-| **MessageStatus** | Message status |
-| **MessageDirection** | Message direction (**`send`** or **`receive`**) |
-| **MessageTime** | Message time |
-| **MessageClientTrackingId** | Message client tracking ID |
-| **InterchangeControlNumber** | Interchange control number |
-| **FunctionalGroupControlNumber** | Functional group control number |
-| **TransactionSetStatus** | Transaction set status |
-| **TransactionSetControlNumber** | Transaction set control number |
-| **IsFunctionalAckExpected** | Is a functional acknowledgment expected (**`true`** or **`false`**) |
-| **AckStatus** | Acknowledgment status |
-| **TransactionSetAckStatus** | Transaction set acknowledgment status |
-| **FunctionalAckStatus** | Functional acknowledgment status |
-
-For more information about the JSON schema for these message properties, see [Table schemas for tracking B2B transactions](tracking-table-schemas-standard.md#).
+For more information about these table columns, see [Tracking schemas for B2B transactions - Standard workflows](tracking-schemas-standard.md).
 
 ## Database tables
 
@@ -169,13 +145,11 @@ In your Azure Data Explorer cluster, the database stores transaction data in a t
 
 > [!NOTE]
 >
-> If you want to [create a tracking store](#manage-with-rest-api) using the Azure Logic Apps REST API, 
-> you must first manually create the two tables named **AS2TrackRecords** and **EdiTrackRecords** in your 
-> Azure Data Explorer database using specific [B2B tracking table schemas](tracking-table-schemas-standard.md). 
+> To [create a tracking store](#manage-with-rest-api) using the Azure Logic Apps REST API, 
+> you must first manually create two tables named **AS2TrackRecords** and **EdiTrackRecords** 
+> in your Azure Data Explorer database using specific [JSON schemas for tracking B2B transactions](tracking-schemas-standard.md). 
 > Your database must also grant **Ingester** permissions to your integration account resource.
 
-For more information, see [Table schemas for tracking B2B transactions - Standard workflows](tracking-table-schemas-standard.md).
-
 <a name="manage-with-rest-api"></a>
 
 ## Manage tracking stores with the REST API
@@ -191,7 +165,7 @@ Create a tracking store or update an existing one.
 > In this release, your integration account currently supports only one tracking store.
 > Before you create a tracking store using the Azure Logic Apps REST API, you must first 
 > manually create the two tables named **AS2TrackRecords** and **EdiTrackRecords** in your 
-> Azure  Data Explorer database using specific [table schemas for tracking B2B transactions](tracking-table-schemas-standard.md). 
+> Azure Data Explorer database using specific [JSON schemas for tracking B2B transactions](tracking-schemas-standard.md). 
 > Your database must also grant **Ingester** permissions to your integration account resource.
 
 `PUT https://management.azure.com/subscriptions/{subscription-ID}/resourceGroups/{resource-group-name}/providers/Microsoft.Logic/integrationAccounts/{integration-account-name}/groups/default/trackingstores/{tracking-store-name}?api-version=2016-06-01`
@@ -278,4 +252,4 @@ Return a success response for a successfully deleted tracking store.
 
 ## Related content
 
-- [Table schemas for tracking B2B transactions - Standard workflows](tracking-table-schemas-standard.md)
+- [Table schemas for tracking B2B transactions - Standard workflows](tracking-schemas-standard.md)
diff --git a/articles/logic-apps/tracking-schemas-consumption.md b/articles/logic-apps/tracking-schemas-consumption.md
@@ -258,7 +258,7 @@ The following table describes the attributes in a tracking schema for an X12 tra
 | **`direction`** | Yes | Enum | Message flow direction, which is either **`send`** or **`receive`** |
 | **`functionalGroupControlNumber`** | No | String | Functional group control number for the functional acknowledgment. This value populates only for the sender when a functional acknowledgment is received for the messages sent to the partner. |
 | **`interchangeControlNumber`** | No | String | Interchange control number for the functional acknowledgment. This value populates only for the sender when a functional acknowledgment is received for the messages sent to the partner. |
-| **`isaSegment`** | No | String | The ISA segment for the X12 message. This value populates only for the sender when a functional acknowledgment is received for the messages sent to the partner. |
+| **`isaSegment`** | No | String | The Interchange Control Header (ISA) segment for the X12 message. This value populates only for the sender when a functional acknowledgment is received for the messages sent to the partner. |
 | **`gsSegment`** | No | String | GS segment in the X12 message. This value populates only for the sender when a functional acknowledgment is received for the messages sent to the partner. |
 | **`isMessageFailed`** | Yes | Boolean | Whether the X12 message failed |
 | **`processingStatus`** | Yes | Enum | Processing status for the acknowledgment with these permitted values: **`Received`**, **`Generated`**, and **`Sent`** |
diff --git a/articles/logic-apps/tracking-schemas-standard.md b/articles/logic-apps/tracking-schemas-standard.md
@@ -96,7 +96,7 @@ The **MessageProperties** table column has a **dynamic** type structure that use
 | **isMessageSigned** | Boolean | Whether the AS2 message was signed |
 | **isMessageEncrypted** | Boolean | Whether the AS2 message was encrypted |
 | **isMessageCompressed** | Boolean | Whether the AS2 message was compressed |
-| **correlationMessageId** | String | Message ID for correlatating AS2 messages with Message Disposition Notifications (MDNs) |
+| **correlationMessageId** | String | Message ID for correlating AS2 messages with Message Disposition Notifications (MDNs) |
 | **incomingHeaders** | JToken dictionary | Header details for the incoming AS2 message |
 | **outgoingHeaders** | JToken dictionary | Header details for the outgoing AS2 message |
 | **isNrrEnabled** | Boolean | Whether Non-Repudiation of Receipt (NRR) is enabled |
@@ -215,7 +215,7 @@ The **MessageProperties** table column has a **dynamic** type structure that use
 | **needAk2LoopForValidMessages** | Boolean | Whether the AK2 loop is required for a valid message |
 | **segmentsCount** | Integer | Number of segments in the X12 transaction set |
 
-#### X12 transaction set acknowledgement - MessageProperties schema
+#### X12 transaction set acknowledgment - MessageProperties schema
 
 ```json
 {
@@ -369,6 +369,8 @@ The **MessageProperties** table column has a **dynamic** type structure that use
 | **ak903** | String | Number of received transaction sets |
 | **ak903** | String | Number of accepted transaction sets in the identified functional group |
 
+<a name="workflow-run-operation-schema"></a>
+
 ## WorkflowRunOperationInfo schema
 
 The **WorkflowRunOperationInfo** table column in the **AS2TrackRecords** table and **EdiTrackRecords** table captures information about the Standard logic app workflow run. This column has a **dynamic** type structure that uses the following JSON schema:
