Changing 'Failure view' to 'Failures view' to match diagram and Azure UI.

Author: v-jbasden

articles/azure-monitor/app/app-insights-overview.md

@@ -34,7 +34,7 @@ To understand the number of Application Insights resources required to cover you
 
 :::image type="content" source="media/app-insights-overview/app-insights-overview-blowout.svg" alt-text="Diagram that shows the path of data as it flows through the layers of the Application Insights service." border="false" lightbox="media/app-insights-overview/app-insights-overview-blowout.svg":::
 
-Firewall settings need to be adjusted to make sure telemetry data can reach ingestion endpoints. For more information, see [IP addresses used by Azure Monitor](./ip-addresses.md).
+Firewall settings must be adjusted for data to reach ingestion endpoints. For more information, see [IP addresses used by Azure Monitor](./ip-addresses.md).
 
 ## How do I use Application Insights?
 
@@ -49,7 +49,7 @@ Consider starting with the [Application Map](app-map.md) for a high-level view.
 Two views are especially useful:
 
 - [Performance view](tutorial-performance.md): Get deep insights into how your application or API and downstream dependencies are performing. You can also find a representative sample to [explore end to end](transaction-diagnostics.md).
-- [Failure view](tutorial-runtime-exceptions.md): Understand which components or actions are generating failures and triage errors and exceptions. The built-in views are helpful to track application health proactively and for reactive root-cause analysis.
+- [Failures view](tutorial-runtime-exceptions.md): Understand which components or actions are generating failures and triage errors and exceptions. The built-in views are helpful to track application health proactively and for reactive root-cause analysis.
 
 [Create Azure Monitor alerts](tutorial-alert.md) to signal potential issues in case your application or components parts deviate from the established baseline.