Merge pull request #343 from sigmacomputing/Data-App-Reconciliation-Revision-Jan-20

Data App Revisions Jan 20

Author: pballai

site/sigmaguides/src/dataapps_pivot_spreading/dataapps_pivot_spreading.md

@@ -320,7 +320,7 @@ Act as a Data Adjustment Target:
 - This table holds the rows that will be updated during the spread process.
 - Adjustments made in the pivot table are applied to this table, modifying the relevant rows based on the selected `KEY` and `LEVEL` values passed.
 
-Act as am Intermediate Layer:
+Act as an Intermediate Layer:
 - It acts as a bridge between the source data (BASE_TABLE) and the final output.
 - Rows from the `BASE_TABLE` are merged into the `SPREAD_UPDATE` table if they don’t already exist, ensuring that all necessary data is available for spreading.
 
@@ -384,10 +384,10 @@ This creates a new `hidden` page called `Modal 1`. The page is hidden as we only
 
 Rename the page to `Adjustments` and the title from `New Modal` to `Adjustments`.
 
-For the purposes of this demonstration, this modal will allow the user to adjust the selected `Coalesced Revenue` from the pivot table, choosing from three different methods. It will also display information about selections have been made.
+For the purposes of this demonstration, this modal will allow the user to adjust the selected `Coalesced Revenue` from the pivot table, choosing from three different methods. It will also display information about which selections have been made.
 
 <aside class="positive">
-<strong>IMPORTANT:</strong><br> It production, it may not be desirable to show the additional details we will configure for display. We do so now for clarity only.
+<strong>IMPORTANT:</strong><br> Im production, it may not be desirable to show the additional details we will configure for display. We do so now for clarity only.
 </aside>
 
 ### Adding the Controls
@@ -738,7 +738,7 @@ Once Sigma evaluate the selected procedure, we are prompted to choose how requir
 
 Add another action to refresh the `Revenue Planning` pivot with the new data.
 
-Add another action to clear the `Selected Adjustments` and `Desire Adjustment` containers, just so we are always sure that the current values are removed prior to using the modal.
+Add another action to clear the `Selected Adjustments` and `Desired Adjustment` containers, just so we are always sure that the current values are removed prior to using the modal.
 
 Add one more action to `Navigate in this workbook` to the `Pivot` pages, `Top of page`.
 

site/sigmaguides/src/dataapps_reconciliation/dataapps_reconciliation.md

@@ -705,7 +705,7 @@ Before we configure Sigma to run the script on demand, we should make sure it wo
 
 Execute the following script in the Snowflake console:
 ```code
-CALL SIGMA_QUICKSTARTS_SNAPSHOTS.STORED_PROCEDURES.SNAPSHOT_INVENTORY_ADJUSTMENTS();
+ALL SIGMA_QUICKSTARTS.SNAPSHOT_AND_INVENTORY_ADJUSTMENTS_METADATA.SNAPSHOT();
 ```
 
 The expected response is:
@@ -778,9 +778,9 @@ Duration: 5
 <strong>IMPORTANT:</strong><br> Be aware that there may be a small amount of lag time (depending on the Snowflake warehouse configuration) between when a users clicks "Save" on an input table and the data being available in Snowflake. If we run our stored procedure before the data has landed, the latest edits will not appear in the the metadata table or snapshot. For the purposes of this QuickStart, we did not include logic to check the the data has landed, but wanted to mention this potential situation so that developers can include scripting to handle it.
 </aside>
 
-Lets perform to editing "runs" in Sigma, each time saving the edits and taking a snapshot. The expected outcome will be two additional snapshot tables. 
+Lets perform two editing "runs" in Sigma, each time saving the edits and taking a snapshot. The expected outcome will be two additional snapshot tables. 
 
-### Reset the text environment
+### Reset the test environment
 While not required, it may be helpful to know how to quickly reset the data so that the test results are more easily seen. Here is how to do that:
 
 **1:** Clear the one cell that was edited (to have the "1000" value). Do this directly in the Sigma UI. Just click on the cell that has the value, press the delete key and then enter. Save the input table data. It will not matter that Sigma will record this action in Snowflake, we are only concerned with rows that have values for `Ajusted_Qty`, so this edit will be ignored when we snapshot.

site/sigmaguides/src/use_cases_finance_discounted_cash_flow/use_cases_finance_discounted_cash_flow.md

@@ -37,7 +37,7 @@ Our cloud-based architecture offers:
 
 - Enhanced Governance and Security: Sigma inherits all the governance features from your cloud data warehouse, including audit trails and version history, ensuring data accuracy and reducing risks associated with manual errors.
 
-This QuickStart will provides an example of DCF, based on Sigma provided sample data, so users can build on their own. 
+This QuickStart provides an example of DCF, based on Sigma provided sample data, so users can build on their own. 
 
 <aside class="positive">
 <strong>IMPORTANT:</strong><br> Some screens in Sigma may appear slightly different from those shown in QuickStarts. This is because Sigma is continuously adding and enhancing functionality. Rest assured, Sigma’s intuitive interface ensures that any differences will not prevent you from successfully completing any QuickStart.