minor updates

Author: vibhuti sodhi

docs/topics/mta-review-reports.adoc

@@ -158,19 +158,22 @@ Issues are sorted into four categories by default. Information on these categori
 
 === Insights
 
-Insights provide helpful information about the technologies used in the application and their usage in the code.
+include::
+
+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.
 
 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.
 
 [NOTE]
 =====
-Insights are generated automatically, if applicable or present. However, you must run the application analysis by using the CLI because MTA 7.1 does not support their generation through the UI.
+Insights are generated automatically if applicable or present.
 =====
 
-You can view Insights in the Static report under the Insights tab and in the analysis output under the Insights section.
+You can view Insights under the Insights tab in the Static report.
 
-.Example: Insights generated by a tagging rule with undefined effort and category
+.Example: Insights generated by a tagging rule with undefined effort
 
 [source,terminal]
 ----
@@ -188,7 +191,7 @@ You can view Insights in the Static report under the Insights tab and in the ana
       pattern: .*wicket.*\.jar
 ----
 
-.Example: Insights generated by a non-tagging rule with zero effort and no category
+.Example: Insights generated by a non-tagging rule with zero effort
 
 [source,terminal]
 ----