Replace <= and >= with single chars (#4576)

* replace with ≤ * add both chars
camunda · Nov 6, 2024 · 3797185 · 3797185
1 parent ef400e0
commit 3797185
Show file tree

Hide file tree

Showing 41 changed files with 193 additions and 193 deletions.
diff --git a/docs/apis-tools/spring-zeebe-sdk/getting-started.md b/docs/apis-tools/spring-zeebe-sdk/getting-started.md
@@ -8,10 +8,10 @@ This project allows you to leverage Zeebe APIs ([gRPC](/apis-tools/zeebe-api/grp
 
 ## Version compatibility
 
-| Camunda Spring SDK version | JDK    | Camunda version | Bundled Spring Boot version |
-| -------------------------- | ------ | --------------- | --------------------------- |
-| 8.5.x                      | \>= 17 | 8.5.x           | 3.2.x                       |
-| 8.6.x                      | \>= 17 | 8.6.x           | 3.2.x                       |
+| Camunda Spring SDK version | JDK  | Camunda version | Bundled Spring Boot version |
+| -------------------------- | ---- | --------------- | --------------------------- |
+| 8.5.x                      | ≥ 17 | 8.5.x           | 3.2.x                       |
+| 8.6.x                      | ≥ 17 | 8.6.x           | 3.2.x                       |
 
 ## Add the Spring Zeebe SDK to your project
 

diff --git a/docs/guides/getting-started-orchestrate-microservices.md b/docs/guides/getting-started-orchestrate-microservices.md
@@ -32,7 +32,7 @@ You must have access to a Camunda 8 SaaS account.
 
 Additionally, you need the following:
 
-- Java >= 8
+- Java ≥ 8
 - Maven
 - IDE (IntelliJ, VSCode, or similar)
 - Download and unzip or clone the [repo](https://github.com/camunda/camunda-platform-tutorials), then `cd` into `camunda-platform-tutorials/orchestrate-microservices/worker-java`

diff --git a/docs/reference/notices.md b/docs/reference/notices.md
@@ -115,7 +115,7 @@ At this point, Camunda is not aware of any specific attack vector in Tasklist al
 
 #### How to determine if the installation is affected
 
-You are Tasklist version (8.0.3 >= version <= 8.0.7) or <= 8.1.2
+You are Tasklist version (8.0.3 ≥ version ≤ 8.0.7) or ≤ 8.1.2
 
 #### Solution
 
@@ -142,7 +142,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper
 
 #### How to determine if the installation is affected
 
-You are using Zeebe, Operate or Tasklist version <= 1.2.11 or <= 1.3.6
+You are using Zeebe, Operate or Tasklist version ≤ 1.2.11 or ≤ 1.3.6
 
 #### Solution
 
@@ -168,7 +168,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper
 
 #### How to determine if the installation is affected
 
-You are using Zeebe, Operate or Tasklist version <= 1.2.8 or <= 1.1.9
+You are using Zeebe, Operate or Tasklist version ≤ 1.2.8 or ≤ 1.1.9
 
 #### Solution
 
@@ -194,7 +194,7 @@ Specifically, IAM bundles log4j-api and log4j-to-slf4j. However, IAM does not bu
 
 #### How to determine if the installation is affected
 
-You are using IAM version <= 1.2.8
+You are using IAM version ≤ 1.2.8
 
 #### Solution
 
@@ -219,7 +219,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper
 
 #### How to determine if the installation is affected
 
-You are using Zeebe, Operate or Tasklist version <= 1.2.7 or <= 1.1.8
+You are using Zeebe, Operate or Tasklist version ≤ 1.2.7 or ≤ 1.1.8
 
 #### Solution
 
@@ -248,7 +248,7 @@ At this point, Camunda is not aware of any specific attack vector in IAM allowin
 
 #### How to determine if the installation is affected
 
-You are using IAM version <= 1.2.7
+You are using IAM version ≤ 1.2.7
 
 #### Solution
 
@@ -273,7 +273,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper
 
 #### How to determine if the installation is affected
 
-You are using Zeebe, Operate or Tasklist version <= 1.2.6 or <= 1.1.7
+You are using Zeebe, Operate or Tasklist version ≤ 1.2.6 or ≤ 1.1.7
 
 #### Solution
 
@@ -302,7 +302,7 @@ At this point, Camunda is not aware of any specific attack vector in IAM allowin
 
 #### How to determine if the installation is affected
 
-You are using IAM version <= 1.2.6
+You are using IAM version ≤ 1.2.6
 
 #### Solution
 
@@ -327,7 +327,7 @@ At this point, Camunda is not aware of any specific attack vector in Zeebe, Oper
 
 #### How to determine if the installation is affected
 
-You are using Zeebe, Operate or Tasklist version <= 1.2.5 or <= 1.1.6
+You are using Zeebe, Operate or Tasklist version ≤ 1.2.5 or ≤ 1.1.6
 
 #### Solution
 
@@ -357,7 +357,7 @@ Still, Camunda recommends applying fixes as mentioned in the Solution section be
 
 #### How to determine if the installation is affected
 
-You are using IAM version <= 1.2.5
+You are using IAM version ≤ 1.2.5
 
 #### Solution
 

diff --git a/docs/self-managed/operate-deployment/importer-and-archiver.md b/docs/self-managed/operate-deployment/importer-and-archiver.md
@@ -86,7 +86,7 @@ You can further parallelize archiver and/or importer within one node using the f
 | camunda.operate.importer.threadsCount | Number of threads in which data will be imported. | 3             |
 
 :::note
-Parallelization of import and archiving within one node will also happen based on Zeebe partitions, meaning only configurations with (number of nodes) \* (threadsCount) <= (total number of Zeebe partitions) will make sense. Too many threads and nodes will still work, but some of them will be idle.
+Parallelization of import and archiving within one node will also happen based on Zeebe partitions, meaning only configurations with (number of nodes) \* (threadsCount) ≤ (total number of Zeebe partitions) will make sense. Too many threads and nodes will still work, but some of them will be idle.
 :::
 
 ## Archive period

diff --git a/docs/self-managed/tasklist-deployment/importer-and-archiver.md b/docs/self-managed/tasklist-deployment/importer-and-archiver.md
@@ -86,7 +86,7 @@ You can further parallelize archiver and/or importer within one node using the f
 | camunda.tasklist.importer.threadsCount | Number of threads in which data will be imported. | 3             |
 
 :::note
-Parallelization of import and archiving within one node will also happen based on Zeebe partitions, meaning only configurations with (number of nodes) \* (threadsCount) <= (total number of Zeebe partitions) will make sense. Too many threads and nodes will still work, but some of them will be idle.
+Parallelization of import and archiving within one node will also happen based on Zeebe partitions, meaning only configurations with (number of nodes) \* (threadsCount) ≤ (total number of Zeebe partitions) will make sense. Too many threads and nodes will still work, but some of them will be idle.
 :::
 
 ## Archive period