windup · HagayVider1 · Apr 21, 2024 · May 6, 2024 · May 6, 2024 · May 7, 2024
diff --git a/.gitignore b/.gitignore
@@ -4,4 +4,9 @@ html/
 */build/*
 Gemfile.lock
 */master.html
-.idea/
+.idea/
-.idea/
+.idea/ 
-.idea/
+.idea/ 
+.gitignore
+.DS_Store
+assets/.DS_Store
+docs/.DS_Store
+docs/topics/.DS_Store
diff --git a/docs/topics/about-cli-guide.adoc b/docs/topics/about-cli-guide.adoc
@@ -6,4 +6,4 @@
 [id="about-cli-guide_{context}"]
 = About the {UserCLIBookName}
 
-This guide is for engineers, consultants, and others who want to use the {ProductName} ({ProductShortName}) to migrate Java applications or other components. It describes how to install and run the {CLIName}, review the generated reports, and take advantage of additional features.
+This guide is for programmers, engineers, consultants, and others who want to use the {ProductName} ({ProductShortName}) to migrate Java and Go applications, or other software components. It describes how to install and run the {CLIName}, review the generated reports, and take advantage of additional features.
diff --git a/docs/topics/about-cli.adoc b/docs/topics/about-cli.adoc
@@ -7,7 +7,7 @@
 [id="about-cli_{context}"]
 = The {ProductShortName} {CLINameTitle}
 
-The {CLIName} is a command-line tool in the {ProductName} that you can use to assess and prioritize migration and modernization efforts for applications. It provides numerous reports that highlight the analysis without using the other tools. The {CLIName} includes a wide array of customization options. By using the {CLIName}, you can tune {ProductShortName} analysis options or integrate with external automation tools.
+The {ProductShortName} {CLIName} is a command-line tool that you can use to assess and prioritize migration and modernization efforts for applications. It provides numerous reports that highlight the analysis without using the other tools. The {CLIName} includes a wide array of customization options, enabling you to tune the {ProductShortName} analysis options or integrate with external automation tools.
 
 ifndef::cli-guide[]
 For more information about using the {CLIName}, see link:{ProductDocUserGuideURL}[_{UserCLIBookName}_].

diff --git a/docs/topics/installing-cli-tool.adoc b/docs/topics/installing-cli-tool.adoc
@@ -7,8 +7,7 @@
 [id="installing-cli-tool_{context}"]
 = Installing the {CLINameTitle}
 
-You can install the {CLINameTitle} on Linux, Windows, or macOS operating systems.
-
+You can install the {ProductShortName} {CLINameTitle} on Linux, Windows, or macOS operating systems.
 
 .Prerequisites
 
@@ -24,24 +23,51 @@ Podman provides a command line interface (CLI) familiar to anyone who has used t
 For more information on installing and using Podman, see link:https://podman.io/docs/installation[Podman installation instructions].
 ====
 
+Installation options
+
+This section offers two options to install {ProductShortName} {CLINameTitle}:
+
+* Downloading a `.zip` file and installing it using a command line
+* Running PodMan on your computer and installing using PodMan commands
+
++
+[WARNING]
+====
+Although installation using Podman is possible, downloading and installing the `.zip` file is the preferred installation.
+====
+
+
 [id="installing-downloadable-cli-zip_{context}"]
 == Installing the {CLINameTitle} `.zip` file
 
 .Procedure
 
 To install using the downloadable `.zip` file:
 
-. Navigate to the link:{DevDownloadPageURL}[{ProductShortName} Download page] and download the OS specific CLI file or the `src` file:
+. Navigate to the link:https://developers.redhat.com/products/mta/download[{ProductShortName} Download page] and download the OS specific CLI file or the `mta-{ProductVersion}-cli-src` file:
 +
-* {ProductShortNameLower}-{ProductVersion}-cli-linux.zip
-* {ProductShortNameLower}-{ProductVersion}-cli-macos.zip
-* {ProductShortNameLower}-{ProductVersion}-cli-windows.zip
-* {ProductShortNameLower}-{ProductVersion}-cli-src.zip
+* Migration Toolkit {CLINameTitle} -{CLINameTitle} for Linux x86_64
+* Migration Toolkit {CLINameTitle} -{CLINameTitle} for Linux aarch64
+* Migration Toolkit {CLINameTitle} -{CLINameTitle} for macOS x86_64
+* Migration Toolkit {CLINameTitle} -{CLINameTitle} for macOS aarch64
+* Migration Toolkit {CLINameTitle} -{CLINameTitle} for Windows x86_64
+* Migration Toolkit {CLINameTitle} -{CLINameTitle} for Windows aarch64
+* Migration Toolkit {CLINameTitle} -{CLINameTitle} for {ProductShortName} source Code
+
++
+[NOTE]
+====
+Do not download and install the {ProductShortName} source Code file if your computer runs one of the above operating systems.
+====
 
 . Extract the `.zip` file to a directory of your choice. The `.zip` file extracts a single binary, called *mta-cli*.
 +
 When you encounter `<{ProductShortName}_HOME>` in this guide, replace it with the actual path to your {ProductShortName} installation.
 
