MTA-4662: Update containerless CLI docs

Signed-off-by: A.Arnold <[email protected]>

Author: anarnold97

docs/topics/installing-cli-tool.adoc

@@ -11,6 +11,7 @@ You can install the {CLINameTitle} on Linux, Windows, or macOS operating systems
 
 [IMPORTANT]
 ====
+
 Starting from {ProductShortName} 7.2.0, you can run the application analysis for Java applications in the containerless mode.
 
 The containerless mode is set by default and is used automatically if all requirements are met. For more information, see xref:running-the-containerless-mta-cli_cli-guide[Running the containerless CLI].
@@ -231,17 +232,16 @@ Server: Docker Desktop 4.32.0 (157355)
 ----
 PS C:\Users\<your_user_name>> $env:PODMAN_BIN="C:\Windows\system32\docker.exe"
 ----
-
 . Set the `DOTNET_PROVIDER_IMG` environment variable to use the upstream `dotnet-external-provider`:
 +
 [source,powershell]
 ----
-PS C:\Users\<your_user_name>> $env:DOTNET_PROVIDER_IMG="quay.io/konveyor/dotnet-external-provider:v0.5.0"
+PS C:\Users\<your_user_name>> $env:DOTNET_PROVIDER_IMG="registry.redhat.io/mta/mta-dotnet-external-provider-rhel9:7.1.0"
 ----
-
 . Set the `RUNNER_IMG` environment variable to use the upstream image:
 +
 [source,powershell]
 ----
-PS C:\Users\<your_user_name>> $env:RUNNER_IMG="quay.io/konveyor/kantra:v0.5.0"
+# double-check reference
+PS C:\Users\<your_user_name>> $env:RUNNER_IMG="registry.redhat.io/mta/mta-cli-rhel9:7.1.0"
 ----

docs/topics/proc_running-the-containerless-mta-cli.adoc

@@ -26,26 +26,46 @@ In {ProductShortName} 7.2.0 and later, containerless CLI is a default mode. To e
 * You have the `JAVA_HOME` environmental variable set.
 * You have the `JVM_MAX_MEM` system variable set.
 +
-NOTE: If you do not set `JVM_MAX_MEM`, the analysis might hang.
+[NOTE]
+====
+If you do not set `JVM_MAX_MEM`, the analysis might hang.
+====
 
-.Procedure
+.Procedure for Linux
 
-. Move the installed {ProductShortName} CLI `.zip` file to your `$PATH`:
+After unpacking the whole zip file to `~/.kantra`, add that path to the `$PATH` variable.
+
+[NOTE]
+====
+Moving the `mta-cli` binary to `/usr/bin` requires root privileges, whereas adding that path to `$PATH` variable does not require root privileges.
+====
+
+. To extract the dependency zip file to `~/.kantra`, run:
 +
 [source,terminal,subs="attributes+"]
 ----
-$ mv <mta_cli_zip>/<os>-kantra /usr/bin
+unzip $HOME/mta-cli.<os>.<arch>.zip -d $HOME/.kantra
 ----
 
-. Move the requirements to the `.kantra` directory:
+. For example, to move the `mta-cli` binary to `/usr/bin` using `sudo`, run:
 +
 [source,terminal,subs="attributes+"]
 ----
-$ mv $HOME/kantra.<os>.<arch> $HOME/.kantra
+sudo mv ~/.kantra/mta-cli /usr/bin/
 ----
+
+. For example, to add to the `$PATH` variable, run:
 +
-NOTE: The CLI can run with the requirements moved to the directory from which you run an analysis. During the analysis, the CLI checks for the requirements in this directory first, and if it does not find the requirements, it searches for them in the `$HOME/.kantra` directory.
+[source,terminal,subs="attributes+"]
+----
+export PATH=$HOME/.kantra:$PATH
+----
 
++
+[NOTE]
+====
+The CLI can run with the requirements moved to the directory from which you run an analysis. During the analysis, the CLI checks for the requirements in this directory first, and if it does not find the requirements, it searches for them in the `$HOME/.kantra` directory.
+====
 
 . Optional: Display all `mta-cli analyze` command options:
 +
@@ -73,4 +93,3 @@ The command arguments represent the following:
 .Additional resources
 
 * xref:installing-downloadable-cli-zip_cli-guide[Installing the CLI .zip file]
-