oops: fix angle brackets

camunda · Dec 16, 2024 · ec0337f · ec0337f
1 parent ba941eb
commit ec0337f
Show file tree

Hide file tree

Showing 6 changed files with 25 additions and 25 deletions.
diff --git a/docs/components/early-access/alpha/sap/odata-connector.md b/docs/components/early-access/alpha/sap/odata-connector.md
@@ -168,4 +168,4 @@ If the SAP OData Connector encounters an error, the boundary event will catch th
 
 - Ensure the connection from the Cloud Foundry environment via the destination to the SAP systems works. Using the [Terminal in Business Application Studio](https://community.sap.com/t5/technology-blogs-by-sap/how-to-check-the-connectivity-to-your-backend-system-in-business/ba-p/13479832) is a quick way to verify this.
 - Validate requests first in an API client before trying with the SAP OData Connector in Modeler. Then, copy over to the element template fields. This saves time and reduces potential error.
-- Any payload size \<= 2.5MB can be considered safe.
+- Any payload size &lt;= 2.5MB can be considered safe.
diff --git a/docs/components/modeler/desktop-modeler/telemetry/telemetry.md b/docs/components/modeler/desktop-modeler/telemetry/telemetry.md
@@ -54,8 +54,8 @@ These events include the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the case of a form, the payload also includes the `formFieldTypes`:
 
@@ -78,8 +78,8 @@ The `Deployment Event` and `Start Instance` have the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the event of an unsuccessful deployment, an `error` property will be present in the payload containing an error code.
 

diff --git a/...oned_docs/version-8.3/components/modeler/desktop-modeler/telemetry/telemetry.md b/...oned_docs/version-8.3/components/modeler/desktop-modeler/telemetry/telemetry.md
@@ -54,8 +54,8 @@ These events include the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 ### Deployment and start instance events
 
@@ -68,8 +68,8 @@ The `Deployment Event` and `Start Instance` have the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the event of an unsuccessful deployment, an `error` property will be present in the payload containing an error code.
 
@@ -82,7 +82,7 @@ If provided, as is the case when deploying to a Zeebe-based platform, the payloa
 If the target engine profile is set in the diagram, the payload will also contain it.
 
 ```json
- "executionPlatform": "\<target platform>"
+ "executionPlatform": "<target platform>"
 ```
 
 ### Tracked click events

diff --git a/...oned_docs/version-8.4/components/modeler/desktop-modeler/telemetry/telemetry.md b/...oned_docs/version-8.4/components/modeler/desktop-modeler/telemetry/telemetry.md
@@ -54,8 +54,8 @@ These events include the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the case of a form, the payload also includes the `formFieldTypes`:
 
@@ -78,8 +78,8 @@ The `Deployment Event` and `Start Instance` have the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the event of an unsuccessful deployment, an `error` property will be present in the payload containing an error code.
 
@@ -92,7 +92,7 @@ If provided, as is the case when deploying to a Zeebe-based platform, the payloa
 If the target engine profile is set in the diagram, the payload will also contain it.
 
 ```json
- "executionPlatform": "\<target platform>"
+ "executionPlatform": "<target platform>"
 ```
 
 ### Tracked click events

diff --git a/...oned_docs/version-8.5/components/modeler/desktop-modeler/telemetry/telemetry.md b/...oned_docs/version-8.5/components/modeler/desktop-modeler/telemetry/telemetry.md
@@ -54,8 +54,8 @@ These events include the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the case of a form, the payload also includes the `formFieldTypes`:
 
@@ -78,8 +78,8 @@ The `Deployment Event` and `Start Instance` have the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the event of an unsuccessful deployment, an `error` property will be present in the payload containing an error code.
 
@@ -92,7 +92,7 @@ If provided, as is the case when deploying to a Zeebe-based platform, the payloa
 If the target engine profile is set in the diagram, the payload will also contain it.
 
 ```json
- "executionPlatform": "\<target platform>"
+ "executionPlatform": "<target platform>"
 ```
 
 ### Tracked click events

diff --git a/...oned_docs/version-8.6/components/modeler/desktop-modeler/telemetry/telemetry.md b/...oned_docs/version-8.6/components/modeler/desktop-modeler/telemetry/telemetry.md
@@ -54,8 +54,8 @@ These events include the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the case of a form, the payload also includes the `formFieldTypes`:
 
@@ -78,8 +78,8 @@ The `Deployment Event` and `Start Instance` have the following properties:
 
 - `diagramType`: BPMN, DMN, or Form
 - Engine profile:
-  - `executionPlatform`: \<target platform\>
-  - `executionPlatformVersion`: \<target platform version\>
+  - `executionPlatform`: &lt;target platform\>
+  - `executionPlatformVersion`: &lt;target platform version\>
 
 In the event of an unsuccessful deployment, an `error` property will be present in the payload containing an error code.
 
@@ -92,7 +92,7 @@ If provided, as is the case when deploying to a Zeebe-based platform, the payloa
 If the target engine profile is set in the diagram, the payload will also contain it.
 
 ```json
- "executionPlatform": "\<target platform>"
+ "executionPlatform": "<target platform>"
 ```
 
 ### Tracked click events