Merge branch 'main' into mta-6471-dotnet-provider

Author: Pkylas007

.github/styles/MTA/SessionID.yml

@@ -0,0 +1,8 @@
+# Merge blocker: do not use "SessionID" or "Session ID" in MTA documentation.
+extends: existence
+message: "Do not use '%s' in documentation. Use the approved term instead."
+level: error
+ignorecase: true
+tokens:
+  - SessionID
+  - Session ID

assemblies/intellij-plugin-guide/assembly_resolving-issues.adoc

@@ -19,7 +19,7 @@ endif::[]
 You can resolve issues by doing one of the following:
 
 * Using a _Quick Fix_ to fix a code snippet that has a hint
-* Editing the code of a file that appears in a classification
+* Editing the code of a file that is displayed in a classification
 
 include::topics/mta-intellij-plugin/proc_quick-fix.adoc[leveloffset=+1]
 

assemblies/rules-development-guide/assembly_rule-yaml-conditions.adoc

@@ -22,7 +22,7 @@ Additionally, {ProductShortName} provides a built-in provider with abilities suc
 
 Currently, {ProductShortName} supports the following providers:
 
-* Builtin
+* builtin
 * Java 
 * Csharp
 * External providers (for `Python`, `Go`, and `Node.js` applications) initialized by the generic provider binary

assemblies/ui-guide/assembly_analyzing-applications.adoc

@@ -10,11 +10,12 @@ endif::[]
 ifdef::context[]
 [id="analyzing-applications_{context}"]
 endif::[]
-= Analyzing an application with MTA
+= Analyzing applications with {ProductShortName}
 
 :context: analyzing-applications
 
-You can use the {ProductFullName} user interface (UI) to configure and run an application analysis. The analysis determines which specific lines in the application must be modified before the application can be migrated or modernized. 			
+[role="_abstract"]
+To identify potential risks and modernization requirements, run an analysis on your applications in the {ProductFullName} user interface (UI). 
 
 include::topics/mta-ui/proc_configuring-and-running-an-application-analysis.adoc[leveloffset=+1]
 

assemblies/ui-guide/assembly_assessing-applications.adoc

@@ -10,11 +10,12 @@ endif::[]
 ifdef::context[]
 [id="assessing-applications_{context}"]
 endif::[]
-= Assessing applications with the MTA
+= Assessing applications with {ProductShortName}
 
 :context: assessing-applications
 
-You can use the {ProductFullName} user interface (UI) to assess applications. When assessing applications, {ProductShortName} estimates the risks and costs involved in preparing applications for containerization, including time, personnel, and other factors. You can use the results of an assessment for discussions between stakeholders to determine whether applications are suitable for containerization.
+[role="_abstract"]
+Estimate the risks and costs involved in preparing applications for containerization, including time, personnel, and other factors, by assessing applications with the {ProductFullName} user interface (UI). You can use the results of an assessment for discussions between stakeholders to determine whether applications are suitable for containerization.
 
 
 include::topics/mta-ui/con_assessment-module-features.adoc[leveloffset=+1]

assemblies/ui-guide/assembly_assessment-questionnaires.adoc

@@ -14,9 +14,8 @@ endif::[]
 
 :context: assessment-questionnaires
 
-The {ProductFullName} uses an assessment questionnaire, either xref:mta-default-questionnaire_assessment-questionnaires[default] or xref:mta-custom-questionnaire_assessment-questionnaires[custom], to assess the risks involved in containerizing an application. 
-
-The assessment report provides information about applications and risks associated with migration. The report also generates an adoption plan informed by the prioritization, business criticality, and dependencies of the applications submitted for assessment.
+[role="_abstract"]
+To determine the readiness of your portfolio for modernization, use assessment questionnaires to provide the {ProductFullName} user interface (UI) with the details required for the migration process. The {ProductFullName} uses either xref:mta-default-questionnaire_assessment-questionnaires[default] or xref:mta-custom-questionnaire_assessment-questionnaires[custom] assessment questionnaire.
 
 include::topics/mta-ui/con_mta-default-questionnaire.adoc[leveloffset=+1]
 

…onsole/assembly_asset-generation-ui.adoc …-guide/assembly_asset-generation-ui.adocdocs/topics/web-console/assembly_asset-generation-ui.adoc renamed to assemblies/ui-guide/assembly_asset-generation-ui.adoc docs/topics/web-console/assembly_asset-generation-ui.adoc renamed to assemblies/ui-guide/assembly_asset-generation-ui.adoc

@@ -15,18 +15,18 @@ endif::[]
 
 :context: asset-generation-ui
 
-[role=_abstract]
-Starting with 8.0.0, asset generation in {ProductShortName} {WebName} allows you to create different  assets (manifests) required to deploy applications from Cloud Foundry (CF) instances to {ocp-full} or Kubernetes. 
+[role="_abstract"]
+To create different assets (manifests) required to deploy applications from Cloud Foundry (CF) instances to {ocp-full} or Kubernetes, use asset generation in {ProductShortName} {WebName}.
 
