More modifications from the SME review

Author: Mariya Pershina

assemblies/cli-guide/assembly_analyzing-applications-mta-cli.adoc

@@ -11,7 +11,7 @@ endif::[]
 ifdef::context[]
 [id="analyzing-applications-mta-cli_{context}"]
 endif::[]
-= Analyzing Java applications with {ProductShortName} CLI
+= Analyzing Java applications with {ProductShortName} command-line interface
 
 :context: analyzing-applications-mta-cli
 

assemblies/cli-guide/assembly_analyzing-nonjava-applications.adoc

@@ -11,7 +11,7 @@ endif::[]
 ifdef::context[]
 [id="analyzing-nonjava-applications_{context}"]
 endif::[]
-= Analyzing applications written in languages other than Java
+= Analyzing applications written in languages other than Java with {ProductShortName} command-line interface
 
 :context: analyzing-nonjava-applications
 

assemblies/cli-guide/assembly_generating-assets.adoc

@@ -17,23 +17,20 @@ endif::[]
 
 Starting from {ProductShortName} version 7.3.0, you can use the `discover` and `generate` commands in containerless mode to automatically generate the manifests needed to deploy a Cloud Foundry (CF) application in the {ocp-short}: 
 
-* The `discover` command generates the discovery manifest in the YAML format from the CF application manifest. The discovery manifest preserves the specifications found in the CF manifest that define the metadata, runtime, and platform configurations.
-* The `generate` command generates the deployment manifest for {ocp} deployments by using the discovery manifest. The deployment manifest is generated by using a templating engine, such as Helm, that converts the discovery manifest into a Kubernetes-native format. You can also use this command to generate non-Kubernetes manifests, such as a Dockerfile or a configuration file.
+* Use the `discover` command to generate the discovery manifest in the YAML format from the CF application manifest. The discovery manifest preserves the specifications found in the CF manifest that define the metadata, runtime, and platform configurations.
+* Use the `generate` command to generate the deployment manifest for {ocp} deployments by using the discovery manifest. The deployment manifest is generated by using a templating engine, such as Helm, that converts the discovery manifest into a Kubernetes-native format. You can also use this command to generate non-Kubernetes manifests, such as a Dockerfile or a configuration file.
+
+:FeatureName: Generating platform assets for application deployment
+include::topics/snippets/developer-preview-admonition.adoc[]
+
+.Benefits of generating deployment assets
 
 Generating deployment assets has the following benefits:
 
 * Generating the Kubernetes and non-Kubernetes deployment manifests.   
 * Generating deployment manifests by using familiar template engines, for example, Helm, that are widely used for Kubernetes deployments.
 * Adhering to Kubernetes best practices when preparing the deployment manifest by using Helm templates.
 
-:FeatureName: Generating platform assets for application deployment
-include::topics/snippets/developer-preview-admonition.adoc[]
-
-.Prerequisites
-
-* You have Cloud Foundry (v3) as a source platform.
-* You have {ocp-short} as a target platform. 
-* You have {ProductShortName} {CLIName} version 7.3.0 installed.
 
 
 include::topics/mta-cli/proc_generating-discovery-manifest.adoc[leveloffset=+1]

assemblies/cli-guide/assembly_installing-mta-cli.adoc

@@ -11,7 +11,7 @@ endif::[]
 ifdef::context[]
 [id="installing-mta-cli_{context}"]
 endif::[]
-= Installing MTA CLI
+= Installing {ProductShortName} command-line interface
 
 :context: installing-mta-cli
 
@@ -21,9 +21,9 @@ NOTE: You can also install the CLI for use with Docker on Windows. Note, however
 
 include::topics/mta-cli/proc_installing-cli-zip.adoc[leveloffset=+1]
 
-include::topics/mta-cli/proc_installing-cli-for-docker.adoc[leveloffset=+1]
+include::topics/mta-cli/proc_installing-mta-disconnected-environment.adoc[leveloffset=+1]
 
-//NEEDS TO BE REWRITTEN YET include::topics/mta-cli/installing-mta-disconnected-environment.adoc[leveloffset=+2]
+include::topics/mta-cli/proc_installing-cli-for-docker.adoc[leveloffset=+1]
 
 
 ifdef::parent-context-of-installing-mta-cli[:context: {parent-context-of-installing-mta-cli}]

