Sync web site with Quarkus documentation

Author: quarkusbot

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

@@ -17340,6 +17340,8 @@ a| [[quarkus-grpc_quarkus-grpc-server-max-inbound-message-size]] [.property-path
 --
 The max inbound message size in bytes.
 
+When using a single server (using `quarkus.grpc.server.use-separate-server=false`), the default value is 256KB. When using a separate server (using `quarkus.grpc.server.use-separate-server=true`), the default value is 4MB.
+
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_GRPC_SERVER_MAX_INBOUND_MESSAGE_SIZE+++[]

_generated-doc/3.15/config/quarkus-grpc_quarkus.grpc.adoc

@@ -1149,6 +1149,8 @@ a| [[quarkus-grpc_quarkus-grpc-server-max-inbound-message-size]] [.property-path
 --
 The max inbound message size in bytes.
 
+When using a single server (using `quarkus.grpc.server.use-separate-server=false`), the default value is 256KB. When using a separate server (using `quarkus.grpc.server.use-separate-server=true`), the default value is 4MB.
+
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_GRPC_SERVER_MAX_INBOUND_MESSAGE_SIZE+++[]

_generated-doc/3.15/config/quarkus-grpc_quarkus.grpc.server.adoc

@@ -172,6 +172,8 @@ a| [[quarkus-grpc_quarkus-grpc-server_quarkus-grpc-server-max-inbound-message-si
 --
 The max inbound message size in bytes.
 
+When using a single server (using `quarkus.grpc.server.use-separate-server=false`), the default value is 256KB. When using a separate server (using `quarkus.grpc.server.use-separate-server=true`), the default value is 4MB.
+
 
 ifdef::add-copy-button-to-env-var[]
 Environment variable: env_var_with_copy_button:+++QUARKUS_GRPC_SERVER_MAX_INBOUND_MESSAGE_SIZE+++[]

_versions/3.15/guides/_attributes.adoc

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

_versions/3.15/guides/databases-dev-services.adoc

@@ -140,12 +140,14 @@ Dev Services volumes can be mapped to the filesystem or the classpath:
 # Using a filesystem volume:
 quarkus.datasource.devservices.volumes."/path/from"=/container/to <1>
 # Using a classpath volume:
-quarkus.datasource.devservices.volumes."classpath:./file"=/container/to <2>
+quarkus.datasource.devservices.volumes."classpath\:./file"=/container/to <2>
 ----
 
 <1> The file or folder "/path/from" from the local machine will be accessible at "/container/to" in the container.
 <2> When using classpath volumes, the location has to start with "classpath:". The file or folder "./file" from the project's classpath will be accessible at "/container/to" in the container.
 
+CAUTION: The colon character `:` needs to be escaped in `.properties` files as `\:`, or it will be interpreted as a key/value separator.
+
 IMPORTANT: when using a classpath volume, the container will only be granted read permission. On the other hand, when using a filesystem volume, the container will be granted read and write permission.
 
 === Example of mapping volumes to persist the database data

_versions/3.15/guides/vertx-reference.adoc

@@ -730,7 +730,7 @@ Read xref:./virtual-threads.adoc[the virtual thread guide] for more details.
 
 === Use codecs
 
-The https://vertx.io/docs/vertx-core/java/#event_bus[Vert.x Event Bus] uses https://vertx.io/docs/vertx-core/java/#_message_codecs[codecs] to _serialize_ and _deserialize_ message objects.
+The link:++https://vertx.io/docs/vertx-core/java/#event_bus++[Vert.x Event Bus] uses link:++https://vertx.io/docs/vertx-core/java/#_message_codecs++[codecs] to _serialize_ and _deserialize_ message objects.
 Quarkus provides a default codec for local delivery.
 This codec is automatically used for return types and message body parameters of local consumers, i.e. methods annotated with `@ConsumeEvent` where `ConsumeEvent#local() == true` (which is the default).