edit pass: tracing-web-app-availability-javascript

paulth1 · paulth1 · commit 61b1b6978a9e · 2022-08-12T11:30:38.000-07:00
diff --git a/articles/azure-monitor/app/distributed-tracing.md b/articles/azure-monitor/app/distributed-tracing.md
@@ -55,7 +55,7 @@ The following pages consist of language-by-language guidance to enable and confi
 
 In addition to the Application Insights SDKs, Application Insights also supports distributed tracing through [OpenCensus](https://opencensus.io/). OpenCensus is an open-source, vendor-agnostic, single distribution of libraries to provide metrics collection and distributed tracing for services. It also enables the open-source community to enable distributed tracing with popular technologies like Redis, Memcached, or MongoDB. [Microsoft collaborates on OpenCensus with several other monitoring and cloud partners](https://open.microsoft.com/2018/06/13/microsoft-joins-the-opencensus-project/).
 
-[Python](opencensus-python.md)
+For more information on OpenCensus for Python, see [Set up Azure Monitor for your Python application](opencensus-python.md).
 
 The OpenCensus website maintains API reference documentation for [Python](https://opencensus.io/api/python/trace/usage.html), [Go](https://godoc.org/go.opencensus.io), and various guides for using OpenCensus.
 
diff --git a/articles/azure-monitor/app/javascript.md b/articles/azure-monitor/app/javascript.md
@@ -80,7 +80,7 @@ cfg: { // Application Insights Configuration
 ```
 
 > [!NOTE]
-> For readability and to reduce possible JavaScript errors, all of the possible configuration options are listed on a new line in the preceding snippet code. If you don't want to change the value of a commented line, it can be removed.
+> For readability and to reduce possible JavaScript errors, all the possible configuration options are listed on a new line in the preceding snippet code. If you don't want to change the value of a commented line, it can be removed.
 
 #### Report script load failures
 
@@ -142,7 +142,7 @@ This telemetry includes:
     - Exception details and message accompanying the error.
     - Line and column number of the error.
     - URL where the error was raised.
-- **Network Dependency Requests** made by your app **XHR** and **Fetch** (fetch collection is disabled by default) requests, include information on the:
+- **Network Dependency Requests** made by your app **XHR** and **Fetch** (fetch collection is disabled by default) requests include information on the:
     - URL of dependency source.
     - Command and method used to request the dependency.
     - Duration of the request.
@@ -490,13 +490,13 @@ While the script is downloading from the CDN, all tracking of your page is queue
 --- | --- | --- | --- | --- |
 Chrome Latest ✔ |  Firefox Latest ✔ | IE 9+ & Microsoft Edge ✔<br>IE 8- Compatible | Opera Latest ✔ | Safari Latest ✔ |
 
-## ES3/Internet Explorer 8 Compatibility
+## ES3/Internet Explorer 8 compatibility
 
 We need to ensure that this SDK continues to "work" and doesn't break the JavaScript execution when it's loaded by an older browser. It would be ideal to not support older browsers, but numerous large customers can't control which browser their users choose to use.
 
 This statement does *not* mean that we'll only support the lowest common set of features. We need to maintain ES3 code compatibility. New features will need to be added in a manner that wouldn't break ES3 JavaScript parsing and added as an optional feature.
 
-[See GitHub for full details on Internet Explorer 8 support](https://github.com/Microsoft/ApplicationInsights-JS#es3ie8-compatibility)
+See GitHub for full details on [Internet Explorer 8 support](https://github.com/Microsoft/ApplicationInsights-JS#es3ie8-compatibility).
 
 ## Open-source SDK
 
diff --git a/articles/azure-monitor/app/monitor-web-app-availability.md b/articles/azure-monitor/app/monitor-web-app-availability.md
@@ -8,7 +8,7 @@ ms.reviewer: sdash
 
 # Monitor availability with URL ping tests
 
-The name *URL ping test* is a bit of a misnomer. These tests don't use Internet Control Message Protocol (ICMP) to check your site's availability. Instead, they use more advanced HTTP request functionality to validate whether an endpoint is responding. They measure the performance associated with that response. They also add the ability to set custom success criteria, coupled with more advanced features like parsing dependent requests and allowing for retries.
+The name *URL ping test* is a bit of a misnomer. These tests don't use the Internet Control Message Protocol (ICMP) to check your site's availability. Instead, they use more advanced HTTP request functionality to validate whether an endpoint is responding. They measure the performance associated with that response. They also add the ability to set custom success criteria, coupled with more advanced features like parsing dependent requests and allowing for retries.
 
 To create an availability test, you need to use an existing Application Insights resource or [create an Application Insights resource](create-new-resource.md).
 
@@ -33,7 +33,7 @@ To create your first availability request:
    |Parse dependent requests| The test requests images, scripts, style files, and other files that are part of the webpage under test. The recorded response time includes the time taken to get these files. The test fails if any of these resources can't be successfully downloaded within the timeout for the whole test. If the option isn't enabled, the test only requests the file at the URL that you specified. Enabling this option results in a stricter check. The test might fail for cases that aren't noticeable from manually browsing through the site.
    |Enable retries|When the test fails, it's retried after a short interval. A failure is reported only if three successive attempts fail. Subsequent tests are then performed at the usual test frequency. Retry is temporarily suspended until the next success. This rule is applied independently at each test location. *We recommend this option*. On average, about 80 percent of failures disappear on retry.|
    |Test frequency| This setting determines how often the test is run from each test location. With a default frequency of five minutes and five test locations, your site is tested every minute on average.|
-   |Test locations| The values for this setting are the places from which servers send web requests to your URL. *We recommend a minimum of five test locations* to ensure that you can distinguish problems in your website from network issues. You can select up to 16 locations.
+   |Test locations| The values for this setting are the places from which servers send web requests to your URL. *We recommend a minimum of 5 test locations* to ensure that you can distinguish problems in your website from network issues. You can select up to 16 locations.
 
 If your URL isn't visible from the public internet, you can choose to selectively open your firewall to allow only the test transactions through. To learn more about the firewall exceptions for availability test agents, consult the [IP address guide](./ip-addresses.md#availability-tests).
 
