Update simple-report.md

Author: twheeloc

support/dynamics-365/finance/financial-reporting/simple-report.md

@@ -25,12 +25,15 @@ ms.custom: sap:Financial reporting and management reporter\Issues with report de
 ---
 # Troubleshoot report design and data issues
 
-Here is a practical way to troubleshoot report design or missing data issues effectively. The key principle is to simplify the process and control variables, as focusing on a specific scope is often more manageable
-than diagnosing an entire report. Start by creating the smallest possible reproduction of the issue and make changes one at a time. In some cases, manually recreating a report or starting over with the design can 
-help uncover design flaws or process bugs, ensuring a smoother troubleshooting experience.
+A practical way to troubleshoot report design or missing data issues effectively is to simplify the process and control variables. Focusing on a specific scope is often more manageable than diagnosing an entire report. Start by creating the smallest possible reproduction of the issue and make changes one at a time. In some cases, manually recreating a report or starting over with the design helps uncover design flaws or process bugs. 
+
+To help determine the cause of a data mismatch, some common areas to validate are:
+ - Create a simple report to troubleshoot the issue.
+ - Check that your data mart integration is current and healthy.  
+
 
 ## Create a simple report for troubleshooting
-To create a simple report to help troubleshoot report issues, follow these steps:
+To create a simple report to troubleshoot report issues, follow these steps:
 1. Simplify the report as much as possible. The goal is to get to a single number.
 2. Remove any reporting tree and dimension set.
 3. Set the **Detail level** to **Financial**, **Account**, and **Transaction**.
@@ -42,21 +45,21 @@ To create a simple report to help troubleshoot report issues, follow these steps
  - Remove all modifiers for the column. 
 7. This should display a report with a single cell of data.
 8. Verify the report is working as expected.
-9. From there, you can add one modification at a time if your issue include specific design requirements.
-   a.	For example: currency filter, attribute filter, YTD, or BB.
+9. Add one modification at a time if your issue includes specific design requirements.
+   a.	For example: currency filter, attribute filter, year-to-date, or beginning balances.
 10.	If the issue still exists, contact support and provide the following:
- - Exported .tdbx files of your simplified report and your original report.
- - Screenshots of the simplified report build block designs (row & column).
- - Excel export of your report output.
- - Reporting parameters: Company, Reporting date and report name.
+ - Export .tdbx files of the simplified and original reports.
+ - Screenshots of the simplified report build block designs including rows and columns.
+ - Excel export of the report output.
+ - Reporting parameters: **Company**, **Reporting date**, and **Report name**.
  - Details about the incorrect amount and what the expected value is.
 
 ### Check the data mart state
 To check the state of your data mart, follow these steps:
-1. Go to **Report designer**, go to **Tools** > **Integration status**.
-2. Check that the **Status** is not **Failed** and the **Last Runtime** date is after you created your data. Usually, you'll track the General Ledger transactions to **Fact map**. Occasionally, due to system load and data volume, this can take longer. You may need to wait more than one hour for larger data changes to complete integration into data mart.
+1. In **Report designer**, go to **Tools** > **Integration status**.
+2. Check that the **Status** isn't **Failed** and the **Last Runtime** date is after you created your data. Usually, the General Ledger transactions are tracked to **Fact map**. Occasionally, due to system load and data volume, this can take longer. You may need to wait more than one hour for larger data changes to complete integration into data mart.
 3. To check more detailed statistics, go to **Tools** > **Reset data mart**. DO NOT reset the data mart.
-If there are transactions with 6 or more attempts, this could be *stuck* data due to integrity issues. Having amounts here doesn’t mean you have missing data on your report, but it can be a source of missing data. Work with Microsoft support to determine the cause of the stuck data.
+If there are transactions with six or more attempts, this could be *stuck* data due to integrity issues. Having amounts here doesn’t mean data is missing from your report, but it can be a source of missing data. Work with Microsoft support to determine the cause of the stuck data.
 4. If there are any **Misaligned main account** categories, reports based on account categories could report incorrect amounts.