chore(721-to-722): Adjust Quarkus Property Example

Related-to: camunda/camunda-bpm-platform#4579

Author: psavidis

content/update/minor/721-to-722/_index.md

@@ -286,7 +286,7 @@ This requires using the new namespace `generic-config`.
 
 - `quarkus.camunda.enforce-history-time-to-live` **becomes** `quarkus.camunda.generic-config.enforce-history-time-to-live`
 
-- `quarkus.camunda.job-executor.thread-pool.max-pool-size` **becomes** `quarkus.camunda.job-executor.generic-config.thread-pool.max-pool-size`
+- `quarkus.camunda.dmn-enabled` **becomes** `quarkus.camunda.generic-config.dmn-enabled`
 
 For a detailed guide on the new Quarkus properties, visit the updated [Quarkus Configuration]({{< ref "/user-guide/quarkus-integration/configuration.md" >}}) page.
 

content/user-guide/quarkus-integration/configuration.md

@@ -140,10 +140,10 @@ page documents all the available properties. Convert any property names you inte
 `kebab-case` format, like in the following example:
 
 ```properties
-quarkus.camunda.job-executor.generic-config.max-jobs-per-acquisition=5
-quarkus.camunda.job-executor.generic-config.lock-time-in-millis=500000
-quarkus.camunda.job-executor.generic-config.wait-time-in-millis=7000
-quarkus.camunda.job-executor.generic-config.max-wait=65000
+quarkus.camunda.job-executor.max-jobs-per-acquisition=5
+quarkus.camunda.job-executor.lock-time-in-millis=500000
+quarkus.camunda.job-executor.wait-time-in-millis=7000
+quarkus.camunda.job-executor.max-wait=65000
 ```
 
 ## Quarkus Extension Configuration
@@ -177,7 +177,7 @@ the Quarkus-specific properties in the following table:
   <tr><td colspan="4"><b>Job Executor</b></td></tr>
 
   <tr>
-    <td rowspan="2"><code>quarkus.camunda.job-executor.generic-config.thread-pool</code></td>
+    <td rowspan="2"><code>quarkus.camunda.job-executor.thread-pool</code></td>
     <td><code>.max-pool-size</code></td>
     <td>Sets the maximum number of threads that can be present in the thread pool.</td>
     <td><code>10</code></td>
@@ -218,18 +218,18 @@ engine configuration, job executor and data source:
 
 ```properties
 # process engine configuration
-quarkus.camunda.generic-config.cmmn-enabled=false
-quarkus.camunda.generic-config.dmn-enabled=false
-quarkus.camunda.generic-config.history=none
+quarkus.camunda.cmmn-enabled=false
+quarkus.camunda.dmn-enabled=false
+quarkus.camunda.history=none
 
 # job executor configuration
-quarkus.camunda.job-executor.generic-config.thread-pool.max-pool-size=12
-quarkus.camunda.job-executor.generic-config.thread-pool.queue-size=5
-quarkus.camunda.job-executor.generic-config.max-jobs-per-acquisition=5
-quarkus.camunda.job-executor.generic-config.lock-time-in-millis=500000
-quarkus.camunda.job-executor.generic-config.wait-time-in-millis=7000
-quarkus.camunda.job-executor.generic-config.max-wait=65000
-quarkus.camunda.job-executor.generic-config.backoff-time-in-millis=5
+quarkus.camunda.job-executor.thread-pool.max-pool-size=12
+quarkus.camunda.job-executor.thread-pool.queue-size=5
+quarkus.camunda.job-executor.max-jobs-per-acquisition=5
+quarkus.camunda.job-executor.lock-time-in-millis=500000
+quarkus.camunda.job-executor.wait-time-in-millis=7000
+quarkus.camunda.job-executor.max-wait=65000
+quarkus.camunda.job-executor.backoff-time-in-millis=5
 
 # custom data source configuration and selection
 quarkus.datasource.my-datasource.db-kind=h2