Merge pull request #2418 from splunk/adasplunk-O11YDOCS-6384

Fix formatting of code and parameter samples.

Author: adasplunk

synthetics/test-config/private-locations.rst

@@ -144,17 +144,17 @@ Configuring Proxy Settings for Private Locations
 
 In environments where direct internet access is restricted, you can route synthetic test traffic through a proxy server by configuring the following environment variables:
 
-* HTTP_PROXY: Specifies the proxy server for HTTP traffic.
+* ``HTTP_PROXY``: Specifies the proxy server for HTTP traffic.
 
-    * Example: export HTTP_PROXY="\http://proxy.example.com:8080"
+    * Example: ``export HTTP_PROXY="\http://proxy.example.com:8080"``
 
-* HTTPS_PROXY: Specifies the proxy server for HTTPS traffic.
+* ``HTTPS_PROXY``: Specifies the proxy server for HTTPS traffic.
 
-    * Example: export HTTPS_PROXY="\https://proxy.example.com:8443"
+    * Example: ``export HTTPS_PROXY="\https://proxy.example.com:8443"``
 
-* NO_PROXY: Specifies a comma-separated list of domains or IP addresses that should bypass the proxy.
+* ``NO_PROXY``: Specifies a comma-separated list of domains or IP addresses that should bypass the proxy.
 
-    * Example: export NO_PROXY="localhost,127.0.0.1,.internal-domain.com"
+    * Example: ``export NO_PROXY="localhost,127.0.0.1,.internal-domain.com"``
 
 For example, here is what a command might look like after you modify it to fit your environment:
 
@@ -165,15 +165,15 @@ For example, here is what a command might look like after you modify it to fit y
     
 In this example:
 
-HTTP_PROXY and HTTPS_PROXY are set to route traffic through a proxy at \http://172.17.0.1:1234.
+``HTTP_PROXY`` and ``HTTPS_PROXY`` are set to route traffic through a proxy at ``http://172.17.0.1:1234``.
 
-NO_PROXY is configured to bypass the proxy for local addresses and specific domains like .signalfx.com and .amazonaws.com.
+``NO_PROXY`` is configured to bypass the proxy for local addresses and specific domains like .signalfx.com and .amazonaws.com.
 
 Ensure that these variables are correctly configured to comply with your network policies. This setup allows the synthetic tests to communicate securely and efficiently in a controlled network environment.
 
 When using runner, it's important to correctly configure the proxy settings to avoid issues with browser-based tests. The following steps should be followed when setting up their environment:
 
-1. :strong:`Ensure Proper NO_PROXY Setup`:
+1. :strong:`Ensure proper NO_PROXY setup`:
 
    - When configuring ``NO_PROXY`` always include the following addresses: