diff --git a/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md b/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md
index 00060b2145..f263474207 100644
--- a/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md
+++ b/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md
@@ -77,7 +77,7 @@ Camunda 8 supports the following binding types:
           <li><p>Using the <code>versionTag</code> binding option ensures that the right version of the target resource is always used, regardless of future deployments, by pinning the dependency to a specific version.</p></li>
           <li><p>The option is ideal for managing external or shared dependencies.</p></li>
         </ul>
-        <p><u>Heads-Up</u>:</p>
+        <p><strong>Caution:</strong></p>
         <ul>
           <li>
             <p>
diff --git a/docs/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md b/docs/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md
index 1e2fae3456..3fbf3e0bdc 100644
--- a/docs/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md
+++ b/docs/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md
@@ -104,7 +104,7 @@ to transform the variables passed to the job worker, or to customize how the var
 
 ### XML representation
 
-A business rule task with a called decision that does not specify the binding type (`latest` will be used implicitly):
+A business rule task with a called decision that does not specify the binding type (`latest` is used implicitly):
 
 ```xml
 <bpmn:businessRuleTask id="determine-box-size" name="Determine shipping box size">
diff --git a/docs/components/modeler/bpmn/call-activities/call-activities.md b/docs/components/modeler/bpmn/call-activities/call-activities.md
index 67fdbbb8db..e316fdcce1 100644
--- a/docs/components/modeler/bpmn/call-activities/call-activities.md
+++ b/docs/components/modeler/bpmn/call-activities/call-activities.md
@@ -60,7 +60,7 @@ By disabling this attribute, variables existing at higher scopes are no longer c
 
 ### XML representation
 
-A call activity with static process id, propagation of all child variables turned on, and no explicit binding type (`latest` will be used implicitly):
+A call activity with static process id, propagation of all child variables turned on, and no explicit binding type (`latest` is used implicitly):
 
 ```xml
 <bpmn:callActivity id="Call_Activity" name="Call Process A">
diff --git a/docs/components/modeler/bpmn/user-tasks/user-tasks.md b/docs/components/modeler/bpmn/user-tasks/user-tasks.md
index 58a146e6f7..489c120cef 100644
--- a/docs/components/modeler/bpmn/user-tasks/user-tasks.md
+++ b/docs/components/modeler/bpmn/user-tasks/user-tasks.md
@@ -187,7 +187,7 @@ Zeebe user task-specific features are not available to those user tasks.
 
 #### Camunda Form
 
