Sync web site with Quarkus documentation

Author: quarkusbot

_guides/_attributes.adoc

@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.25.3
+:quarkus-version: 3.25.4
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.9

_guides/amqp-reference.adoc

@@ -74,7 +74,7 @@ quarkus.messaging.auto-connector-attachment=false
 
 == Configuring the AMQP Broker access
 
-The AMQP connector connects to AMQP 1.0 brokers such as Apache ActiveMQ or Artemis.
+The AMQP connector connects to AMQP 1.0 brokers such as Apache's ActiveMQ Classic or ActiveMQ Artemis.
 To configure the location and credentials of the broker, add the following properties in the `application.properties`:
 
 [source, properties]
@@ -318,17 +318,19 @@ mp.messaging.outgoing.orders.address=my-order-queue
 If the `address` attribute is not set, the connector uses the channel name.
 
 To use an existing queue, you need to configure the `address`, `container-id` and, optionally, the `link-name` attributes.
-For example, if you have an Apache Artemis broker configured with:
+For example, if you have an Apache ActiveMQ Artemis broker configured with:
 
 [source, xml]
 ----
-<queues>
-    <queue name="people">
-        <address>people</address>
-        <durable>true</durable>
-        <user>artemis</user>
-    </queue>
-</queues>
+<addresses>
+    <address name="people">
+        <anycast>
+            <queue name="people">
+                <user>artemis</user>
+            </queue>
+        </anycast>
+    </address>
+</addresses>
 ----
 
 You need the following configuration:
@@ -367,7 +369,7 @@ mp.messaging.incoming.people-out.container-id=bar
 mp.messaging.incoming.people-out.link-name=people
 ----
 
-More details about the AMQP Address model can be found in the https://activemq.apache.org/components/artemis/documentation/2.0.0/address-model.html[Artemis documentation].
+More details about the AMQP Address model can be found in the https://activemq.apache.org/components/artemis/documentation/latest/address-model.html[ActiveMQ Artemis documentation].
 
 [[blocking-processing]]
 === Execution model and Blocking processing

_guides/logging.adoc

@@ -244,6 +244,17 @@ quarkus.log.level=INFO
 quarkus.log.category."org.hibernate".level=DEBUG
 ----
 
+The equivalent in YAML (assuming the https://quarkus.io/guides/config-yaml[Quarkus YAML extension] is included) would be:
+[source, yaml]
+----
+quarkus:
+  log:
+    level: INFO
+    category:
+      org.hibernate: # The org.hibernate as a single key here is important
+        level: DEBUG
+----
+
 When you set the log level to below `DEBUG`, you must also adjust the minimum log level.
 This setting might be applied either globally with the `quarkus.log.min-level` configuration property, or per category:
 

_guides/security-cors.adoc

@@ -54,7 +54,7 @@ quarkus.http.cors.access-control-allow-credentials=true <7>
 ----
 
 <1> Enables the CORS filter.
-<2> Specifies allowed origins, including a regular expression.
+<2> Specifies allowed origins, including a regular expression. When not specified, CORS is not permitted, and only same-origin requests are allowed.
 <3> Lists allowed HTTP methods for cross-origin requests.
 <4> Declares custom headers that clients can include in requests.
 <5> Identifies response headers that clients can access.

_guides/security-keycloak-authorization.adoc

@@ -525,8 +525,6 @@ public class ProtectedResource {
 }
 ----
 
-NOTE: If you want to use the `AuthzClient` directly, set `quarkus.keycloak.policy-enforcer.enable=true`; otherwise, no bean is available for injection.
-
 [NOTE]
 ====
 To use the `AuthzClient` directly, set `quarkus.keycloak.policy-enforcer.enable=true`.
@@ -535,9 +533,9 @@ Otherwise, no bean is available for injection.
 
 == Mapping protected resources
 
-By default, the extension fetches resources from Keycloak on demand, using their URI to identify and map the application resources that require protection.
+By default, the extension uses lazy loading to fetch resources from Keycloak on demand. It uses the request URI to identify and map application resources that require protection.
 
-To disable on-demand fetching and instead pre-load resources at startup, configure the following property:
+To disable lazy loading and instead pre-load all resources at startup, configure the following property:
 
 [source,properties]
 ----