Modified the MTA-5588 description based on feedback

Author: Prabha Kylasamiyer Sundara Rajan

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

@@ -10,7 +10,7 @@ This section provides the following bug fixes and resolved issues that have a si
 
 .{ProductShortName} now generates consistent results after analyzing large .EAR binary files 
 
-Previously, when analyzing binary applications, {ProductShortName} relied on the Maven search index to determine whether dependencies were 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. This issue has been resolved in {ProductShortName} 7.3.2 by adding the flag `--disable-maven-search` to the `analyze` command. 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 embedded dependencies were internal to the application or were publicly available (usually classified as open-source dependency). Depending on the availability of the Maven search index, an open-source dependency could be wrongly classified as internal to the application and was included as a dependency in the analysis results. In this case, the analysis returned more incidents and greater effort to address issues found in dependencies. This issue has been resolved in {ProductShortName} 7.3.2 by adding the flag `--disable-maven-search` to the `analyze` command. When disabled, the analysis will consistently classify dependencies. link:https://issues.redhat.com/browse/MTA-5588[(MTA-5588)]
 
 .{ProductShortName} does not generate false positives when analyzing Java applications