style(formatting): grammatical tweaks

docs/components/modeler/bpmn/ad-hoc/ad-hoc.md

@@ -1,12 +1,12 @@
 ---
 id: ad-hoc
 title: "Ad-hoc"
-description: "The ad-hoc marker is only available for embedded subprocesses, so called ad-hoc subprocesses."
+description: "The ad-hoc marker is only available for embedded subprocesses, allowing more flexibility while executing inner elements."
 ---
 
-The ad-hoc marker (**~** a tilde character) is only available
-for [embedded subprocesses](../embedded-subprocesses/embedded-subprocesses.md), so called **ad-hoc subprocesses**.
-Compared to regular subprocesses, it allows more flexibility for executing the inner elements.
+The ad-hoc marker (represented by a **~** tilde character) is only available
+for [embedded subprocesses](../embedded-subprocesses/embedded-subprocesses.md), and are therefore called **ad-hoc subprocesses**.
+Compared to regular subprocesses, ad-hoc subprocesses allow more flexibility for executing inner elements.
 
 ![A demo process with an ad-hoc subprocess. Some elements inside the subprocess are active.](assets/ad-hoc-subprocess.png)
 
@@ -31,18 +31,18 @@ An ad-hoc subprocess has the following constraints:
 ## Activate an element
 
 An ad-hoc subprocess can define an expression `activeElementsCollection` that should return a
-[list](../../feel/language-guide/feel-data-types.md#list) of strings. Each string in the list should match to an id of
+[list](../../feel/language-guide/feel-data-types.md#list) of strings. Each string in the list should match to an ID of
 an inner element of the ad-hoc subprocess. Usually, the expression accesses a process instance variable that was
-created before and holds the list of element ids.
+created before and holds the list of element IDs.
 
 ![A process with an ad-hoc subprocess that shows how a variable is used to active the inner elements.](assets/ad-hoc-subprocess-activation.png)
 
 When a process instance reaches an ad-hoc subprocess, it evaluates the expression `activeElementsCollection` and
-activates all elements whose element ids are in the list.
+activates all elements whose element IDs are in the list.
 
-If the list is empty or the expression is not defined, no element is activated and the ad-hoc subprocess stays active.
+If the list is empty or the expression is not defined, no element is activated and the ad-hoc subprocess remains active.
 
-If the expression doesn't evaluate to a list of strings, or the list contains other values than inner element ids, the
+If the expression doesn't evaluate to a list of strings, or the list contains other values than inner element IDs, the
 process instance creates an incident.
 
 :::note
@@ -55,10 +55,10 @@ entering the subprocess.
 An ad-hoc subprocess can define input and output
 [variable mappings](../../../concepts/variables.md#inputoutput-variable-mappings).
 
-Input variable mappings are applied on activating the ad-hoc subprocess and before evaluating the expression
+**Input variable mappings** are applied on activating the ad-hoc subprocess and before evaluating the expression
 `activeElementsCollection`. They can be used to create local variables for the ad-hoc subprocess.
 
-Output variable mappings are applied on completing the ad-hoc subprocess. They can be used to propagate local variables
+**Output variable mappings** are applied on completing the ad-hoc subprocess. They can be used to propagate local variables
 from the ad-hoc subprocess into the process instance. By default, no local variables are propagated.
 
 ## Additional resources