Add missing sections and commands for Windows and Linux/macOS

Author: brunoborges

articles/migrate/appcat/java-preview.md

@@ -150,11 +150,13 @@ On Windows, this is `%USERPROFILE%/.appcat` and on Linux/Mac, this is `$HOME/.ap
 Add the `.appcat` folder to your PATH environment variable so you can run the tool from any folder in the terminal.
 
 # [Linux / macOS](#tab/linux)
+
 ```bash
 mv /path/to/extracted/azure-migrate-appcat-for-java-cli-<OS>-<architecture>-<release-version>-preview/ $HOME/.appcat
 ```
 
 # [Windows](#tab/windows)
+
 ```cmd
 move /path/to/extracted/azure-migrate-appcat-for-java-cli-<OS>-<architecture>-<release-version>-preview/ %USERPROFILE%/.appcat
 ```
@@ -186,41 +188,53 @@ The **analyze** subcommand allows you to run source code and binary analysis.
 To analyze application source code, run the following command:
 
 # [Linux / macOS](#tab/linux)
+
 ```bash
 ./appcat analyze --input=<path/to/source/code> --output=<path/to/output/dir> --target=azure-appservice --overwrite
 ```
 
 # [Windows](#tab/windows)
+
 ```cmd
 .\appcat.exe analyze --input=<path/to/source/code> --output=<path/to/output/dir> --target=azure-appservice --overwrite
 ```
 
+---
+
 The **--input** flag must point to a source code directory or a binary file, and **--output** must point to a directory to store the analysis results.
 
 For more information on the analyze flags, run the following command:
 
 # [Linux / macOS](#tab/linux)
+
 ```bash
 ./appcat analyze --help
 ```
 
 # [Windows](#tab/windows)
+
 ```cmd
 .\appcat.exe analyze --help
 ```
 
+---
+
 To check the available targets for AppCAT, run the following command:
 
 # [Linux / macOS](#tab/linux)
+
 ```bash
 ./appcat analyze --list-targets
 ```
 
 # [Windows](#tab/windows)
+
 ```cmd
 .\appcat.exe analyze --list-targets
 ```
 
+---
+
 With the above command, you should see the following output:
 
 ```
@@ -242,35 +256,43 @@ AppCAT is designed to analyze a single application per command execution, but if
 To analyze multiple applications, run the following command:
 
 # [Linux / macOS](#tab/linux)
+
 ```bash
 ./appcat analyze --bulk --input=<path/to/source/A> --output=<path/to/output/ABC> --target=<targetname>
 ./appcat analyze --bulk --input=<path/to/source/B> --output=<path/to/output/ABC> --target=<targetname>
 ./appcat analyze --bulk --input=<path/to/source/C> --output=<path/to/output/ABC> --target=<targetname>
 ```
 
 # [Windows](#tab/windows)
+
 ```cmd
 .\appcat.exe analyze --bulk --input=<path/to/source/A> --output=<path/to/output/ABC> --target=<targetname>
 .\appcat.exe analyze --bulk --input=<path/to/source/B> --output=<path/to/output/ABC> --target=<targetname>
 .\appcat.exe analyze --bulk --input=<path/to/source/C> --output=<path/to/output/ABC> --target=<targetname>
 ```
 
+---
+
 #### Transform Subcommand
 
 The **transform** subcommand allows you to convert the previous `appcat` XML rules used in the 6.x version into the new YAML format used by this version 7.x.
 
 To transform rules, run the following command:
 
 # [Linux / macOS](#tab/linux)
+
 ```bash
 ./appcat transform rules --input=<path/to/xmlrules> --output=<path/to/output/dir>
 ```
 
 # [Windows](#tab/windows)
+
 ```cmd
 .\appcat.exe transform rules --input=<path/to/xmlrules> --output=<path/to/output/dir>
 ```
 
+---
+
 The **--input** flag should point to a file or directory containing XML rules, and the **--output** flag should point to the output directory for the converted YAML rules.
 
 ### Samples
@@ -289,27 +311,35 @@ In the **samples** directory, you will find several scripts to run different typ
 Depending on your operating system, run the appropriate script. For example,
 
 # [Linux / macOS](#tab/linux)
+
 ```bash
 ./samples/run-assessment
 ```
 
 # [Windows](#tab/windows)
+
 ```cmd
 .\samples\run-assessment.bat
 ```
 
+---
+
 The reports will be automatically generated and launched. You can find the reports under:
 
 # [Linux / macOS](#tab/linux)
+
 ```bash
 ../samples/report-*
 ```
 
 # [Windows](#tab/windows)
+
 ```cmd
 ..\samples\report-*
 ```
 
+---
+
 ### Summary of the analysis
 
 The landing page of the report lists all the technologies that are used in the application. The dashboard provides a summary of the analysis, including the number of transformation incidents, the incidents categories, or the story points.