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.24.4
+:quarkus-version: 3.24.5
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.9

_guides/blaze-persistence.adoc

@@ -51,7 +51,7 @@ Add the following dependencies to your project:
 </dependency>
 <dependency>
     <groupId>com.blazebit</groupId>
-    <artifactId>blaze-persistence-integration-hibernate-6.2</artifactId>
+    <artifactId>blaze-persistence-integration-hibernate-7.0</artifactId>
     <scope>runtime</scope>
 </dependency>
 ----
@@ -60,7 +60,7 @@ Add the following dependencies to your project:
 .Using Gradle
 ----
 implementation("com.blazebit:blaze-persistence-integration-quarkus-3")
-runtimeOnly("com.blazebit:blaze-persistence-integration-hibernate-6.2")
+runtimeOnly("com.blazebit:blaze-persistence-integration-hibernate-7.0")
 ----
 
 The use in native images requires a dependency on the entity view annotation processor that may be extracted into a separate `native` profile:

_guides/compose-dev-services.adoc

@@ -22,7 +22,7 @@ _The Compose Specification is a developer-focused standard for defining cloud an
 
 Compose is a widely used tool for defining and managing multi-container applications, for development and testing purposes.
 A YAML description file, typically named `compose.yml`, defines the services, networks, and volumes required for your application.
-https://docs.docker.com/compose/[Docker Compose] is the reference implementation and https://podman-desktop.io/docs/compose[Podman Desktop] also provides out-of-box support for the Compose specification.
+https://docs.docker.com/compose/[Docker Compose] is the reference implementation and https://podman-desktop.io/docs/compose[Podman Desktop] also provides out-of-the-box support for the Compose specification.
 
 Quarkus detects Compose files named `compose-devservices.yml` (or <<compose-devservices-compose-files>>) in your project and starts the defined services when your application runs in development or test mode.
 Extensions providing dev services discover these custom services and use them instead of creating default ones.
@@ -78,7 +78,7 @@ When you run the application in dev mode or execute tests, Compose Dev Services
 instead of using the default dev service provided by the `quarkus-jdbc-postgresql` extension.
 
 As per the above configuration, the PostgreSQL container port `5432` will be exposed to a random host port
-and the application datasource will be configured by extracting connection information such as _user_, _password_ and the _database name_.
+and the application datasource will be configured by extracting connection information such as _user_, _password_, and the _database name_.
 
 === Multi-Service Example: Custom Network and Dependencies
 
@@ -154,7 +154,7 @@ For example, the PostgreSQL Dev Service looks for a service with the image name
 
 When a match is found, the extension will:
 
-1. Extract connection information from the container (connection url, credentials, database name, etc.)
+1. Extract connection information from the container (connection URL, credentials, database name, etc.)
 2. Configure the application to use the discovered service
 3. Skip creating its own default Dev Service container
 
@@ -287,7 +287,7 @@ quarkus.compose.devservices.files=src/main/docker/base-compose.yml,src/main/dock
 
 ==== Using Compose profiles
 
-With profiles, Compose files can define a set of active profiles so started services is adjusted for various usages and environments.
+With profiles, Compose files can define a set of active profiles so that started services are adjusted for various usages and environments.
 You can specify the profiles to activate by setting the `quarkus.compose.devservices.profiles` property in the `application.properties` file:
 
 [source, yaml]
@@ -313,7 +313,7 @@ services:
 
 === Ignoring Services
 
-You can configure Compose Dev Services to ignore specific services by adding the `io.quarkus.devservices.compose.ignore` label to the service in your Compose file:
+You can configure Compose Dev Services to not discover specific services by adding the `io.quarkus.devservices.compose.ignore` label to the service in your Compose file:
 
 [source, yaml]
 ----
@@ -378,7 +378,7 @@ services:
 ----
 
 You can also specify how many times a log message should appear by setting the numeric suffix value:
-`io.quarkus.devservices.compose.wait_for.logs.3: .*Worker started.*`
+`io.quarkus.devservices.compose.wait_for.logs.3: .\*Worker started.*`
 
 === Wait for Ports
 
@@ -469,7 +469,7 @@ The host is set to the Docker host IP address, and the port is set to the mapped
 
 [NOTE]
 ====
-For database services, if the label `io.quarkus.compose.devservices.jdbc.parameters` is set, the parameters are added to the JDBC URL.
+For database services, if the label `io.quarkus.devservices.compose.jdbc.parameters` is set, the parameters are added to the JDBC URL.
 ====
 
 === Custom config mapping using service labels
