all review comments incorporated

Author: vibhuti sodhi

docs/topics/images/mta-cli-guide-app-insights.png

@@ -158,12 +158,12 @@ Issues are sorted into four categories by default. Information on these categori
 
 === Insights
 
-:FeatureName: Application Insights
+:FeatureName: Insights
 include::snippets/technology-preview-admonition.adoc[]
 
 Issues are generated by general rules, whereas string tags are generated by tagging rules. String tags indicate the presence of a technology but do not show the code location. With the introduction of Insights, you can see the technology used in the application along with its usage in the code.
 
-For example, a rule searching for a deprecated API usage in the code that does not impact the current migration but can be tracked and fixed when needed in the future.
+For example, a rule searching for deprecated API usage in the code that does not impact the current migration but can be tracked and fixed when needed in the future.
 
 Unlike issues, insights do not need to be fixed for a successful migration. They are generated by any tagging or non-tagging rule and do not have an effort and category assigned. They might have a message and tag.
 
@@ -172,7 +172,7 @@ Unlike issues, insights do not need to be fixed for a successful migration. They
 Insights are generated automatically if applicable or present. Currently, {ProductShortName} supports generating Insights when application anaylsis is done using CLI.
 =====
 
-You can view Insights under the Insights tab in the Static report.
+You can view Insights under the *Insights* tab in the static report.
 
 image::mta-cli-guide-app-insights.png[Insights tab in the Static report]