migtools · anarnold97 · Jun 10, 2026 · Jun 10, 2026
diff --git a/docs/topics/developer-lightspeed/con_dl-context.adoc b/docs/topics/developer-lightspeed/con_dl-context.adoc
@@ -18,7 +18,7 @@ The context is a combination of the source code, the issue description, and solv
 +
 * Solved examples constitute code changes from other migrations and a pattern of resolution for an issue that can be used in future. A solved example is created when a Migrator accepts a resolution in a previous analysis that results in updated code or an unfamiliar issue in a legacy application that the Migrator manually fixed. Solved examples are stored in the Solution Server.
 +
-More instances of solved examples for an issue enhance the context and improve the success metrics of rules that trigger the issue. Higher the success metrics of an issue, greater the confidence level associated with the accepted resolutions for that issue in previous analyses.
+More instances of solved examples for an issue enhance the context and improve the success metrics of rules that trigger the issue. The higher the success metrics of an issue, the greater the confidence level associated with the accepted resolutions for that issue in previous analyses.
 
 * (Optional) If you enable the Solution Server, it extracts a pattern of resolution, called the migration hint, that can be used by the LLM to generate a more accurate fix suggestion in a future analysis.
 +

diff --git a/docs/topics/developer-lightspeed/proc_configuring-llm-podman-desktop.adoc b/docs/topics/developer-lightspeed/proc_configuring-llm-podman-desktop.adoc
@@ -8,7 +8,7 @@
 [role="_abstract"]
 The Podman AI lab extension enables you to use an open-source model from a curated list of models and use it locally in your system. 
 
-The code fix suggestions generated by a model depends on the model's capabilities. Models deployed through the Podman AI Lab were found to be insufficient for the complexity of code changes required to fix issues discovered by {ProductShortName}. You must not use such models in a production environment.
+The code fix suggestions generated by a model depend on the model's capabilities. Models deployed through the Podman AI Lab were found to be insufficient for the complexity of code changes required to fix issues discovered by {ProductShortName}. You must not use such models in a production environment.
 
 .Prerequisites
 

diff --git a/docs/topics/developer-lightspeed/ref_dl-benefits.adoc b/docs/topics/developer-lightspeed/ref_dl-benefits.adoc
@@ -13,7 +13,7 @@
 {mta-dl-full} offers options to use large language models of your choice, LLM configuration control, and a platform engineering approach to standardize AI-assisted refactoring efforts for large codebases in your organization.
 
 * *Model agnostic* - {mta-dl-plugin} follows a "Bring Your Own Model" approach, allowing your organization to use a preferred LLM.
-* *Iterative refinement* - {mta-dl-plugin} can include an agent that iterates through the source code to run a series of automated analyses that resolves both the code base and diagnostic issues.
+* *Iterative refinement* - {mta-dl-plugin} can include an agent that iterates through the source code to run a series of automated analyses that resolve both the code base and diagnostic issues.
 * *Contextual code generation* - By leveraging AI for static code analysis, {mta-dl-plugin} breaks down complex problems into more manageable ones, providing the LLM with focused context to generate meaningful results. This helps overcome the limited context size of LLMs when dealing with large codebases.
 * *No fine tuning* - You also do not need to fine tune your model with a suitable data set for analysis which leaves you free to use and switch LLM models to respond to your requirements.
 * *Learning and Improvement* - As more parts of a codebase are migrated with {mta-dl-plugin}, it can use RAG to learn from the available data and provide better recommendations in subsequent application analysis.

diff --git a/docs/topics/mta-install/con_roles-personas-users-permissions.adoc b/docs/topics/mta-install/con_roles-personas-users-permissions.adoc
@@ -12,8 +12,8 @@ A user can have more than one role. Each role must correspond to a specific pers
 
 * The `tackle-admin` role corresponds to the Administrator persona. The Administrator has all permissions that Architects and Migrators have. Administrators can also create application-wide configuration parameters that other users can consume but cannot change or view, for example, Git credentials or Maven `settings.xml` files.
 
