resolve comments

docs/apis-tools/frontend-development/01-task-applications/03-task-application-architecture.md

@@ -6,7 +6,7 @@ description: "Understand and decide on the architecture of your task application
 
 A typical task application architecture consists of a task application frontend, a backend-for-frontend, and one or more data sources or services that contain business data relevant for the application users to perform their work. The backend implements Camunda Zeebe and Tasklist clients to retrieve and interact with tasks via Camunda APIs. For historical process instance data, Operate is also required.
 
-Depending on the user task implementation type (Job worker-based vs Camunda user task) you use in your processes, you need to run either the Tasklist or Zeebe client to run operations on task. Task, form, and variable retrieval happens via the API. Learn more about the differences of the task implementation types in the [migration guide for Camunda user tasks](/apis-tools/migration-manuals/migrate-to-camunda-user-tasks.md).
+Depending on the user task implementation type (job worker-based vs Camunda user task) you use in your processes, you need to run either the Tasklist or Zeebe client to run operations on tasks. Task, form, and variable retrieval happens via the API. Learn more about the differences of the task implementation types in the [migration guide for Camunda user tasks](/apis-tools/migration-manuals/migrate-to-camunda-user-tasks.md).
 
 :::tip
 Starting a new project? Use Camunda user tasks to simplify your implementation.
@@ -79,7 +79,7 @@ click ZeebeRest "../../../zeebe-api-rest/zeebe-api-rest-overview"
 
 Follow these resources to learn more about the individual components:
 
-- Learn how to use the [Camunda 8 API](/apis-tools/camunda-api-rest/specifications/assign-user-task.api.mdx) for task, variable, and form retrieval, and to run operations on job worker-based user tasks managed by Camunda, also known as Camunda user tasks.
+- Learn how to use the [Camunda 8 API](/apis-tools/camunda-api-rest/specifications/assign-user-task.api.mdx) for task, variable, and form retrieval, and to run operations on Camunda user tasks.
 - Familiarize yourself with the [Tasklist API](/apis-tools/tasklist-api-rest/tasklist-api-rest-overview.md) to run operations on Job worker-based user tasks.
 - Understand how to design, embed, and customize [forms](/apis-tools/frontend-development/03-forms/01-introduction-to-forms.md).
 - Understand how this architecture fits into the overall Camunda architecture with the [Java greenfield stack](/components/best-practices/architecture/deciding-about-your-stack.md).

docs/apis-tools/java-client/zeebe-process-test.md

@@ -8,7 +8,7 @@ processes. It will start a lightweight in-memory Zeebe engine and provide you wi
 verify your process behaves as expected.
 
 :::note
-As of 8.5.0, Zeebe Process Test does not support the new REST API and related features (e.g. Camunda user tasks).
+As of 8.5.0, Zeebe Process Test does not support the new REST API and related features (for example, Camunda user tasks).
 :::
 
 ## Prerequisites

docs/apis-tools/migration-manuals/migrate-to-camunda-user-tasks.md

@@ -16,7 +16,7 @@ import CamundaUserTaskSelectionImg from '../tasklist-api-rest/assets/img/camunda
 
 Camunda 8.5 introduced a new [user task](/components/modeler/bpmn/user-tasks/user-tasks.md) implementation type: Camunda user task.
 
-Camunda user tasks have several benefits, compared to Job worked-based user tasks. It includes:
+Camunda user tasks have several benefits compared to Job worked-based user tasks, including:
 
 - Running directly on the automation engine for high performance.
 - Removing dependencies and round trips to Tasklist.
@@ -36,7 +36,7 @@ With this in mind, you can migrate at your own pace. If you should migrate now o
 
 ### Task type differences
 
-Learn the differences between both task types and make an informed decision, and understand the new capabilities of Camunda user tasks. Refer to this table for important high-level differences of the two task types:
+To make an informed decision, you should understand the differences between both task types and the new capabilities of Camunda user tasks. Refer to this table for important high-level differences between the two task types:
 
 <table>
     <tr>

docs/apis-tools/zeebe-api-rest/tutorial.md

@@ -41,7 +41,7 @@ In this tutorial, we will execute arguments to assign and unassign a user to and
 ## Assign a Camunda user task (POST)
 
 :::note
-In this tutorial, you will capture a **Camunda user task** ID to assign and unassign users in this API. Camunda 8.5 introduced this new [user task](/components/modeler/bpmn/user-tasks/user-tasks.md) implementation type, and these Camunda user tasks are different from job worker-based user tasks. See more details on task type differences in the [migrating to Camunda user tasks documentation](/apis-tools/migration-manuals/migrate-to-camunda-user-tasks.md#task-type-differences).
+In this tutorial, you will capture a **Camunda user task** ID to assign and unassign users in this API. Camunda 8.5 introduced this new [user task](/components/modeler/bpmn/user-tasks/user-tasks.md) implementation type, and these Camunda user tasks are different from job worker-based user tasks. To learn more about task type differences, see [migrating to Camunda user tasks](/apis-tools/migration-manuals/migrate-to-camunda-user-tasks.md#task-type-differences).
 :::
 
 First, let's script an API call to assign a Camunda user task.
@@ -71,7 +71,7 @@ async function assignUser([userTaskKey, assignee]) {
 
 `const zeebeApiUrl = process.env.ZEEBE_BASE_URL`
 
-5. On the next line, script the API endpoint to assign a Camunda user task.:
+5. On the next line, script the API endpoint to assign a Camunda user task:
 
 ```javascript
 const url = `${ZeebeApiUrl}/user-tasks/${userTaskKey}/assignment`;

docs/components/concepts/process-instance-migration.md

@@ -370,8 +370,8 @@ The following limitations exist that may be supported in future versions:
   - An element that becomes nested in a newly added subprocess
   - An element that was nested in a subprocess is no longer nested in that subprocess
 - Mapping instructions cannot change the element type
-- Mapping instructions cannot change the task implementation, e.g. from a job worker user task to a job worker-based user task managed by Camunda, also known as a Camunda user task
-- The process instance must be in a wait state, i.e. waiting for an event or external input like job completion. It may not be taking a sequence flow or triggering an event while migrating the instance
+- Mapping instructions cannot change the task implementation, for example, from a job worker user task to a Camunda user task.
+- The process instance must be in a wait state, i.e. waiting for an event or external input like job completion. It may not be taking a sequence flow or triggering an event while migrating the instance.
 
 A full overview of error codes can be found in the migration command [RPC](/apis-tools/zeebe-api/gateway-service.md#migrateprocessinstance-rpc) or [REST](/apis-tools/camunda-api-rest/specifications/migrate-process-instance.api.mdx).
 

docs/components/modeler/web-modeler/advanced-modeling/form-linking.md

@@ -90,7 +90,7 @@ To correct any instances affected by this issue, we recommend the following step
 ### Camunda Form (embedded)
 
 :::info
-Embedded forms are supported only for Job Worker-based user tasks. They are not available for the [Camunda user task implementation type](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-implementation-types).
+Embedded forms are only supported for job worker-based user tasks. They are not available for the [Camunda user task implementation type](/components/modeler/bpmn/user-tasks/user-tasks.md#user-task-implementation-types).
 :::
 
 When choosing **Camunda Form (embedded)** as type you have the option to directly paste the form's JSON schema into the **Form JSON configuration** field of the properties panel.