camunda · christinaausley · Sep 16, 2024
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
@@ -44,9 +44,9 @@ a `string`.
 
 The `bindingType` attribute determines which version of the called decision is evaluated:
 
-- `latest`: the latest deployed version at the moment the business rule task is activated.
-- `deployment`: the version that was deployed together with the currently running version of the process.
-- `versionTag`: the latest deployed version that is annotated with the version tag specified in the `versionTag` attribute.
+- `latest`: The latest deployed version at the moment the business rule task is activated.
+- `deployment`: The version that was deployed together with the currently running version of the process.
+- `versionTag`: The latest deployed version that is annotated with the version tag specified in the `versionTag` attribute.
 
 To learn more about choosing binding types, see [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md).
 

diff --git a/docs/components/modeler/bpmn/call-activities/call-activities.md b/docs/components/modeler/bpmn/call-activities/call-activities.md
@@ -20,9 +20,9 @@ Usually, the `processId` is defined as a [static value](/components/concepts/exp
 
 The `bindingType` attribute determines which version of the called process is instantiated:
 
-- `latest`: the latest deployed version at the moment the call activity is activated.
-- `deployment`: the version that was deployed together with the currently running version of the calling process.
-- `versionTag`: the latest deployed version that is annotated with the version tag specified in the `versionTag` attribute.
+- `latest`: The latest deployed version at the moment the call activity is activated.
+- `deployment`: The version that was deployed together with the currently running version of the calling process.
+- `versionTag`: The latest deployed version that is annotated with the version tag specified in the `versionTag` attribute.
 
 To learn more about choosing binding types, see [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md).
 

diff --git a/docs/components/modeler/bpmn/user-tasks/user-tasks.md b/docs/components/modeler/bpmn/user-tasks/user-tasks.md
@@ -121,9 +121,9 @@ Depending on your use case, two different types of form references can be used:
 
    The `bindingType` attribute determines which version of the linked form is used:
 
-   - `latest`: the latest deployed version at the moment the user task is activated.
-   - `deployment`: the version that was deployed together with the currently running version of the process.
-   - `versionTag`: the latest deployed version that is annotated with the version tag specified in the `versionTag` attribute.
+   - `latest`: The latest deployed version at the moment the user task is activated.
+   - `deployment`: The version that was deployed together with the currently running version of the process.
+   - `versionTag`: The latest deployed version that is annotated with the version tag specified in the `versionTag` attribute.
 
    To learn more about choosing binding types, see [Choosing the resource binding type](/docs/components/best-practices/modeling/choosing-the-resource-binding-type.md).
 

diff --git a/.../components/modeler/web-modeler/advanced-modeling/business-rule-task-linking.md b/.../components/modeler/web-modeler/advanced-modeling/business-rule-task-linking.md
@@ -26,8 +26,8 @@ For business rule tasks that are already linked, clicking on the link icon opens
 
 You can also enter the Decision ID directly in the **Called decision** section in the properties panel after selecting **DMN decision** for the **Implementation**.
 
-- **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.
+- **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
@@ -24,8 +24,8 @@ For call activities that are already linked, clicking on the link button opens a
 
 You can also enter the process ID directly in the **Called element** section in the properties panel.
 
-- **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.
+- **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
@@ -38,10 +38,10 @@ Using the properties panel, you can connect a form to a user task/start event vi
 
 ### Camunda Form (linked)
 
-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).
+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).
 
-- **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.
+- **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} style={{width: 430}} alt="form section in properties panel" /></p>
 

diff --git a/docs/reference/announcements.md b/docs/reference/announcements.md
@@ -52,7 +52,7 @@ The Zeebe Java client will not be developed further and will only receive bug fi
 
 ### Deprecation: Zeebe Go client & zbctl
 
-The Zeebe Go Client and zbctl will be officially deprecated with the 8.6 release as part of our efforts to streamline the Camunda 8 API experience. This client and CLI utility will not get released starting with Camunda 8.6, will no longer receive new features, and will be transitioned to a community-maintained status.
+The Zeebe Go Client and zbctl will be officially deprecated with the 8.6 release as part of our efforts to streamline the Camunda 8 API experience. This client and CLI utility will not be released with Camunda 8.6, will no longer receive new features, and will be transitioned to a community-maintained status.
 
 ### Camunda 8 SaaS - Required cluster update
 

diff --git a/docs/reference/dependencies.md b/docs/reference/dependencies.md
@@ -2066,7 +2066,7 @@ All of these libraries are required for core functionality.
 <TabItem value='modeler'>
 
 - **Dependencies:** You can find an up-to-date list of third party libraries used and their license terms in the [THIRD_PARTY_NOTICES](https://github.com/camunda/camunda-modeler/blob/master/THIRD_PARTY_NOTICES), located in the root of the source code repository. This file is also shipped with the application distribution as `THIRD_PARTY_NOTICES.camunda-modeler.txt`.
-- **Source code:** You can access the source code of the Desktop Modeler on [github.com/camunda/camunda-modeler](https://github.com/camunda/camunda-modeler)
+- **Source code:** Access the source code for Desktop Modeler at [github.com/camunda/camunda-modeler](https://github.com/camunda/camunda-modeler).
 
 </TabItem>
 
@@ -3082,8 +3082,8 @@ All of these libraries are required for core functionality.
 
 <TabItem value='connectors'>
 
-- **Dependencies:** You can find a SBOM CycloneDX file with an up-to-date list of third party libraries used and their licenses in the [release assets](https://github.com/camunda/connectors/releases) of each Connectors release.
-- **Source code:** You can access the source code of Connectors on [github.com/camunda/connectors](https://github.com/camunda/connectors)
+- **Dependencies:** Find a SBOM CycloneDX file with an up-to-date list of third party libraries used and their licenses in the [release assets](https://github.com/camunda/connectors/releases) of each Connectors release.
+- **Source code:** Access the source code for Connectors at [github.com/camunda/connectors](https://github.com/camunda/connectors).
 
 </TabItem>