Line edits2

Author: lootle1

learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/5-azure-technologies-measure-process.md

@@ -8,7 +8,7 @@ However, the way in which features are released to application users can help to
 
 - Controlled deployments with *feature flags*, *feature rings*, and *canary deployments* allow you to release a feature to a limited set of users to prevent disrupting the experience of the whole customer base. Additionally, you can directly compare the performance of the customers with and without the feature to each other.
 - *Portal options* for users to decide if they want to be exposed to new functionality puts the users in control of their own experience. The fact that many users opt for a new feature might already be a confirmation that the previous functionality had room for improvement. If customers that opt for the new feature go back to the previous experience, it might be an indicator that the deployed MVP is missing the mark.
-- *Customer surveys* are a powerful feedback mechanism if they're implemented correctly. Customers provide information about their satisfaction if it's simple to give. One-click "traffic light" satisfaction surveys or single questions about new functionality might provide insights to help in evaluating whether the innovation hypothesis was correct. In general, only a few users answer longer surveys, and take the time to fill them in thoroughly and truthfully.
+- *Customer surveys* are a powerful feedback mechanism if they're implemented correctly. Customers provide information about their satisfaction if it's simple to give. One-click "traffic light" satisfaction surveys or single questions about new functionality might provide insights to help in evaluating whether the innovation hypothesis was correct. In general, only a few users answer longer surveys and take the time to fill them in thoroughly and truthfully.
 
 ## Understanding your application
 
@@ -30,17 +30,17 @@ Notifications typically report that there might be a problem without context abo
 
 After you formulate a hypothesis with the data provided by Azure Application Insights, you can analyze telemetry to measure whether the situation is now better or worse. You can embed custom business events in the application so that telemetry data contains additional information that helps in the measure process.
 
-[Funnels](/azure/azure-monitor/app/usage?tabs=aspnetcore#the-retention-tool?azure-portal=true) can be an insightful tool. With funnels, you can predefine the *flows* that you expect users to follow when they use the application. Then you can monitor which patterns users follow, and identify problems in the applications if users behave in unexpected ways.
+[Funnels](/azure/azure-monitor/app/usage?tabs=aspnetcore&branch=main#funnels---discover-how-customers-use-your-application) can be an insightful tool. With funnels, you can predefine the *flows* that you expect users to follow when they use the application. Then you can monitor which patterns users follow, and identify problems in the applications if users behave in unexpected ways.
 
 ### Retain users
 
-The Application Insights [retention tool](/azure/azure-monitor/app/usage?tabs=aspnetcore#the-retention-tool?azure-portal=true) offers specific functionality around user churn. It contains valuable learning data when combined with business events. For example, understanding which actions that customers who left the application unexpectedly took, allows you to formulate hypotheses with maximum business impact.
+The Application Insights [retention tool](/azure/azure-monitor/app/usage?tabs=aspnetcore&branch=main#users-sessions-and-events---analyze-telemetry-from-three-perspectives) offers specific functionality around user churn. It contains valuable learning data when combined with business events. For example, understanding which actions that customers who left the application unexpectedly took, allows you to formulate hypotheses with maximum business impact.
 
 For example, if most users who abandoned your website did so from the payment method page, you'd suspect a business problem there. Maybe the payment options are insufficient or not clearly displayed, or another problem is preventing users from moving forward in their shopping process.
 
 ### Impact analysis
 
-[Impact analysis](/azure/azure-monitor/app/usage?tabs=aspnetcore#the-retention-tool?azure-portal=true) is a feature in Azure Application Insights that correlates technical aspects of the application to tangible business metrics.
+[Impact analysis](/azure/azure-monitor/app/usage?tabs=aspnetcore&branch=main#impact-analysis---discover-how-different-properties-influence-conversion-rates) is a feature in Azure Application Insights that correlates technical aspects of the application to tangible business metrics.
 
 For example, how fast should the product page load so that most users continue with their shopping process? With impact analysis, you can show the relationship between page load time and the rate of users who purchase the product shown. This information can help you to validate or reject an innovation hypothesis, and to convert business requirements into technical specifications.