Applying peer review suggestions

mpershina · anarnold97 · web-flow · commit aef647c08c54 · 2025-07-04T15:30:37.000+02:00
Co-authored-by: Andy Arnold &lt;anarnold@redhat.com&gt;
diff --git a/assemblies/cli-guide/assembly_analyzing-nonjava-applications.adoc b/assemblies/cli-guide/assembly_analyzing-nonjava-applications.adoc
@@ -18,10 +18,10 @@ endif::[]
 Starting from {ProductFullName} version 7.1.0, you can run the application analysis on applications written in languages other than Java. You can perform the analysis either of the following ways:
 
 * Select a supported language provider to run the analysis for. 	
-* Overwrite the existing supported language provider with your own unsupported language provider and then run the analysis for it. 
+* Overwrite the existing supported language provider with your own unsupported language provider, and then run the analysis on it.
  
 
-IMPORTANT: Analyzing applications written in languages other than Java is only possible in container mode. You can use containerless CLI only for Java applications. For more information, see xref:running-the-containerless-mta-cli_analyzing-applications-mta-cli[Analyzing an application in containerless mode].
+IMPORTANT: Analyzing applications written in languages other than Java is only possible in container mode. You can use the containerless CLI only for Java applications. For more information, see xref:running-the-containerless-mta-cli_analyzing-applications-mta-cli[Analyzing an application in containerless mode].
 
 
 include::topics/mta-cli/proc_analyze-selected-provider.adoc[leveloffset=+1]
diff --git a/docs/topics/mta-cli/con_intro-to-the-cli.adoc b/docs/topics/mta-cli/con_intro-to-the-cli.adoc
@@ -17,7 +17,7 @@ The {ProductFullName} command-line interface (CLI) provides a comprehensive set
 :FeatureName: Analyzing applications written in the .NET language
 include::../snippets/developer-preview-admonition.adoc[]
 
-:FeatureName: Analysing applications written in the Python and Node.js languages
+:FeatureName: Analyzing applications written in the Python and Node.js languages
 include::../snippets/technology-preview-admonition.adoc[]
 
 The CLI provides numerous reports that highlight the analysis without using the other tools. You can use the CLI to customize {ProductShortName} analysis options or integrate with external automation tools.
diff --git a/docs/topics/mta-cli/proc_analyzing-multiple-apps-with-mta-cli.adoc b/docs/topics/mta-cli/proc_analyzing-multiple-apps-with-mta-cli.adoc
@@ -5,7 +5,7 @@
 [id="analyzing-multiple-apps-with-mta-cli_{context}"]
 = Analyzing multiple applications
 
-You can use the {ProductFullName} {CLINameTitle} to perfrom ana application analysis for multiple applications at once and generate a combined report.
+You can use the {ProductFullName} {CLINameTitle} to perform an application analysis for multiple applications at once and generate a combined report.
 
 :FeatureName: Analyzing multiple applications
 include::../snippets/developer-preview-admonition.adoc[]
diff --git a/docs/topics/mta-cli/proc_generating-discovery-manifest.adoc b/docs/topics/mta-cli/proc_generating-discovery-manifest.adoc
@@ -19,7 +19,7 @@ You can generate the discovery manifest for the Cloud Foundry (CF) application b
 
 . Open the terminal application and navigate to the `<{ProductShortName}_HOME>/` directory.
 
-. List supported platforms for the discovery process:
+. List the supported platforms for the discovery process:
 +
 [subs="+quotes"]
 ----
diff --git a/docs/topics/mta-cli/proc_installing-cli-for-docker.adoc b/docs/topics/mta-cli/proc_installing-cli-for-docker.adoc
@@ -5,7 +5,7 @@
 [id="installing-cli-for-docker_{context}"]
 = Installing the CLI for use with Docker on Windows
 
-To migrate applications built with .NET framework version 4.5 or later on Windows to cross-platform .NET 8.0, you must install the CLI for use with Docker on Windows. To do so, you must configure Docker to use Windows containers first.
+To migrate applications built with .NET framework version 4.5 or later, on Microsoft Windows to cross-platform .NET 8.0, you must install the CLI for use with Docker on Windows. To do so, you must configure Docker to use Windows containers first.
 
 .Prerequisites
 
diff --git a/docs/topics/mta-cli/proc_installing-cli-zip.adoc b/docs/topics/mta-cli/proc_installing-cli-zip.adoc
@@ -5,7 +5,7 @@
 [id="installing-cli-zip_{context}"]
 = Installing the CLI by using a .zip file
 
-You can install the {ProductFullName} command-line interface (CLI) by using the downloadable `.zip` file available at the link:https://developers.redhat.com/products/mta/download[official {ProductShortName} download page].
+You can install the {ProductFullName} command-line interface (CLI) by using the downloadable `.zip` file available on the link:https://developers.redhat.com/products/mta/download[official {ProductShortName} download page].
 
 
 .Prerequisites
