merge in latest

docs/validations/validations-getting-started.mdx

@@ -6,7 +6,7 @@ sidebar_label: 'Getting Started with Validations'
 
 ![Screenshot of a scenario](./img/scenario-example.png)
 
-**Validations** are used to assert states within you game. You can create the Scenarios you want to verify using our Scenario Builder, and can assert Rules against various metrics captured during gameplay. 
+**Validations** are used to assert states within your game. You can create Validation Scenarios using our Scenario Builder, and then run them against a gameplay recording to ensure that your game is behaving as expected. You can also create Validation Rules to assert specific criteria about your game, such as the average frames per second during a gameplay recording.
 
 ## Validation Suites
 
@@ -40,9 +40,9 @@ Check out the [full Rules reference](./validations-rules-reference) for more det
 
 ## Running Validations
 
-You can either run **all** of the Scenarios within a Suite, or test run an individual Scenario. To run a Suite, click the "Run Suite" button, and select a Gameplay Session to test against. When the Suite is finished running, you can view the results of each Scenario and Rule within the Suite on the Test Runs page.
+You can either run **all** of the Scenarios within a Suite, or trial run an individual Scenario. To run a Suite, click the "Run Suite" button, and select a Gameplay Session to test against. When the Suite is finished running, you can view the results of each Scenario and Rule within the Suite on the Test Runs page.
 
-To test run an individual Scenario, click the "Run Scenario" button within the Scenario's menu. The Scenario's results will be shown in a dialog, and will not be persisted.
+To trial run an individual Scenario, click the "Run Scenario" button within the Scenario's menu. The Scenario's results will be shown in a dialog, and will not be persisted.
 
 ![Screenshot of a scenario](./img/run-scenario.png)