corrections for the 7.3.0 RNs

Author: Mariya Pershina

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

@@ -12,4 +12,4 @@ This section provides the following bug fixes and resolves issues and other prob
 Previously, for compiled Java Maven projects, the {ProductShortName} CLI included incidents by analyzing the `target` folder. This generated different reports for Java Maven projects before and after running the `mvn-clean-package` command. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5078[(MTA-5078)]
 
 .Application credential update now triggers a new discovery task
-Previously, when you update the source or Maven credential for an application, a new discovery task was not triggered in the {ProductShortName} {WebName}. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5121[(MTA-5121)]
+Previously, when you updated the source or Maven credential for an application, a new discovery task was not triggered in the {ProductShortName} {WebName}. This issue has been resolved in {ProductShortName} 7.3.0. link:https://issues.redhat.com/browse/MTA-5121[(MTA-5121)]

docs/topics/ref_known-issues-7-3-0.adoc

@@ -10,7 +10,7 @@ This section provides highlighted known issues in {ProductFullName} version 7.3.
 
 
 .`.NET` Framework application analysis fails in the {ProductShortName} {CLIName} 
-When you analyze `.NET` Framework applications in Windows containers using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables: 
+When you analyze `.NET` Framework applications in Windows containers by using the {ProductShortName} {CLIName}, the analysis fails for the following environment variables: 
 
 * `DOTNET_PROVIDER_IMG`: `quay.io/konveyor/dotnet-external-provider:release-0.7`
 * `RUNNER_IMG`: `quay.io/konveyor/kantra:latest`
@@ -29,7 +29,7 @@ Workaround: set the `--run-local=false` flag to analyze non-Java applications. l
 
 .Application analysis fails to get a list of dependencies for Node.js in the {ProductShortName} UI
 
-When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error is displayed in the analysis log:
+When you run an application analysis for the Node.js language provider by using the {ProductShortName} user-interface (UI), the analysis completes with the following error displayed in the analysis log:
 
 ----
 level=error msg="failed to get list of dependencies for provider" error="dependency provider path not set" provider=nodejs'

docs/topics/ref_new-features-7-3-0.adoc

@@ -23,11 +23,11 @@ include::snippets/developer-preview-admonition.adoc[]
 
 .{ProductShortName} now uses Red Hat Build of Keycloak for user authentication
 
-{ProductShortName} {ProductVersion} now uses `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name has changed. The pod name for {rhbk-short} is changed to `rhbk-operator`. (link:https://issues.redhat.com/browse/MTA-4540[MTA-4540])
+{ProductShortName} {ProductVersion} now uses the `{rhbk-first}` instance for user authentication and authorization. The {ProductShortName} Operator manages the `{rhbk-short}` instance and configures a dedicated realm with necessary roles and permissions. For `{rhbk-short}`, the secret and the pod name have changed. The pod name for {rhbk-short} is changed to `rhbk-operator`. (link:https://issues.redhat.com/browse/MTA-4540[MTA-4540])
 
 .Listing all languages in an application is now available
 
-In {ProductShortName} {ProductVersion}, you can list all languages in an application by using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the --`override-provider-settings` flag when you analyze the application.
+In {ProductShortName} {ProductVersion}, you can list all languages in an application by using the `--list-languages` flag in the {CLIName}. The listed language that has no supported providers requires a custom rule set and the `--override-provider-settings` flag when you analyze the application.
 
 :FeatureName: Listing all languages in an application
 include::snippets/developer-preview-admonition.adoc[]