Merge pull request #150 from migtools/MTA-4549_python-nodejs

[WIP] Mentions of Python/Node.js support for MTA 7.3.0

Author: raoradhika

docs/cli-guide/master-docinfo.xml

@@ -1,9 +1,9 @@
 <title>CLI Guide</title>
 <productname>{DocInfoProductName}</productname>
 <productnumber>{DocInfoProductNumber}</productnumber>
-<subtitle>Learn how to use the {ProductName} {CLIName} to migrate your applications.</subtitle>
+<subtitle>Using the {ProductName} command-line interface to migrate your applications</subtitle>
 <abstract>
-    <para>This guide describes how to use the {ProductName} {CLIName} to simplify migration of Java applications.</para>
+    <para>By using the {ProductFullName} command-line interface (CLI), you can assess and prioritize migration and modernization efforts for applications written in different languages. You can use the CLI to customize {ProductShortName} analysis options or integrate with external automation tools.</para>
 </abstract>
 <authorgroup>
     <orgname>Red Hat Customer Content Services</orgname>

docs/topics/mta-web-configuring-and-running-an-application-analysis.adoc

@@ -74,7 +74,7 @@ You can attach tags to the application manually instead of enabling automated ta
 +
 [NOTE]
 ====
-Analysis engines use standard rules for a comprehensive set of migration targets. However, if the target is not included, is a customized framework, or the application is written in a language that is not supported (for example, Node.js, Python), you can add custom rules by skipping the target selection in the Set Target tab and uploading custom rule files in the Custom Rules tab. Only custom rule files that are uploaded manually are validated.
+Analysis engines use standard rules for a comprehensive set of migration targets. However, if the target is not included, is a customized framework, or the application is written in a language that is not supported, for example, Ruby, you can add custom rules by skipping the target selection in the Set Target tab and uploading custom rule files in the Custom Rules tab. Only custom rule files that are uploaded manually are validated.
 ====
 
 . Click *Next*.

docs/topics/mta-web-creating-custom-migration-targets.adoc

@@ -19,6 +19,9 @@ By using ready-made custom migration targets, you can avoid configuring custom r
 . In the *Administration* view, click *Custom migration targets*.
 . Click *Create new*.
 . Enter the name and description of the target.
+. Click the *Provider* drop-down menu and choose the language provider.
++
+IMPORTANT: Support for the Python and Node.js language providers is available as a Technology Preview only.
 . In the *Image* section, upload an image file for the target's icon. The file can be in either the PNG or JPEG format, up to 1 MB. If you do not upload any file, a default icon is used.
 . In the *Custom rules* section, select either *Upload manually* or *Retrieve from a repository*:
 ** If you selected *Upload manually*, upload or drag and drop the required rule files from your local drive.