style(formatting): grammatical review

camunda · Jun 20, 2024 · 78682e9 · 78682e9
1 parent d9888e6
commit 78682e9
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/components/connectors/use-connectors/inbound.md b/docs/components/connectors/use-connectors/inbound.md
@@ -12,12 +12,12 @@ Review our [list of existing inbound Connectors](/components/connectors/out-of-t
 
 ## Creating the Connector event
 
-Inbound Connectors are modeled as **catch events** in BPMN. Connectors that create a new process instance are modeled as **start events**, and Connectors that send messages to an already running process instance are modeled as **intermediate catch events**. It is also possible to create new processes by using a **message start events** and to use Inbound Connects via **boundary events**
+Inbound Connectors are modeled as **catch events** in BPMN. Connectors that create a new process instance are modeled as **start events**, and Connectors that send messages to an already running process instance are modeled as **intermediate catch events**. It is also possible to create new processes by using a **message start event** and to use inbound Connectors via **boundary events**.
 
 :::important
-If **idempotency** is a concern for the process creation and reprocessing of messages should never lead to a duplicate process instance creation, it is recommended to use the **message start event** element for an Inbound Connector as it relies on publishing a message.
+If **idempotency** is a concern for the process creation and reprocessing of messages should never lead to a duplicate process instance creation, use the **message start event** element for an inbound Connector as it relies on publishing a message.
 
-**Message start events** support the **Message ID** property that allows to specify a unique value that will be used by Zeebe to [guarantee uniqueness](/components/concepts/messages.md#message-uniqueness) in case other messages are published that use the same **Message ID**.
+**Message start events** support the **Message ID** property that allows you to specify a unique value that will be used by Zeebe to [guarantee uniqueness](/components/concepts/messages.md#message-uniqueness) in case other messages are published that use the same **Message ID**.
 :::
 
 When you **deploy** such a BPMN diagram with an inbound Connector, the Connector becomes ready to receive incoming requests. The outcome depends on the Connector type: