Made changes based on team review

Author: Prabha Kylasamiyer Sundara Rajan

docs/topics/mta-rn-technical-changes-7-3-2.adoc

@@ -8,4 +8,4 @@
 
 The following technical changes have been made in {ProductFullName} 7.3.2:
 
-* The Eclipse IDE plugin for {ProductShortName} is available till 7.3.2. The plugin will be deprecated in future releases.
+* The Eclipse IDE plugin for {ProductShortName} is available up to 7.3.2. The plugin will be deprecated in future releases.

docs/topics/ref_fixed-issues-7-3-2.adoc

@@ -6,11 +6,11 @@
 [id="fixed-issues-7-3-2_{context}"]
 = Fixed issues
 
-This section provides the following bug fixes and resolved issues and other problems that have a significant impact on the {ProductFullName} 7.3.2.
+This section provides the following bug fixes and resolved issues that have a significant impact on the {ProductFullName} 7.3.2.
 
 .{ProductShortName} now generates consistent results after analyzing large .EAR binary files 
 
-Previously, when analyzing binary applications, MTA relied on the Maven search index to determine whether dependencies are internal to the application or whether the application was installed as an open-source dependency. Depending on the availability of the Maven search index, it was assumed that an open-source dependency was internal to the application and includes the dependency in the analysis results. In this case, analysis returned more incidents and greater effort to address issues found in dependencies, even if the user did not expect to see those results. This issue has been resolved in {ProductShortName} 7.3.2. link:https://issues.redhat.com/browse/MTA-5588[(MTA-5588)]
+Previously, when analyzing binary applications, {ProductShortName} relied on the Maven search index to determine whether dependencies are internal to the application or whether the application was installed as an open-source dependency. Depending on the availability of the Maven search index, it was assumed that an open-source dependency was internal to the application and includes the dependency in the analysis results. In this case, analysis returned more incidents and greater effort to address issues found in dependencies, even if the user did not expect to see those results. This issue has been resolved in {ProductShortName} 7.3.2. link:https://issues.redhat.com/browse/MTA-5588[(MTA-5588)]
 
 .{ProductShortName} does not generate false positives when analyzing Java applications