-To generate assets, you must become familiar with the following entities:
+To generate assets, familiarize yourself with the following entities:
 
 * Archetypes - Archetypes contain one or more criteria tags to identify technologies such as EAP 6. An archetype helps you to classify applications based on technologies common to them. For asset generation, you can plan your migration paths by archetypes because you configure the other asset generation entities  in the archetype (for example, target profiles that contain the generators). 
 
 * Generators - A generator takes a templating engine, such as Helm, along with a set of templates as input configuration. Generators use the templates that are defined for a target platform and a migration path to generate deployment assets. When you run an asset generation process, the generator parses the application discovery manifest to create deployment assets.
 +
 For example, the migration path for an EAP 6 application is EAP 8 and the target platform is Kubernetes. A generator can generate the required assets to migrate the EAP 6 application to EAP 8 that is to be deployed on Kubernetes. The assets are generated by parsing the discovery manifest of the EAP 6 application.
 
-* Target profiles - A target profile represents the target platform to which you want to migrate. It contains a seqeuence of generators. Through target profiles, you can run more than one generator, with each generator creating assets for a specific migration path. Thus, a target profile enables you to generate assets for multiple migration path-target platform combinations at the same time for a given Archetype. 
+* Target profiles - A target profile represents the target platform to which you want to migrate. It contains a sequence of generators. Through target profiles, you can run more than one generator, with each generator creating assets for a specific migration path. Thus, a target profile enables you to generate assets for multiple migration path-target platform combinations at the same time for a given archetype. 
 +
 For example, if you want to create assets to migrate an EAP 6 application as an OpenJDK 21 application _and_ as an EAP 8 application in {ocp-short} (target platform), you can achieve this through a target profile that has two generators, one for each migration path.
 
@@ -41,13 +41,13 @@ The asset repository is where you find the generated assets for deployment in th
 
 You can reuse generators in different archetypes.
 
-include::proc_configuring-generators.adoc[leveloffset=+1]
+include::topics/mta-ui/proc_configuring-generators.adoc[leveloffset=+1]
 
-include::proc_configuring-target-profiles.adoc[leveloffset=+1]
+include::topics/mta-ui/proc_configuring-target-profiles.adoc[leveloffset=+1]
 
-include::proc_configuring-asset-repository.adoc[leveloffset=+1]
+include::topics/mta-ui/proc_configuring-asset-repository.adoc[leveloffset=+1]
 
-include::proc_generating-deployment-assets.adoc[leveloffset=+1]
+include::topics/mta-ui/proc_generating-deployment-assets.adoc[leveloffset=+1]
 
 ifdef::parent-context-of-generating-assets[:context: {parent-context-of-asset-generation-ui}]
 ifndef::parent-context-of-asset-generation-ui[:!context:]

assemblies/ui-guide/assembly_configuring-credentials.adoc

@@ -14,7 +14,10 @@ endif::[]
 
 :context: configuring-credentials
 
-You can set up the following credential types to configure the {ProductFullName} instance environment: 
+[role="_abstract"]
+To provide the {ProductFullName} instance environment with secure access to your private source code and repositories, configure credentials in the user interface (UI). 
+
+You can set up the following credential types to configure the {ProductShortName} instance environment: 
 
 * Source control 					
 * Maven settings file 					

assemblies/ui-guide/assembly_configuring-mta-instance-environment.adoc

@@ -14,7 +14,10 @@ endif::[]
 
 :context: configuring-mta-instance-environment
 
-You can configure the {ProductFullName} instance environment by setting up the following parameters: 		
+[role="_abstract"]
+To adjust migration projects to specific requirements, configure the {ProductFullName} instance environment.
+
+You can configure the {ProductShortName} instance environment by setting up the following parameters: 		
 
 * General	 				
 * Credentials					

assemblies/ui-guide/assembly_configuring-mta-instance.adoc

@@ -14,7 +14,11 @@ endif::[]
 
 :context: configuring-mta-instance
 
-If you are a project architect, you can configure the instance’s key parameters before migration. You can add and edit these parameters as needed. The following parameters define applications, individuals, teams, verticals, or areas within an organization affected or participating in the migration:
+
+[role="_abstract"]
+To adjust the {ProductFullName} to your needs, configure a {ProductShortName} instance. By configuring the instance, you ensure {ProductShortName} considers key parameters during the migration process and generates comprehensive modernization reports.
+
+If you are a project architect, you can configure the instance’s key parameters before migration. The following parameters define applications, individuals, teams, verticals, or areas within an organization affected or participating in the migration:
 
 * Stakeholders 					
 * Stakeholder groups