-* The `tackle-architect` role corresponds to the Architect persona. An Architects is a technical lead for the migration project. Architects can run assessments and can create and modify applications and information related to the applications. Architects cannot modify or delete sensitive information, but can consume such information. For example, Architects can associate an existing set of credentials to the repository of a specific application. 	
+* The `tackle-architect` role corresponds to the Architect persona. An Architect is a technical lead for the migration project. Architects can run assessments and can create and modify applications and information related to the applications. Architects cannot modify or delete sensitive information, but can consume such information. For example, architects can associate an existing set of credentials to the repository of a specific application.
 
 * The `tackle-migrator` role corresponds to the Migrator persona. A Migrator can analyze applications. However, the Migrator cannot create, modify, or delete the applications. 
 
-{ProductShortName} has two views, *Administration* and *Migration*. Only Administrator can access the *Administration* view. Architects and Migrators cannot see or access the *Administration* view. Administrators can perform all actions supported by the *Migration* view. Architects and Migrators can see all elements of the *Migration* view. However, whether Architects and Migrators can perform actions in the *Migration* view depends on the permissions granted to their role.
+{ProductShortName} has two views, *Administration* and *Migration*. Only an Administrator can access the *Administration* view. Architects and Migrators cannot see or access the *Administration* view. Administrators can perform all actions supported by the *Migration* view. Architects and Migrators can see all elements of the *Migration* view. However, whether Architects and Migrators can perform actions in the *Migration* view depends on the permissions granted to their role.
diff --git a/docs/topics/mta-install/proc_creating-mta-instance.adoc b/docs/topics/mta-install/proc_creating-mta-instance.adoc
@@ -13,7 +13,7 @@ To use the {ProductShortName} UI for assessing and analyzing your applications,
 .Prerequisites
 
 * You installed the {ProductShortName} Operator on your system. For more information, see xref:installing-mta-operator_installing-mta-ui[Installing the {ProductShortName} Operator].
-* You environment has 4 vCPUs, 8 GB RAM, and 40 GB persistent storage.
+* Your environment has 4 vCPUs, 8 GB RAM, and 40 GB persistent storage.
 * Your environment uses Red Hat OpenShift (cloud service or self-hosted), version 4.13–4.15.
 * You logged in as a user with `cluster-admin` permissions.
 

diff --git a/docs/topics/mta-install/proc_installing-cli-zip.adoc b/docs/topics/mta-install/proc_installing-cli-zip.adoc
@@ -43,7 +43,7 @@ pass:[<!-- vale RedHat.Spelling = YES -->]
 . Move the `mta-cli` binary to your `$PATH` variable.
 
 +
-NOTE: You can place the `mta-cli` binary in any folder that included in the `$PATH` variable. You can also add a folder that contains `mta-cli` to `$PATH`. This way, you do not need to specify a full path when using the CLI.
+NOTE: You can place the `mta-cli` binary in any folder that is included in the `$PATH` variable. You can also add a folder that contains `mta-cli` to `$PATH`. This way, you do not need to specify a full path when using the CLI.
 
 
 [role="_additional-resources"]

diff --git a/docs/topics/mta-ui/con_assessment-module-features.adoc b/docs/topics/mta-ui/con_assessment-module-features.adoc
@@ -27,7 +27,7 @@ You can import and export assessment questionnaires. You can also design custom
 NOTE: You can customize and save the default questionnaire.
 
 Archetypes::
-You can use archetypes to assess a group applications with similar characteristics. Each archetype has a shared taxonomy of tags, stakeholders, and stakeholder groups. All applications inherit assessment and review from their assigned archetypes.
+You can use archetypes to assess a group of applications with similar characteristics. Each archetype has a shared taxonomy of tags, stakeholders, and stakeholder groups. All applications inherit assessment and review from their assigned archetypes.
 
 
 [role="_additional-resources"]

diff --git a/docs/topics/mta-ui/con_mta-default-questionnaire.adoc b/docs/topics/mta-ui/con_mta-default-questionnaire.adoc
@@ -525,7 +525,7 @@ sections:
             mitigation: ''
           - order: 2
             text: >-
-              Application fails when a soutbound dependency is unavailable and
+              Application fails when a southbound dependency is unavailable and
               does not recover automatically
             risk: red
             rationale: ''
@@ -902,7 +902,7 @@ sections:
       - order: 1
         text: How is the application tested?
         explanation: >-
-          Is the application is tested? Is it easy to test (example: automated
+          Is the application tested? Is it easy to test (example: automated
           testing)? Is it tested in production?
         answers:
           - order: 0