Merge pull request #2265 from splunk/gschatz-DOCGUILD-25905

Update transactional browser test table

Author: gschatz-splunk

synthetics/browser-test/set-up-browser-test.rst

@@ -456,6 +456,8 @@ The following image shows how to configure a test to go to a URL, wait for 10 se
    :alt: This image shows a browser test with three steps: go to url, wait 20 seconds, then log in. 
 
 
+.. _configurable-wait-times:
+
 Limits and defaults for configurable wait times 
 ------------------------------------------------------
 Here are the limits for each type of wait time. The maximum limit for a run is 30 minutes, after which it times out. 

synthetics/browser-test/set-up-transactional-browser-test.rst

@@ -46,7 +46,8 @@ A step doesn't generate its own dedicated metrics, but it counts toward the metr
 
 Types of steps you can include in your Browser Tests
 -----------------------------------------------------------
-The following table describes the types of steps you can include: 
+Assertions are checks to see what state an object exists in, for example if text is present or an element is visible.  
+The following table describes the types of steps you can include for actions: 
 
 .. list-table::
    :header-rows: 1
@@ -58,15 +59,15 @@ The following table describes the types of steps you can include:
    * - Accept alert
      - Accept an alert that appears on the page.
 
-   * - Dismiss alert
-     - Dismiss an alert that appears on the page.
-
    * - Clear
      - Clear an element you identify under :guilabel:`Selector`. Optionally, wait for navigation. 
 
    * - Click
      - Click on an element you identify under :guilabel:`Selector`. Optionally, wait for navigation. 
 
+   * - Dismiss alert
+     - Dismiss an alert that appears on the page.
+
    * - Fill in field
      - Fill a field you identify under :guilabel:`Selector` with a value you provide under :guilabel:`Value`. Optionally, wait for navigation. For security and reusability, use a built-in, custom, or global variable to provide the value. See :ref:`global-variables` to learn more.
 
@@ -88,26 +89,9 @@ The following table describes the types of steps you can include:
    * - Switch to main
      - Switch focus back to the main frame of the webpage.
 
-   * - Wait for text present
-     - Wait until the text identified in the key-value pair under :guilabel:`Value` appears on the webpage.
-
-   * - Wait for text present
-     - Wait until the text identified in the key-value pair under :guilabel:`Value` appears on the webpage.
-
-   * - Wait for text not present
-     - Wait until the text identified in the key-value pair under :guilabel:`Value` is not present on the webpage.
-
-   * - Wait for element present
-     - Wait until the element you identify under :guilabel:`Selector` is present on the webpage.
-
-   * - Wait for element not present
-     - Wait until the element you identify under :guilabel:`Selector` is not present on the webpage.
-
-   * - Wait for element visible
-     - Wait until the element you identify under :guilabel:`Selector` is visible on the webpage.
+   * - Wait
+     - Wait a certain number of minutes. See, :ref:`configurable-wait-times`.
 
-   * - Wait for element not visible
-     - Wait until the element you identify under :guilabel:`Selector` is not visible on the webpage.