+. Copy or save the `mta-cli` binary, or `mta-cli.exe` in Windows, to a known directory.
++
+Continue to xref:cli-run_cli-guide[Running the CLI] to run the CLI command.
+
 
 [id="installing-using-podman_{context}"]
 == Installing the {CLINameTitle} using Podman
@@ -60,21 +86,25 @@ To install using `podman pull`:
 [source,terminal]
 ----
 podman login registry.redhat.io
+----
+
+. Enter your `Username` and `Password`.
++
+[source,terminal]
+---- 
 Username: <username>
 Password: <***********>
 ----
-. Issue:
++
+If your `Usernam` and `Password` are correct, the terminal line should show `Login Succeeded!`.
+
+. Copy the binary `PATH` for system-wide use.
 +
 [source,terminal]
 ----
 podman cp $(podman create registry.redhat.com/mta-toolkit/mta-mta-cli-rhel9:{ProductVersion}):/usr/local/bin/mta-cli ./
 ----
 +
 This command will copy the binary `PATH` for system-wide use.
-+
-[WARNING]
-====
-Although installation using Podman is possible, downloading installing the `.zip` file is the preferred installation.
-====
 
 
diff --git a/docs/topics/migration-paths.adoc b/docs/topics/migration-paths.adoc
@@ -26,6 +26,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |Spring Boot in Red Hat Runtimes
 |Quarkus 
 |Open Liberty
+|Azure App Service
 
 |Oracle WebLogic Server
 |{icon-check}
@@ -36,6 +37,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
 
 |IBM WebSphere Application Server
 |{icon-check}
@@ -46,6 +48,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |{icon-check}
+|-
 
 |JBoss EAP 4
 |{icon-x} footnoteref:[note2,Although {ProductShortName} does not currently provide rules for this migration path, Red Hat Consulting can assist with migration from any source platform to JBoss EAP 7.]
@@ -55,6 +58,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
 
 |JBoss EAP 5
 |{icon-check}
@@ -65,6 +69,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
 
 |JBoss EAP 6
 |{icon-check}
@@ -75,6 +80,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
 
 |JBoss EAP 7
 |{icon-check}
@@ -85,6 +91,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |{icon-check}
 |-
+|-
 
 |Thorntail
 |{icon-check} footnoteref:[note3,Requires JBoss Enterprise Application Platform expansion pack 2 (EAP XP 2)]
@@ -95,6 +102,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
 
 |Oracle JDK
 |-
@@ -105,6 +113,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
 
 |Camel 2
 |-
@@ -115,6 +124,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
 
 |Spring Boot
 |-
@@ -125,6 +135,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |{icon-check}
 |{icon-check}
 |-
+|-
 
 |Any Java application
 |-
@@ -135,6 +146,7 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
 
 |Any Java EE application
 |-
@@ -145,4 +157,16 @@ The {ProductName} ({ProductShortName}) supports the following migrations:
 |-
 |-
 |-
+|-
+
+|Azure
+|-
+|-
+|-
+|-
+|-
+|-
+|-
+|-
+|{icon-check}
 |===
diff --git a/docs/topics/mta-what-is-the-toolkit.adoc b/docs/topics/mta-what-is-the-toolkit.adoc
@@ -17,16 +17,19 @@
 
 {ProductName} ({ProductShortName}) accelerates large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface.
 
-{ProductShortName} uses an extensive default questionnaire as the basis for assessing your applications, or you can create your own custom questionnaire, enabling you to estimate the difficulty, time, and other resources needed to prepare an application for containerization. You can use the results of an assessment as the basis for discussions between stakeholders to determine which applications are good candidates for containerization, which require significant work first, and which are not suitable for containerization.
+{ProductShortName} uses an extensive default questionnaire as the basis to assess your applications. You can also create your own custom questionnaires, enabling you to estimate the difficulty, time, and other resources needed to prepare an application for containerization. The results of your assessment can be the basis for discussions between stakeholders to determine the status of application migration:
+* Applications that are good candidates for containerization
+* Applications that require significant work before being modernized
+* Applications that are not suitable for containerization
 
-{ProductShortName} analyzes applications by applying one or more rulesets to each application considered to determine which specific lines of that application must be modified before it can be modernized.
+{ProductShortName} analyzes applications by applying one or more rulesets to each application considered, determining which specific lines of that application require modification before it can be migrated or modernized.
 
-{ProductShortName} examines application artifacts, including project source directories and application archives, and then produces an HTML report highlighting areas needing changes.
+{ProductShortName} examines application artifacts, including project source directories and application archives, and then produces an HTML report highlighting areas that need changes.
 
 
 [discrete]
 == How does the {ProductName} simplify migration?
 
-The {ProductName} looks for common resources and known trouble spots when migrating applications. It provides a high-level view of the technologies used by the application.
+The {ProductName} analyzes the application by looking for common resources and known trouble spots when migrating applications. It provides a high-level view of the technologies used by the application.
 
-{ProductShortName} generates a detailed report evaluating a migration or modernization path. This report can help you to estimate the effort required for large-scale projects and to reduce the work involved.
+After analyzing the application, {ProductShortName} generates a detailed report evaluating a migration or modernization path. This report can help you to estimate the effort required for large-scale projects, and to reduce the work involved.