Updated articles based on the Aarti's suggestions.

Author: lucciz01

support/dynamics-365/commerce/development-sdks/set-up-dev-environment-debugging.md

@@ -4,7 +4,7 @@ description: Resolves errors that occur when you debug a Tier 1 Retail Server VM
 author: josaw1 
 ms.author: josaw
 ms.reviewer: rassadi, brstor
-ms.date: 09/01/2023
+ms.date: 09/04/2023
 ---
 # Errors when you debug against a Tier 1 Retail Server virtual machine in an e-commerce development environment
 
@@ -22,6 +22,8 @@ When you debug against a Tier 1 environment, because the site is now calling a d
 
 The following screenshot shows an example of an error that might occur when a variant is selected on a product details page.
 
+> Unhandled Rejection (ActionError): Error
+
 :::image type="content" source="media/set-up-dev-environment-debugging/unhandled-rejection-error.png" alt-text="Screenshot that shows an Unhandled Rejection Action error.":::
 
 The following screenshot shows an example of a similar error in a browser's debugger tools (F12 Developer Tools). The error message mentions a violation of the content security policy directive.

support/dynamics-365/commerce/financial-statements/fix-common-posting-issues.md

@@ -4,7 +4,7 @@ description: Provides resolutions to help you fix common statement posting issue
 author: josaw1 
 ms.author: josaw
 ms.reviewer: shajain, brstor
-ms.date: 09/01/2023
+ms.date: 09/04/2023
 ms.search.form: RetailStatementTable_SOCreateFailed, RetailStatementTable_InvoiceFailed, RetailStatementTable_PaymentPosted, RetailStatementTable_Aggregated, RetailStatementTable_CustomerOrderCreated, RetailStatementTable_Invoiced
 ---
 # Fix common statement posting issues by editing transactions
@@ -22,7 +22,7 @@ Sometimes, statement posting fails because the data in one or more transactions
 
 The data is corrected by editing the necessary transactions. The steps that are required to edit the transactions vary, depending on which stage of statement posting an issue occurs during. This article first lists the generic steps that are required to edit a transaction, depending on the stage of statement posting. It then lists common errors that occur during the stages and provides the specific steps that are required to fix each issue.
 
-> [NOTE]
+> [!NOTE]
 > For information about the structure of the Excel files that are downloaded when transactions are edited, see [Edit and audit cash and carry and cash management transactions](/dynamics365/commerce/edit-cash-trans).
 
 ## Issues during statement calculation
@@ -65,7 +65,7 @@ One step of the statement posting process is to create customer orders by groupi
 
   **Cause**: This issue occurs because the **Site** and **Warehouse** fields are configured as mandatory for the transactions, but some of the transactions are missing values or have incorrect values for those fields. This error is generated for transactions that are imported from external systems where validation might have missed the issue, or in cases where the values that are specified for the fields aren't valid.
 
