Fix Acrolinx issues around voice and consistency

Author: ecfan

articles/logic-apps/logic-apps-enterprise-integration-b2b-list-errors-solutions.md

@@ -14,42 +14,41 @@ ms.date: 02/20/2025
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
-This article helps you troubleshoot errors that might happen in Azure Logic Apps B2B 
-scenarios and suggests appropriate actions for correcting those errors.
+This article helps you troubleshoot errors that might happen in Azure Logic Apps B2B scenarios and suggests appropriate actions for correcting those errors.
 
 ## Agreement resolution
 
 ### No agreement found
 
-**Error description**: No agreement found with Agreement Resolution Parameters.
+**Error description**: **No agreement found with Agreement Resolution Parameters.**
 
-**User action**: The agreement should be added to the integration account with agreed business identities. The business identities should match to the input message IDs.
+**User action**: Add an agreement with the appropriate business identities to your integration account. Make sure that the business identities match to the input message IDs.
 
 ### No agreement found with identities
 
-**Error description**: No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3'
+**Error description**: **No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3'**
 
-**User action**: Invalid AS2-From or AS2-To configured for agreement. Correct the AS2 message's "AS2-From" or "AS2-To" headers or the agreement to match the AS2 IDs in the AS2 message headers with agreement configurations.
+**User action**: The agreement has invalid **AS2-From** or **AS2-To** values. To match the AS2 IDs in the AS2 message headers for your agreement setup, correct the AS2 message header values **AS2-From** or **AS2-To** or the agreement.
 
 ## AS2
 
 ### Missing AS2 message headers  
 
-**Error description**: Invalid AS2 headers. One of the "AS2-To" or "AS2-From" headers is empty.
+**Error description**: **Invalid AS2 headers. One of the "AS2-To" or "AS2-From" headers is empty.**
 
-**User action**: An AS2 message was received that did not contain the AS2-From or AS2-To or both headers. Check AS2 message AS2-From and AS2-To headers and correct them based on agreement configuration.
+**User action**: A received AS2 message didn't contain the headers for **AS2-From**, **AS2-To**, or both. Check the AS2 message **AS2-From** and **AS2-To** headers, and correct them based on your agreement setup.
 
 ### Missing AS2 message body and headers    
 
-**Error description**: The request content is null or empty.
+**Error description**: **The request content is null or empty.**
 
-**User action**: An AS2 message was received that did not contain the message body.
+**User action**: A received AS2 message didn't contain a message body.
 
 ### AS2 message decryption failure
 
-**Error description**:  [processed/Error: decryption-failed]
+**Error description**: **`[processed/Error: decryption-failed]`**
 
-**User action**: Add @base64ToBinary to AS2Message before sending to partner.
+**User action**: Apply the `@base64ToBinary()` function to the AS2Message before sending the message to the trading partner.
 
 For example:
 
@@ -63,11 +62,11 @@ For example:
 },
 ``` 
 
-### MDN decryption failure
+### Message Disposition Notification (MDN) decryption failure
 
-**Error description**:  [processed/Error: decryption-failed]
+**Error description**: **`[processed/Error: decryption-failed]`**
 
-**User action**: Add @base64ToBinary to MDN before sending to partner.
+**User action**: Apply the `@base64ToBinary()` function to the MDN before sending the notification to the partner.
 
 For example:
 
@@ -82,42 +81,47 @@ For example:
 
 ### Missing signing certificate
 
-**Error description**: The Signing Certificate has not been configured for AS2 party. AS2-From: partner1 AS2-To: partner2
+**Error description**: **The Signing Certificate has not been configured for AS2 party. AS2-From: partner1 AS2-To: partner2**
 
-**User action**: Configure AS2 agreement settings with correct certificate for signature.
+**User action**: Set the AS2 agreement settings with the correct certificate for the signature.
 
 ## X12 and EDIFACT
 
 ### Leading or trailing space found    
 
-**Error description**: Error encountered during parsing. The EDIFACT transaction set with ID '123456' contained in interchange (without group) with ID '987654', with sender ID 'Partner1', receiver ID 'Partner2' is being suspended with following errors: "Leading Trailing separator found"
+**Error description**: **Error encountered during parsing. The EDIFACT transaction set with ID '123456' contained in interchange (without group) with ID '987654', with sender ID 'Partner1', receiver ID 'Partner2' is being suspended with following errors: "Leading Trailing separator found"**
 
-**User action**: The agreement settings to be configured to allow leading and trailing space. Edit agreement settings to allow leading and trailing space.
+**User action**: Set up or edit the agreement settings to allow leading and trailing whitespace.
 
-![allow space](./media/logic-apps-enterprise-integration-b2b-list-errors-solutions/leadingandtrailing.png)
+![Screenshot shows example for setting to allow leading and trailing whitespace.](./media/logic-apps-enterprise-integration-b2b-list-errors-solutions/leadingandtrailing.png)
 
-### Duplicate check has enabled in the agreement
+### Duplicate check is enabled in the agreement
 
-**Error description**: Duplicate Control Number
+**Error description**: **Duplicate Control Number**
 
-**User action**: This error indicates the received message has duplicate control numbers. Correct the control number and resend the message.
+**User action**: This error indicates that the received message has duplicate control numbers. Correct the control number, and resend the message.
 
 ### Missing schema in the agreement
 
-**Error description**: Error encountered during parsing. The X12 transaction set with ID '564220001' contained in functional group with ID '56422', in interchange with ID '000056422', with sender ID '12345678', receiver ID '87654321' is being suspended with following errors: "The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement"
+**Error description**: **Error encountered during parsing. The X12 transaction set with ID '564220001' contained in functional group with ID '56422', in interchange with ID '000056422', with sender ID '12345678', receiver ID '87654321' is being suspended with following errors: "The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement"**
 
-**User action**: Configure schema in the agreement settings.
+**User action**: Set up the schema in the agreement settings.
 
 ### Incorrect schema in the agreement
 
-**Error description**: The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement.
+**Error description**: **The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement.**
 
-**User action**: Configure correct schema in the agreement settings.
+**User action**: Set up the correct schema in the agreement settings.
 
 ## Flat file
 
 ### Input message with no body
 
-**Error description**: InvalidTemplate. Unable to process template language expressions in action 'Flat_File_Decoding' inputs at line '1' and column '1902': 'Required property 'content' expects a value but got null. Path ''.'.
+**Error description**: **InvalidTemplate. Unable to process template language expressions in action 'Flat_File_Decoding' inputs at line '1' and column '1902': 'Required property 'content' expects a value but got null. Path ''.'.**
+
+**User action**: This error indicates that the input message doesn't contain a body.
+
+## Related content
+
+- [Exchange B2B messages between partners using workflows in Azure Logic Apps](/azure/logic-apps/logic-apps-enterprise-integration-b2b)
 
-**User action**: This error indicates the input message does not contain a body.