assemblies/cli-guide/assembly_performing-transformation.adoc

@@ -11,7 +11,7 @@ endif::[]
 ifdef::context[]
 [id="performing-transformation_{context}"]
 endif::[]
-= Performing a transformation with the {ProductShortName} CLI
+= Performing a transformation with the {ProductShortName} command-line interface
 
 
 :context: performing-transformation
@@ -22,14 +22,18 @@ You can use transformation to perform the following actions:
 * Convert XML rules to YAML rules by using the `transform rules` command.
 
 IMPORTANT: Performing transformation requires the container runtime to be configured. 
-
+ 
 
 include::topics/mta-cli/proc_transforming-application-source-code.adoc[leveloffset=+1]
 
 include::topics/mta-cli/ref_available-openrewrite-recipes.adoc[leveloffset=+1]
 
+include::topics/mta-cli/ref_openrewrite-command-options.adoc[leveloffset=+1]
+
 include::topics/mta-cli/proc_converting-xml-to-yaml.adoc[leveloffset=+1]
 
+include::topics/mta-cli/ref_rules-command-options.adoc[leveloffset=+1]
+
 ifdef::parent-context-of-performing-transformation[:context: {parent-context-of-performing-transformation}]
 ifndef::parent-context-of-performing-transformation[:!context:]
 

assemblies/cli-guide/assembly_reviewing-analysis-reports.adoc

@@ -11,22 +11,15 @@ endif::[]
 ifdef::context[]
 [id="reviewing-analysis-reports_{context}"]
 endif::[]
-= Reviewing analysis reports
+= Reviewing an analysis report
 
 :context: reviewing-analysis-reports
 
-When you run an application analysis, the {ProductFullName} CLI generates an analysis report in the output directory that you specify by using the `--output` argument in the `mta-cli analyze` command.
-
-The output directory contains the following files and subdirectories: 	
-
-* analysis.log
-* dependencies.yaml
-* output.yaml
-* shim.log
-* static-report
-* static-report.log
+After analyzing an application, you can access an analysis report to check the details of the entire application migration effort.
 
+include::topics/mta-cli/proc_accessing-analysis-report.adoc[leveloffset=+1]
 
+include::topics/mta-cli/ref_analysis-report-sections.adoc[leveloffset=+1]
 
 
 ifdef::parent-context-of-reviewing-analysis-reports[:context: {parent-context-of-reviewing-analysis-reports}]

docs/cli-guide/assemblies

@@ -0,0 +1 @@
+../../assemblies/

docs/cli-guide/master.adoc

@@ -24,12 +24,9 @@ include::assemblies/cli-guide/assembly_analyzing-applications-mta-cli.adoc[level
 
 include::assemblies/cli-guide/assembly_analyzing-nonjava-applications.adoc[leveloffset=+1]
 
-include::assemblies/cli-guide/assembly_performing-transformation.adoc[leveloffset=+1]
+include::assemblies/cli-guide/assembly_reviewing-analysis-reports.adoc[leveloffset=+1]
 
-//REWRITE FIRST (very much outdated)include::topics/access-report.adoc[leveloffset=+2]
-//include::topics/mta-review-reports.adoc[leveloffset=+1]
-// include::topics/csv-export.adoc[leveloffset=+1]
-// include::topics/mavenize.adoc[leveloffset=+1]
+include::assemblies/cli-guide/assembly_performing-transformation.adoc[leveloffset=+1]
 
 include::assemblies/cli-guide/assembly_generating-assets.adoc[leveloffset=+1]
 

docs/topics/access-report.adoc

@@ -0,0 +1,20 @@
+:_newdoc-version: 2.18.5
+:_template-generated: 2025-06-18
+:_mod-docs-content-type: PROCEDURE
+
+[id="accessing-analysis-report_{context}"]
+= Accessing an analysis report
+
+When you run an application analysis, a report is generated in the output directory that you specify by using the `--output` argument in the command line.
+
+.Procedure
+
+* Copy the path of the `index.html` file from the analysis output and paste it in a browser of your choice:
++
+[subs="+quotes"]
+----
+Report created: _<output_report_directory>_/index.html
+          	Access it at this URL: file:///_<output_report_directory>_/index.html
+----
++
+Alternatively, press *Ctrl* and click on the path of the `index.html` file.