Merge pull request #2314 from splunk/tcarter-anchors-DOCGUILD-26785

tcarter-anchors-DOCGUILD-26785

Author: aurbiztondo-splunk

synthetics/test-config/test-config.rst

@@ -21,42 +21,29 @@ Manage synthetic tests
 
 To simulate diverse types of traffic to your site or application, use a range of configuration options to customize each of your tests.
 
-.. raw:: html
-
-  <embed>
-    <h2>Devices</h2>
-  </embed>
+========================================================================================
+Devices
+========================================================================================
 
 When you set up a test in Splunk Synthetic Monitoring, you can configure the viewport and network connection of the device from which the test is simulated. 
 
 Because Browser tests capture the visual experience of a page, while Uptime and API tests only capture response data, viewport applies to Browser tests only. Network connection applies to all test types. 
 
-.. raw:: html
-
-  <embed>
-    <h3>Viewport</h3>
-  </embed>
-
-
+----------------------------------------------------------------------------------------
+Viewport
+----------------------------------------------------------------------------------------
 Browser tests in Splunk Synthetic Monitoring capture the visual experience of a user interacting with your application. The viewport is the framed area on a device's screen for viewing information, such as the browser window on a desktop. By default, Browser tests run from a desktop-sized viewport. You can configure tests to run from other viewport sizes to test the user experience from a variety of window sizes and device types. 
 
 When you set up a test, you can choose the viewport size from a list of common devices, or set a custom viewport by height and width. 
 
-
-.. raw:: html
-
-  <embed>
-    <h3>Network connection</h3>
-  </embed>
-
+----------------------------------------------------------------------------------------
+Network connection
+----------------------------------------------------------------------------------------
 You can run Browser, Uptime, or API tests to simulate network connections of various latencies, including Mobile LTE, Mobile 3G, DSL, Mobile 5G, and cable internet. Testing your site from a variety of connection types lets you monitor the experience of users in a variety of settings. 
 
-.. raw:: html
-
-  <embed>
-    <h2>Variables</h2>
-  </embed>
-
+========================================================================================
+Variables
+========================================================================================
 Use variables to fill in fields, provide URLs, and enter other information during your tests. 
 
 .. list-table::
@@ -70,14 +57,9 @@ Use variables to fill in fields, provide URLs, and enter other information durin
    * - Global variables 
      - Pre-saved, reusable variables you can define once and use across all your Browser and API tests. See :ref:`global-variables` to learn more. 
 
-
-.. raw:: html
-
-  <embed>
-    <h2>Locations</h2>
-  </embed>
-
-
+========================================================================================
+Locations
+========================================================================================
 Specify locations for your tests to simulate traffic from a range of checkpoints around the world, or use private locations to test sites from within a private network.
 
 For more, see: 
@@ -88,12 +70,9 @@ For more, see:
 .. * See :ref:`private-locations` to set up private locations. 
 
 
-.. raw:: html
-
-  <embed>
-    <h2>Test state and current status</h2>
-  </embed>
-
+========================================================================================
+Test state and current status
+========================================================================================
 You can use the play and pause buttons in the more menu (|more|) of your tests to pause or resume data collection. 
 
 The current status of a test is updated every time you load the :guilabel:`Test Overview` page in Splunk Synthetic Monitoring. The following table describes the possible status types for each test. 
@@ -117,14 +96,9 @@ The current status of a test is updated every time you load the :guilabel:`Test
    * - Failure
      - The test encountered a failure. 
 
-
-
-.. raw:: html
-
-  <embed>
-    <h2>Test naming conventions</h2>
-  </embed>
-
+========================================================================================
+Test naming conventions
+========================================================================================
 Choosing informative names for your tests and alerts helps organize content. Here are some guidelines: 
 
 * Add a category as a prefix to your test name like group, application, brand, or team names so that you can simplify searches. For example, these two Browser tests start with ``[ButtercupGames]``. 
@@ -136,13 +110,9 @@ Choosing informative names for your tests and alerts helps organize content. Her
       :alt: This image shows two Browser tests with the prefix [ButtercupGames].
 
 
-.. raw:: html
-
-  <embed>
-    <h2>Troubleshoot broken tests </h2>
-  </embed>
-
-
+========================================================================================
+Troubleshoot broken tests
+========================================================================================
 Follow these guidelines to troubleshoot a broken test. 
 
 #. (Optional) Make a copy of the test so that you can check various solutions before fixing the original test. 
@@ -159,12 +129,9 @@ Follow these guidelines to troubleshoot a broken test.
 #. Verify that there is one instance only of the selector you want to use in your test. If the selector appears more than once your test might break again in the future. Unique selectors provide optimal test performance. 
 #. Update your tests with your findings. 
 
-.. raw:: html
-
-  <embed>
-    <h2>Filter tests</h2>
-  </embed>
-
+========================================================================================
+Filter tests
+========================================================================================
 You can filter by test type, key-value pairs, and more. 
 
 .. image:: /_images/synthetics/syn-filter-test.png