Sync documentation of main branch

Author: actions-user

_generated-doc/main/config/quarkus-all-config.adoc

@@ -32557,7 +32557,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Whether or not the jacoco extension is enabled.
+Whether or not the Jacoco extension is enabled.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -32578,7 +32578,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The jacoco data file. The path can be relative (to the module) or absolute.
+The Jacoco data file. The path can be relative (to the module) or absolute.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -32599,7 +32599,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Whether to reuse (`true`) or delete (`false`) the jacoco data file on each run.
+Whether to reuse (`true`) or delete (`false`) the Jacoco data file on each run.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-jacoco.adoc

@@ -15,7 +15,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Whether or not the jacoco extension is enabled.
+Whether or not the Jacoco extension is enabled.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -36,7 +36,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The jacoco data file. The path can be relative (to the module) or absolute.
+The Jacoco data file. The path can be relative (to the module) or absolute.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -57,7 +57,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Whether to reuse (`true`) or delete (`false`) the jacoco data file on each run.
+Whether to reuse (`true`) or delete (`false`) the Jacoco data file on each run.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-jacoco_quarkus.jacoco.adoc

@@ -15,7 +15,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Whether or not the jacoco extension is enabled.
+Whether or not the Jacoco extension is enabled.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -36,7 +36,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The jacoco data file. The path can be relative (to the module) or absolute.
+The Jacoco data file. The path can be relative (to the module) or absolute.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -57,7 +57,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Whether to reuse (`true`) or delete (`false`) the jacoco data file on each run.
+Whether to reuse (`true`) or delete (`false`) the Jacoco data file on each run.
 
 
 ifdef::add-copy-button-to-env-var[]

_versions/main/guides/qute-reference.adoc

@@ -3007,10 +3007,9 @@ If there is a message bundle method that accepts a single parameter of an enum t
 @Message <1>
 String methodName(MyEnum enum);
 ----
-<1> The value is intentionally not provided. There's also no key for the method in a localized file.
-
-Then it receives a generated template:
+<1> The value is intentionally not provided. There's also no key/value pair for this method in a localized file.
 
+Then it receives a generated template like:
 [source,html]
 ----
 {#when enumParamName}
@@ -3019,15 +3018,27 @@ Then it receives a generated template:
 {/when}
 ----
 
-Furthermore, a special message method is generated for each enum constant. Finally, each localized file must contain keys and values for all constant message keys:
+Furthermore, a special message method is generated for each enum constant. 
+Finally, each localized file must contain keys and values for all enum constants:
 
 [source,poperties]
 ----
 methodName_CONSTANT1=Value 1
 methodName_CONSTANT2=Value 2
 ----
 
-In a template, an enum constant can be localized with a message bundle method like `{msg:methodName(enumConstant)}`.
+// We need to escape the first underscore 
+// See https://docs.asciidoctor.org/asciidoc/latest/subs/prevent/
+[IMPORTANT] 
+.Message keys for enum constants
+==== 
+By default, the message key consists of the method name followed by the `\_` separator and the constant name.
+If any constant name of a particular enum contains the `_` or the `$` character then the `\_$` separator must be used for all message keys for this enum instead.
+For example, `methodName_$CONSTANT_1=Value 1` or `methodName_$CONSTANT$1=Value 1`.
+A constant of a localized enum may not contain the `_$` separator.
+====
+
+In a template, the localized message for an enum constant can be obtained with a message bundle method like `{msg:methodName(enumConstant)}`.
 
 TIP: There is also <<convenient-annotation-for-enums,`@TemplateEnum`>> - a convenient annotation to access enum constants in a template.
 

_versions/main/guides/security-openid-connect-multitenancy.adoc

@@ -332,6 +332,7 @@ A similar technique can be used with `TenantConfigResolver`, where a `tenant-id`
 ====
 If you also use Hibernate ORM multitenancy or MongoDB with Panache multitenancy and both tenant ids are the same,
 you can get the tenant id from the `RoutingContext` attribute with `tenant-id`. You can find more information here:
+
 * xref:hibernate-orm.adoc#multitenancy[Hibernate ORM multitenancy]
 * xref:mongodb-panache.adoc#multitenancy[MongoDB with Panache multitenancy]
 ====