-A user task with a linked Camunda Form that does not specify the binding type (`latest` will be used implicitly) as well as an assignment definition and a task schedule:
+A user task with a linked Camunda Form that does not specify the binding type (`latest` is used implicitly) as well as an assignment definition and a task schedule:
 
 ```xml
 <bpmn:userTask id="configure" name="Configure">
diff --git a/docs/components/modeler/web-modeler/advanced-modeling/business-rule-task-linking.md b/docs/components/modeler/web-modeler/advanced-modeling/business-rule-task-linking.md
index bdd2c4e2c0..eb4b848769 100644
--- a/docs/components/modeler/web-modeler/advanced-modeling/business-rule-task-linking.md
+++ b/docs/components/modeler/web-modeler/advanced-modeling/business-rule-task-linking.md
@@ -6,11 +6,11 @@ description: Use one of the following approaches to link the DMN decision to be
 
 import PropertiesPanelImg from './img/brt_properties-panel.png'
 
-You can use one of the following approaches to link the DMN decision to be called by a [business rule task](/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md).
+You can use either of the following approaches to link the DMN decision to be called by a [business rule task](/components/modeler/bpmn/business-rule-tasks/business-rule-tasks.md).
 
 ## Using the link button
 
-1. Select a business rule task from the canvas and a link icon will appear at the bottom right.
+1. Select a business rule task from the canvas. A link icon appears at the bottom right.
 2. Click the link icon and choose any decision from the same project.
 3. Click **Link** to complete the linking process. In the properties panel, the value **DMN decision** is chosen for the **Implementation** property, and the Decision ID of the decision you chose to link is automatically copied to the **Called decision** section.
 
@@ -24,10 +24,10 @@ For business rule tasks that are already linked, clicking on the link icon opens
 
 ## Using the properties panel
 
-You may also enter the Decision ID directly in the **Called decision** section in the properties panel after selecting **DMN decision** for the **Implementation**.
+You can also enter the Decision ID directly in the **Called decision** section in the properties panel after selecting **DMN decision** for the **Implementation**.
 
-There you can also select a different **Binding** for the called decision (learn more about the different options in [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md)).
-If you select **version tag**, you need to enter the actual version tag to be used.
+- **Binding**: You can also select a different Binding for the called decision. See [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md).
+- **Version tag**: If you select **version tag** for the Binding, you must enter the actual version tag to use.
 
 <p><img src={PropertiesPanelImg} alt="called decision section in properties panel" style={{width: 430}} /></p>
 
diff --git a/docs/components/modeler/web-modeler/advanced-modeling/call-activity-linking.md b/docs/components/modeler/web-modeler/advanced-modeling/call-activity-linking.md
index 8b55ee3ea0..1055533019 100644
--- a/docs/components/modeler/web-modeler/advanced-modeling/call-activity-linking.md
+++ b/docs/components/modeler/web-modeler/advanced-modeling/call-activity-linking.md
@@ -10,7 +10,7 @@ You can use one of the following approaches to link the process to be called by
 
 ## Using the link button
 
-1. Select a call activity task from the canvas and a link button will appear at the bottom right.
+1. Select a call activity task from the canvas. A link button appears at the bottom right.
 2. Click on the button and choose any diagram from the same project.
 3. Click the **Link** button to complete the linking process. The process ID of the diagram you chose to link is automatically copied to the **Called element** section in the properties panel.
 
@@ -22,10 +22,10 @@ For call activities that are already linked, clicking on the link button opens a
 
 ## Using the properties panel
 
-You may also enter the process ID directly in the **Called element** section in the properties panel.
+You can also enter the process ID directly in the **Called element** section in the properties panel.
 
-There you can also select a different **Binding** for the called process (learn more about the different options in [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md)).
-If you select **version tag**, you need to enter the actual version tag to be used.
+- **Binding**: You can also select a different Binding for the called decision. See [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md).
+- **Version tag**: If you select **version tag** for the Binding, you must enter the actual version tag to use.
 
 <p><img src={PropertiesPanelImg} alt="called element section in properties panel" style={{width: 430}} /></p>
 
diff --git a/docs/components/modeler/web-modeler/advanced-modeling/form-linking.md b/docs/components/modeler/web-modeler/advanced-modeling/form-linking.md
index 2b3d7be43b..3fea0b463b 100644
--- a/docs/components/modeler/web-modeler/advanced-modeling/form-linking.md
+++ b/docs/components/modeler/web-modeler/advanced-modeling/form-linking.md
@@ -38,14 +38,14 @@ Using the properties panel, you can connect a form to a user task/start event vi
 
 ### Camunda Form (linked)
 
-Choosing **Camunda Form (linked)** as type and entering the form ID directly yields the same result as [using the link button on the modeling canvas](#using-the-link-button).
+Choosing **Camunda Form (linked)** as the type and entering the form ID directly, produces the same result as [using the link button on the modeling canvas](#using-the-link-button).
 
-You can also select a different **Binding** for the linked form (learn more about the different options in [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md)).
-If you select **version tag**, you need to enter the actual version tag to be used.
+- **Binding**: You can also select a different Binding for the linked form. See [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md).
+- **Version tag**: If you select **version tag** for the Binding, you must enter the actual version tag to use.
 
 <p><img src={PropertiesPanelImg} style={{width: 430}} alt="form section in properties panel" /></p>
 
-Using a linked form is the recommended approach as it allows you to benefit from the form automatically being deployed along with the diagram.
+Using a linked form is the recommended approach as it allows you to benefit from the form automatically being deployed with the diagram.
 This means when deploying a BPMN diagram, Web Modeler will always deploy the latest version of all linked forms along with the diagram, so you do not have to manually re-link forms or [copy & paste JSON configuration](#camunda-form-embedded) when making changes.
 
 :::danger
diff --git a/docs/components/modeler/web-modeler/run-or-publish-your-process.md b/docs/components/modeler/web-modeler/run-or-publish-your-process.md
index 3f681ec87d..759a9c4345 100644
--- a/docs/components/modeler/web-modeler/run-or-publish-your-process.md
+++ b/docs/components/modeler/web-modeler/run-or-publish-your-process.md
@@ -41,7 +41,7 @@ To deploy, click **Deploy** in the upper right corner of the modeling screen:
 
 - Make sure your process is free of errors, otherwise it can't be deployed. Use the [problems panel to detect and fix errors](./fix-problems-in-your-diagram.md).
 - Make sure all dependent files are deployed first, such as DMN diagrams, forms, or called processes. You can use the [link tool](./advanced-modeling/call-activity-linking.md) to drill-down into linked resources and deploy them.
-  If you're using [`versionTag` binding](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md) for a linked resource, make sure it is deployed with the correct version tag.
+  If you are using [`versionTag` binding](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md) for a linked resource, make sure it is deployed with the correct version tag.
   :::tip
   Consider using a [process application](process-applications.md) that allows you to deploy a process and all dependent files together in a single bundle.
   :::