@@ -22,7 +22,7 @@ NOTE: This prerequisite is not applicable for the containerless mode. For more i
 
 .Procedure
 
-. Navigate to the link:{DevDownloadPageURL}[{ProductShortName} download page] and download one of the following operating system specific CLI file or the `src` file:
+. Navigate to the link:{DevDownloadPageURL}[{ProductShortName} download page] and download one of the following operating system-specific CLI files or the `src` file:
 +
 * {ProductShortNameLower}-{ProductVersion}-cli-linux.zip
 * {ProductShortNameLower}-{ProductVersion}-cli-macos.zip
@@ -33,4 +33,4 @@ NOTE: This prerequisite is not applicable for the containerless mode. For more i
 
 . Move the `mta-cli` binary to your `$PATH` variable.
 +
-NOTE: You can place the `mta-cli` binary in any folder that is included into the `$PATH` variable. Alternatively, you can add a folder that contains `mta-cli` to `$PATH`. This way, you do not need to specify a full path when using the CLI.
+NOTE: You can place the `mta-cli` binary in any folder that is included in the `$PATH` variable. Alternatively, you can add a folder that contains `mta-cli` to `$PATH`. This way, you do not need to specify a full path when using the CLI.
diff --git a/docs/topics/mta-cli/proc_installing-mta-disconnected-environment.adoc b/docs/topics/mta-cli/proc_installing-mta-disconnected-environment.adoc
@@ -13,11 +13,11 @@ When your system is in a disconnected environment, you can install the {ProductF
 
 IMPORTANT: The following procedure applies only to container mode.
 
-NOTE: The analysis output in the disconnected environment usually results in less incidents because a dependency analysis does not run accurately without access to Maven.
+NOTE: The analysis output in the disconnected environment usually results in fewer incidents because a dependency analysis does not run accurately without access to Maven.
 
 .Prerequisites
 
-* You downloaded the required {ProductShortName} CLI binary from {ProductName} Red Hat Developer page.
+* You downloaded the required {ProductShortName} CLI binary from the link:https://developers.redhat.com/products/mta/download[{ProductName} Red Hat Developer page].
 * You installed the Podman tool on your system.
 * For the analysis of Java applications, you enabled container runtime usage by setting the `--run-local` flag to `false`: 
 +
@@ -46,7 +46,7 @@ $ *podman login registry.redhat.io*
 $ *mta-cli analyze*
 ....
 +
-IMPORTANT: This command only pulls the required images. For example, if you  run a command that requires Java images, a .NET image will not be pulled.
+IMPORTANT: This command only pulls the required images. For example, if you run a command that requires Java images, a .NET image will not be pulled.
 
 .. Display the image list:
 +
diff --git a/docs/topics/mta-cli/ref_analysis-report-sections.adoc b/docs/topics/mta-cli/ref_analysis-report-sections.adoc
@@ -16,11 +16,11 @@ include::../snippets/technology-preview-admonition.adoc[]
 [options="header"]
 |====
 |Section|Description
-|Dashboard|An overview of the incidents and total story points sorted by category.
+|Dashboard|An overview of the incidents and total story points, sorted by category.
 |Issues|A concise summary of all issues and their details that require attention.
 |Dependencies|All Java-packaged dependencies found within the application. 
 |Technologies|All embedded libraries grouped by functionality. Use this report to display the technologies used in each application. 
-|Insights|Information about a violation generated by a rule with zero effort. 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. Insights contain the information about the technologies used in the application and their usage in the code.
+|Insights|Information about a violation generated by a rule with zero effort. Issues are generated by general rules, whereas string tags are generated by the tagging rules. String tags indicate the presence of a technology but do not show the code location. Insights contain information about the technologies used in the application and their usage in the code.
 
 Insights do not impact the migration. 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. 		
 
diff --git a/docs/topics/mta-cli/ref_assets-generation-example.adoc b/docs/topics/mta-cli/ref_assets-generation-example.adoc
@@ -75,7 +75,7 @@ $ *mta-cli generate helm \
 --input discover.yaml --output-dir newDir*
 ----
 
-. Check the contents of the Dockerfile the `newDir` directory:
+. Check the contents of the Dockerfile in the `newDir` directory:
 +
 [subs="+quotes"]
 ----
diff --git a/docs/topics/mta-cli/ref_discover-generate-command-options.adoc b/docs/topics/mta-cli/ref_discover-generate-command-options.adoc
@@ -19,7 +19,7 @@ a|Display details for different command arguments.
 
 
 a|`--list-platforms`
-a|List supported platforms for the discovery process.
+a|List the supported platforms for the discovery process.
 
 
 .3+a|`discover cloud-foundry`
diff --git a/docs/topics/mta-cli/ref_mta-cli-analyze-flags.adoc b/docs/topics/mta-cli/ref_mta-cli-analyze-flags.adoc
@@ -16,7 +16,7 @@ The following are the options that you can use together with the `mta-cli analyz
 |`--context-lines` (int)|A number of lines of source code to include in the output for each incident. The default is 100.
 |`--dependency-folders` (stringArray)|A directory for dependencies.
 |`--enable-default-rulesets` (bool)|Run default rulesets with analysis. The default is `true`.
-|`--help`|Display the available flags for `analyze` command.
+|`--help`|Display the available flags for the `analyze` command.
 |`--http-proxy` (string)|An HTTP proxy string URL.
 |`--https-proxy` (string)|An HTTPS proxy string URL.
 |`--incident-selector` (string) a|An expression to select incidents based on custom variables, for example:
@@ -32,7 +32,7 @@ The following are the options that you can use together with the `mta-cli analyz
 | `--list-providers` |List available supported providers.
 |`--list-sources`|List rules for available migration sources.
 |`--list-targets`|List rules for available migration targets.
-|`--maven-settings` (string)|A path to the custom maven settings file to use.
+|`--maven-settings` (string)|A path to the custom Maven settings file to use.
 |`--mode` (string) a|An analysis mode. Must be set to either of the following values:
 
 * `full` (default)
diff --git a/docs/topics/mta-cli/ref_openrewrite-command-options.adoc b/docs/topics/mta-cli/ref_openrewrite-command-options.adoc
@@ -13,9 +13,9 @@ The following are the options that you can use together with the `mta-cli transf
 |Option|Description
 |`--goal` (string)|A target goal. The default is `"dryRun"`.
 |`--help`|Display all `mta-cli transform openrewrite` command options. 
-|`--input` (string)|A path to application source code directory.
+|`--input` (string)|A path to the application source code directory.
 |`--list-targets`|List all available OpenRewrite recipes.
-|`-maven-settings` (string)|A path to a custom maven settings file.
+|`-maven-settings` (string)|A path to a custom Maven settings file.
 |`--target` (string)|A target OpenRewrite recipe.
 |`--log-level uint32`|A log level. The default is `4`.
 |`--no-cleanup`|Do not clean up temporary resources.

Original file line number	Diff line number	Diff line change
`@@ -19,7 +19,7 @@ You can generate the discovery manifest for the Cloud Foundry (CF) application b`
`19`	`19`
`20`	`20`	. Open the terminal application and navigate to the `<{ProductShortName}_HOME>/` directory.
`21`	`21`
`22`		`-. List supported platforms for the discovery process:`
	`22`	`+. List the supported platforms for the discovery process:`
`23`	`23`	`+`
`24`	`24`	`[subs="+quotes"]`
`25`	`25`	`----`
Original file line number	Diff line number	Diff line change
`@@ -13,11 +13,11 @@ When your system is in a disconnected environment, you can install the {ProductF`
`13`	`13`
`14`	`14`	`IMPORTANT: The following procedure applies only to container mode.`
`15`	`15`
`16`		`-NOTE: The analysis output in the disconnected environment usually results in less incidents because a dependency analysis does not run accurately without access to Maven.`
	`16`	`+NOTE: The analysis output in the disconnected environment usually results in fewer incidents because a dependency analysis does not run accurately without access to Maven.`
`17`	`17`
`18`	`18`	`.Prerequisites`
`19`	`19`
`20`		`-* You downloaded the required {ProductShortName} CLI binary from {ProductName} Red Hat Developer page.`
	`20`	`+* You downloaded the required {ProductShortName} CLI binary from the link:https://developers.redhat.com/products/mta/download[{ProductName} Red Hat Developer page].`
`21`	`21`	`* You installed the Podman tool on your system.`
`22`	`22`	* For the analysis of Java applications, you enabled container runtime usage by setting the `--run-local` flag to `false`:
`23`	`23`	`+`
`@@ -46,7 +46,7 @@ $ podman login registry.redhat.io`
`46`	`46`	`$ mta-cli analyze`
`47`	`47`	`....`
`48`	`48`	`+`
`49`		`-IMPORTANT: This command only pulls the required images. For example, if you run a command that requires Java images, a .NET image will not be pulled.`
	`49`	`+IMPORTANT: This command only pulls the required images. For example, if you run a command that requires Java images, a .NET image will not be pulled.`
`50`	`50`
`51`	`51`	`.. Display the image list:`
`52`	`52`	`+`
Original file line number	Diff line number	Diff line change
`@@ -75,7 +75,7 @@ $ *mta-cli generate helm \`
`75`	`75`	`--input discover.yaml --output-dir newDir*`
`76`	`76`	`----`
`77`	`77`
`78`		-. Check the contents of the Dockerfile the `newDir` directory:
	`78`	+. Check the contents of the Dockerfile in the `newDir` directory:
`79`	`79`	`+`
`80`	`80`	`[subs="+quotes"]`
`81`	`81`	`----`