-  **Resolution**: To fix the issue, follow the steps in the preceding procedure. In step 6, on the **Transactions** and **SalesTransactions** tabs of the Excel file (if those tabs are present), correct the **Site** and **Warehouse** values.
+  **Resolution**: To fix the issue, follow the steps in the [preceding procedure](#issues-during-order-creation). In step 6, on the **Transactions** and **SalesTransactions** tabs of the Excel file (if those tabs are present), correct the **Site** and **Warehouse** values.
 
   > [!NOTE]
   > The **Site** and **Warehouse** fields aren't available by default in Excel. To add them, follow the instructions in [Add fields to an Excel workbook to edit retail transactions](/dynamics365/commerce/add-fields-excel).
@@ -74,7 +74,7 @@ One step of the statement posting process is to create customer orders by groupi
 
   **Cause**: This issue occurs because the batch number is configured as mandatory for an item, but it isn't provided.
 
-  **Resolution**: To fix the issue, follow the steps in the preceding procedure. In step 6, on the **Lines** or **Sales transaction** tab of the Excel file, update the **Batch number** value for the item.
+  **Resolution**: To fix the issue, follow the steps in the [preceding procedure](#issues-during-order-creation). In step 6, on the **Lines** or **Sales transaction** tab of the Excel file, update the **Batch number** value for the item.
 
   > [!NOTE]
   > The **Batch number** field isn't available by default in Excel. To add it, follow the instructions in [Add fields to an Excel workbook to edit retail transactions](/dynamics365/commerce/add-fields-excel).
@@ -100,19 +100,19 @@ After customer orders are created, the next statement posting step is to try to
 
   **Cause**: This issue occurs because the transaction date belongs to a fiscal period that's no longer open. This error is generated when transactions haven't been posted for a long time.
 
-  **Resolution**: To fix the issue, follow the steps in the preceding procedure. In step 8, on the **Statement aggregations** tab of the Excel file, update the **Business date** field to a value that corresponds to an open fiscal period.
+  **Resolution**: To fix the issue, follow the steps in the [preceding procedure](#issues-during-customer-order-invoicing). In step 8, on the **Statement aggregations** tab of the Excel file, update the **Business date** field to a value that corresponds to an open fiscal period.
 
 - > While processing the state Payments posted, generic exception encountered in retail statement in the controller : Posting results for journal batch number \<batch number> Voucher \<Voucher> Voucher \<Voucher> Period for 1/1/2000 does not exist. Posting results for journal batch number \<batch number> Voucher \<Voucher> Voucher \<Voucher> Fiscal year for 1/1/2000 does not exist.
 
   **Cause**: This issue is similar to the previous one.
 
-  **Resolution**: To fix the issue, follow the steps in the preceding procedure. In step 8, on the **Transactions**, **Sales Transactions**, and **Payment Transactions** tabs of the Excel file, update the **Business date** field to a value that corresponds to an open fiscal period.
+  **Resolution**: To fix the issue, follow the steps in the [preceding procedure](#issues-during-customer-order-invoicing). In step 8, on the **Transactions**, **Sales Transactions**, and **Payment Transactions** tabs of the Excel file, update the **Business date** field to a value that corresponds to an open fiscal period.
 
 - > While processing the state Customer order invoiced, generic exception encountered in retail statement \<> in the controller : Posting Posting Sales order: \<> Item: \<> Inventory dimension Location must be specified.
 
   **Cause**: This issue occurs because the **Site** and **Warehouse** fields are configured as mandatory for the transactions, but some of the transactions are missing values or have incorrect values for those fields. This error is generated for transactions that are imported from external systems where validation might have missed the issue, or in cases where the values that are specified for the fields aren't valid.
 
-  **Resolution**: To fix the issue, follow the steps in the preceding procedure. In step 8, on the **Transactions** and **SalesTransactions** tabs of the Excel file (if those tabs are present), correct **Site** and **Warehouse** values.
+  **Resolution**: To fix the issue, follow the steps in the [preceding procedure](#issues-during-customer-order-invoicing). In step 8, on the **Transactions** and **SalesTransactions** tabs of the Excel file (if those tabs are present), correct **Site** and **Warehouse** values.
 
   > [!NOTE]
   > The **Site** and **Warehouse** fields aren't available by default in Excel. To add them, follow the instructions in [Add fields to an Excel workbook to edit retail transactions](/dynamics365/commerce/add-fields-excel).
@@ -121,8 +121,8 @@ After customer orders are created, the next statement posting step is to try to
 
   **Cause**: This issue occurs because a required field for statement posting is missing a value.
 
-  **Resolution**: To fix the issue, follow the steps in the preceding procedure. In step 8, correct the values for the fields that are mentioned in the error message.
+  **Resolution**: To fix the issue, follow the steps in the [preceding procedure](#issues-during-customer-order-invoicing). In step 8, correct the values for the fields that are mentioned in the error message.
 
 - > While processing aggregation state Sales order is invoiced for this aggregation. Transaction state Customer order invoiced, the invoice couldn't be found for the manually invoiced sales order for this aggregation \<>.
 
-  **Resolution**: To fix the issue, follow the steps in the preceding procedure. In step 8, on the **Statement aggregations** tab of the Excel file, check whether the **Business date** value for the aggregation matches the invoice date of the manually invoiced sales order for the aggregation. If the values don't match, update the **Business date** value to the invoice date of the order.
+  **Resolution**: To fix the issue, follow the steps in the [preceding procedure](#issues-during-customer-order-invoicing). In step 8, on the **Statement aggregations** tab of the Excel file, check whether the **Business date** value for the aggregation matches the invoice date of the manually invoiced sales order for the aggregation. If the values don't match, update the **Business date** value to the invoice date of the order.

support/dynamics-365/commerce/financial-statements/inventory-errors-posting.md

@@ -4,7 +4,7 @@ description: Provides workarounds for inventory-related issues during statement
 author: josaw1 
 ms.author: josaw
 ms.reviewer: shajain, brstor
-ms.date: 09/01/2023
+ms.date: 09/04/2023
 ms.search.form: RetailStatementTable_InvoiceFailed
 ---
 # Statement posting errors due to unavailable inventory or update conflicts
@@ -27,7 +27,7 @@ For a consistent posting experience, Microsoft recommends that you enable physic
 
 For example, no inventory is available for an item, but a cashier returns the item and then adds it back to the same transaction at a reduced price to mimic a price match. In this case, both the return transaction and the sales transaction will be pulled into the same statement of the single customer order. However, because there's no guarantee that the return line (which increases the inventory) will be posted before the sales line (which reduces the inventory) is posted, inventory errors can occur. If physical negative inventory is enabled in this scenario, transaction posting isn't negatively affected, and the system correctly reflects the inventory.
 
-To enable negative physical inventory for an item model group in Commerce headquarters, follow these steps:
+To enable physical negative inventory for an item model group in Commerce headquarters, follow these steps:
 
 1. Go to **Inventory management** > **Setup** > **Inventory**.
 1. In the left navigation pane, select the item model group.

support/dynamics-365/commerce/payments/payments-auto-settled.md

@@ -4,11 +4,11 @@ description: Resolves an issue where a payment is settled in the Adyen portal im
 author: josaw1 
 ms.author: josaw
 ms.reviewer: rassadi, brstor
-ms.date: 09/01/2023
+ms.date: 09/04/2023
 ---
 # Payments are automatically settled before orders are invoiced or shipped
 
-This article provides a resolution for an issue where a payment is settled in the Adyen portal immediately before the sales order is invoiced or shipped in Microsoft Dynamics 365 Commerce.
+This article provides a resolution for an issue where a payment is settled in the Adyen portal immediately after an order is placed, even though the sales order hasn't been invoiced or shipped in Microsoft Dynamics 365 Commerce.
 
 ## Symptoms