docs: document v7.13.0 features

- Live formulas (HARDFORMULA/SOFTFORMULA) in dcc-validations with operator-friendly explanations
- MPE_VALIDATIONS table doc: add HARDFORMULA/SOFTFORMULA to RULE_TYPE values
- Roadmap: mark Frontend Formulae and Regex Rules as delivered
- SAS VA Embed: document Live vs Confirm filter modes
- ViewBoxes: document edge/corner drag resizing
- Licensing: combined-key paste, key preview, protocol warning
- CAS Tables: REPLACE load type support and temp table cleanup
- Editor: native date/time pickers, paste-validation overlay, row status indicators
- Stage page: Formatted/Unformatted toggle on the approvals screen
- Viya deploy: configurator improvements, deploy checks, login page UX
- Index page: add live formulas and VA embed to features list

docs/admin-services.md

@@ -24,7 +24,7 @@ Button info as follows:
 
 ## Licence Key Screen
 
-The licence key screen is where you apply or update your Data Controller licence key.  The following features are available:
+The licence key screen is where you apply or update your Data Controller licence key.  Three improvements have been made to make this easier:
 
 * **Paste both keys at once** - if you have received a combined key, simply paste it into the licence key field and both the licence key and activation key fields are filled in automatically.  You can toggle between the combined-key input and the traditional two-field layout.
 * **Preview before applying** - as soon as both fields are populated, the key details (expiry date, number of users, active features) are displayed so you can confirm the key is correct before clicking Apply.

docs/cas-tables.md

@@ -41,7 +41,7 @@ It can happen that a CAS table is configured in Data Controller but not loaded i
 
 ### REPLACE Load Type
 
-The REPLACE load type (which replaces all rows in the target table with the staged data) is supported on CAS tables.  This works the same way as it does for regular SAS datasets - see [MPE_TABLES](/dcc-tables/#loadtype) for general REPLACE documentation.
+The REPLACE load type (which replaces all rows in the target table with the staged data) is now fully supported on CAS tables.  This works the same way as it does for regular SAS datasets - see [MPE_TABLES](/dcc-tables/#loadtype) for general REPLACE documentation.
 
 ## Unloading
 

docs/dc-userguide.md

@@ -50,7 +50,7 @@ New rows can be added using the right click context menu, or the 'Add Row' butto
 
 #### Native Date and Time Pickers
 
-Date, time, and datetime columns use native browser pickers when editing a cell.  This provides a familiar calendar and time selector, and respects your browser's locale settings for date and time formats.
+Date, time, and datetime columns now use native browser pickers when editing a cell.  This provides a familiar calendar and time selector, and respects your browser's locale settings for date and time formats.
 
 #### Paste Validation Overlay
 

docs/dcc-validations.md

@@ -70,7 +70,7 @@ Each row calculates its own result - the PRICE in row 1 is multiplied by the VOL
 ### Editor behaviour
 
 * When you paste a formula into the grid, column names are automatically translated so the formula works in its new position.
-* A cell that is overwritten by a formula is flagged so you can revert it.
+* A cell that has been overwritten by a formula is flagged so you can revert it.
 * Formula-looking values pasted from Excel are treated as plain data (not evaluated), unless you explicitly choose "Apply as formula".
 
 ### Special values
@@ -81,7 +81,7 @@ Formulas can reference three special values that are resolved at runtime:
 * `DC.USER_NAME` - the logged-in user id.
 * `DC.ORIG_VALUE` - the original cell value before the current edit.
 
-Example - show the current user id if the row is changed, otherwise keep the original value:
+Example - show the current user id if the row has been changed, otherwise keep the original value:
 
 ```
 = if( DC.ROW_STATUS != 'U', DC.USER_NAME, DC.ORIG_VALUE )

docs/deploy-viya.md

@@ -131,14 +131,14 @@ Now the services are deployed (including the service which creates the staging a
 * Compute Context - the context configured in Step 1
 
 !!! note
-    On the first-launch configuration screen, the **Groups** dropdown shows your own groups first, the **Contexts** dropdown groups contexts by their batch user, and a **Verify** button lets you confirm the startup service is running before continuing.  If no admin groups are found, a clear message is shown instead of the screen hanging silently.
+    The first-launch configuration screen has been improved.  The **Groups** dropdown now shows your own groups first, the **Contexts** dropdown groups contexts by their batch user, and a new **Verify** button lets you confirm the startup service is running before continuing.  If no admin groups are found, a clear message is shown instead of the screen hanging silently.
 
 !!! note
-    The login page provides input contrast and validation.  Submitting empty fields does not produce an infinite spinner.
+    The login page has been improved with better input contrast and validation.  Submitting empty fields no longer produces an infinite spinner.
 
 ### Deploy Checks
 
-The deploy process runs additional checks during installation to catch configuration issues early.  For larger Viya environments, the deploy script is chunked for reliability.  The compute context is also automatically corrected during deploy if needed.
+The deploy process now runs additional checks during installation to catch configuration issues early.  For larger Viya environments, the deploy script is chunked for reliability.  The compute context is also automatically corrected during deploy if needed.
 
 !!! note
     A debug comment is added to the compute context during deploy.  This is permanent - it is not removed by subsequent deploys.