@@ -481,7 +481,7 @@ You can customize how environment variables and exposed ports are mapped to appl
 To map an environment variable to a specific application configuration property,
 use the `io.quarkus.devservices.compose.config_map.env.<env-var-name>` label.
 
-Let's take the example of a MQTT broker:
+Let's take the example of an MQTT broker:
 
 [source, yaml]
 ----
@@ -611,7 +611,7 @@ export KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://localhost:$PORT_9092;
 
 Compose Dev Services provides several configuration options to control how services are started, stopped and shared between application instances.
 
-When the application starts in development or test mode, Compose Dev Services decide whether to start services or to discover already running services based on the configuration.
+When the application starts in development or test mode, Compose Dev Services decides whether to start services or to discover already running services based on the configuration.
 When the application stops, Compose Dev Services stops the services it started.
 
 === Compose Project Name
@@ -627,9 +627,9 @@ Compose Dev Services determines the project name as follows:
 
 === Discovering already started Compose Services
 
-Once the project name is determined, Compose Dev Services first tries discovering existing services with that project name.
+Once the project name is determined, Compose Dev Services first tries to discover existing services with that project name.
 
-The already started compose project may have been already started by another Quarkus application running locally with the same project name,
+The already started compose project may have been started by another Quarkus application running locally with the same project name,
 or manually using the `docker compose up` or `podman compose up` commands.
 
 Regardless of how the services were started,
@@ -664,7 +664,7 @@ This allows services to be reused by other applications or subsequent runs of th
 
 You can also configure the timeout for stopping services with the `quarkus.compose.devservices.stop-timeout` property.
 After the timeout, Compose Dev Services will forcefully stop the services.
-The default timeout is chosen deliberately short to 1 second for fast cleanup, but you can increase it as needed:
+The default timeout is deliberately chosen to be short (1 second) for fast cleanup, but you can increase it as needed:
 
 [source, text]
 ----

_guides/container-image.adoc

@@ -150,7 +150,7 @@ For example, building multi-platform images is implemented differently for Docke
 === OpenShift
 
 The extension `quarkus-container-image-openshift` is using OpenShift binary builds in order to perform container builds inside the OpenShift cluster.
-The idea behind the binary build is that you just upload the artifact and its dependencies to the cluster and during the build they will be merged to a builder image (defaults to `fabric8/s2i-java`).
+The idea behind the binary build is that you just upload the artifact and its dependencies to the cluster and during the build they will be merged to a builder image (defaults to `ubi9/openjdk-17` or `ubi9/openjdk-21`).
 
 The benefit of this approach, is that it can be combined with OpenShift's `DeploymentConfig` that makes it easy to roll out changes to the cluster.
 

_guides/rest.adoc

@@ -138,7 +138,7 @@ public static class MyApplication extends Application {
 ----
 
 This will cause all rest endpoints to be resolve relative to `/api`, so the endpoint above with `@Path("rest")` would
-be accessible at `/api/rest/`. You can also set the `quarkus.rest.path` build time property to set the root path if you
+be accessible at `/api/rest/`. You can also set the <<quarkus-rest-common_quarkus-rest-path,`quarkus.rest.path`>> build time property to set the root path if you
 don't want to use an annotation.
 
 === Declaring endpoints: HTTP methods
@@ -1652,7 +1652,7 @@ This feature is introduced as a Technology Preview and is disabled by default.
 By eliminating reliance on reflection during deserialization, applications can achieve better performance and reduced memory consumption, particularly for native applications where reflection can introduce overhead.
 If you implement this feature, run tests to assess its effect on your applications.
 
-To enable this feature, set the following configuration property to `true`:
+To enable this feature, set the <<quarkus-rest-jackson_quarkus-rest-jackson-optimization-enable-reflection-free-serializers,`quarkus.rest.jackson.optimization.enable-reflection-free-serializers`>> configuration property to `true`:
 
 `quarkus.rest.jackson.optimization.enable-reflection-free-serializers=true`.
 
@@ -3374,3 +3374,9 @@ In addition to the Server side, Quarkus REST comes with a new MicroProfile REST
 Please note that the `quarkus-resteasy-client` extension may not be used with Quarkus REST, use `quarkus-rest-client` instead.
 
 See the xref:rest-client.adoc[REST Client Guide] for more information about the REST client.
+
+[[rest-configuration-reference]]
+== Quarkus REST Configuration Reference
+
+include::{generated-dir}/config/quarkus-rest-common_quarkus.rest.adoc[leveloffset=+1, opts=optional]
+include::{generated-dir}/config/quarkus-rest-jackson.adoc[leveloffset=+1, opts=optional]