Sync documentation of main branch

Author: actions-user

_data/versioned/main/index/quarkus.yaml

@@ -769,7 +769,7 @@ types:
     url: /guides/extension-writing-dev-service
   - title: YAML configuration
     filename: config-yaml.adoc
-    summary: "Optionally, use `application.yaml` instead of `application.properties` to configure your application."
+    summary: "Optionally, use application.yaml instead of application.properties to configure your application."
     categories: core
     topics:
     - configuration
@@ -996,7 +996,7 @@ types:
     url: /guides/aws-lambda-http
   - title: Accessing application properties with Spring Boot properties API
     filename: spring-boot-properties.adoc
-    summary: Use Spring Boot's `@ConfigurationProperties` in place of MicroProfile Config annotations
+    summary: Use Spring Boot's @ConfigurationProperties in place of MicroProfile Config annotations
     categories: compatibility
     topics:
     - spring

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

@@ -21020,6 +21020,27 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
+a| [[quarkus-grpc_quarkus-grpc-clients-client-name-use-vertx-event-loop]] [.property-path]##link:#quarkus-grpc_quarkus-grpc-clients-client-name-use-vertx-event-loop[`quarkus.grpc.clients."client-name".use-vertx-event-loop`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.grpc.clients."client-name".use-vertx-event-loop+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+Use Vert.x event loop(s) for gRPC client, if it's using the previous Java gRPC support.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_GRPC_CLIENTS__CLIENT_NAME__USE_VERTX_EVENT_LOOP+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_GRPC_CLIENTS__CLIENT_NAME__USE_VERTX_EVENT_LOOP+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`true`
+
 h|[[quarkus-grpc_section_quarkus-grpc-clients-client-name-xds]] [.section-name.section-level1]##link:#quarkus-grpc_section_quarkus-grpc-clients-client-name-xds[Configure XDS usage, if enabled]##
 h|Type
 h|Default

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

@@ -100,6 +100,27 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
+a| [[quarkus-grpc_quarkus-grpc-clients-client-name-use-vertx-event-loop]] [.property-path]##link:#quarkus-grpc_quarkus-grpc-clients-client-name-use-vertx-event-loop[`quarkus.grpc.clients."client-name".use-vertx-event-loop`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.grpc.clients."client-name".use-vertx-event-loop+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+Use Vert.x event loop(s) for gRPC client, if it's using the previous Java gRPC support.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_GRPC_CLIENTS__CLIENT_NAME__USE_VERTX_EVENT_LOOP+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_GRPC_CLIENTS__CLIENT_NAME__USE_VERTX_EVENT_LOOP+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`true`
+
 h|[[quarkus-grpc_section_quarkus-grpc-clients-client-name-xds]] [.section-name.section-level1]##link:#quarkus-grpc_section_quarkus-grpc-clients-client-name-xds[Configure XDS usage, if enabled]##
 h|Type
 h|Default

_generated-doc/main/config/quarkus-grpc_quarkus.grpc.clients.adoc

@@ -28,6 +28,27 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
+a| [[quarkus-grpc_quarkus-grpc-clients_quarkus-grpc-clients-client-name-use-vertx-event-loop]] [.property-path]##link:#quarkus-grpc_quarkus-grpc-clients_quarkus-grpc-clients-client-name-use-vertx-event-loop[`quarkus.grpc.clients."client-name".use-vertx-event-loop`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.grpc.clients."client-name".use-vertx-event-loop+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+Use Vert.x event loop(s) for gRPC client, if it's using the previous Java gRPC support.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_GRPC_CLIENTS__CLIENT_NAME__USE_VERTX_EVENT_LOOP+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_GRPC_CLIENTS__CLIENT_NAME__USE_VERTX_EVENT_LOOP+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`true`
+
 h|[[quarkus-grpc_quarkus-grpc-clients_section_quarkus-grpc-clients-client-name-xds]] [.section-name.section-level1]##link:#quarkus-grpc_quarkus-grpc-clients_section_quarkus-grpc-clients-client-name-xds[Configure XDS usage, if enabled]##
 h|Type
 h|Default

_versions/main/guides/_attributes.adoc

@@ -24,7 +24,7 @@
 :kotlin-version: 2.0.21
 :grpc-version: 1.69.1
 :protoc-version: 3.25.5
-:gcf-invoker-version: 1.3.0
+:gcf-invoker-version: 1.4.1
 // Cannot simply use the name 'hibernate-*-version' here as it somehow gets
 // overridden to the full version, at least when building locally.
 :hibernate-orm-version-major-minor: 6.6

_versions/main/guides/config-yaml.adoc

@@ -7,7 +7,7 @@ https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 include::_attributes.adoc[]
 :diataxis-type: howto
 :categories: core
-:summary: Optionally, use `application.yaml` instead of `application.properties` to configure your application.
+:summary: Optionally, use application.yaml instead of application.properties to configure your application.
 :topics: configuration
 :extensions: io.quarkus:quarkus-config-yaml
 

_versions/main/guides/rest.adoc

@@ -1624,7 +1624,7 @@ public User userPrivate() {
 }
 ----
 
-When the result the `userPublic` method is serialized, the `id` field will not be contained in the response as the `Public` view does not include it.
+When the result of the `userPublic` method is serialized, the `id` field will not be contained in the response as the `Public` view does not include it.
 The result of `userPrivate` however will include the `id` as expected when serialized.
 
 ===== Reflection-free Jackson serialization and deserialization

_versions/main/guides/spring-boot-properties.adoc

@@ -6,7 +6,7 @@ https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 = Accessing application properties with Spring Boot properties API
 include::_attributes.adoc[]
 :categories: compatibility
-:summary: Use Spring Boot's `@ConfigurationProperties` in place of MicroProfile Config annotations
+:summary: Use Spring Boot's @ConfigurationProperties in place of MicroProfile Config annotations
 :topics: spring,configuration,compatibility
 :extensions: io.quarkus:quarkus-spring-boot-properties
 

_versions/main/guides/telemetry-micrometer.adoc

@@ -10,7 +10,7 @@ include::_attributes.adoc[]
 :categories: observability
 :summary: Use Micrometer to collect metrics produced by Quarkus, its extensions, and your application.
 :base-units: https://github.com/micrometer-metrics/micrometer/blob/main/micrometer-core/src/main/java/io/micrometer/core/instrument/binder/BaseUnits.java
-:concepts: https://micrometer.io/docs/concepts
+:concepts: https://docs.micrometer.io/micrometer/reference/concepts
 :topics: observability,micrometer
 :extensions: io.quarkus:quarkus-micrometer
 
@@ -188,7 +188,7 @@ For hierarchical systems that only support a flat metric name, Micrometer will f
 
 Tags can be specified when a meter is registered with a `MeterRegistry` or using a <<meter-filter,Meter Filter>>.
 
-See the Micrometer documentation for additional advice on link:{concepts}#_tag_naming[tag naming].
+See the Micrometer documentation for additional advice on link:{concepts}/naming[tag naming].
 
 IMPORTANT: Each unique combination of metric name and dimension produces a unique time series.
 Using an unbounded set of dimensional data can lead to a "cardinality explosion", an exponential increase in the creation of new time series.
@@ -279,7 +279,7 @@ Gauge.builder("jvm.threads.peak", threadBean, ThreadMXBean::getPeakThreadCount)
 <4> Associate <<define-tags,tags>> with the gauge
 <5> Register the Gauge with the MeterRegistry
 
-See link:{concepts}#_gauges[Gauges] in the Micrometer documentation for more information and examples.
+See link:{concepts}/gauges[Gauges] in the Micrometer documentation for more information and examples.
 Of note are two special cases: `TimeGauge` for measuring time, and a `MultiGauge` for reporting several criteria together.
 
 NOTE: Micrometer does not create strong references to the objects it observes by default.
@@ -336,7 +336,7 @@ void countThisMethod(){
 <1> A CDI interceptor will create and register a counter called `counted.method`
 <2> The interceptor-created counter will have the "extra" dimension tag with value "annotated"
 
-See link:{concepts}#_counters[Counters] in the Micrometer documentation for more information and examples, including the less common `FunctionCounter` that can be used to measure the result returned by an always increasing function.
+See link:{concepts}/counters[Counters] in the Micrometer documentation for more information and examples, including the less common `FunctionCounter` that can be used to measure the result returned by an always increasing function.
 
 When should you use a counter?
 Use a counter if you are doing something that can not be either timed or summarized.
@@ -478,7 +478,7 @@ sample.stop(registry.timer("my.timer", "response", response.status())); // <3>
 ==== Histograms and percentiles
 
 Both timers and distribution summaries can be configured to emit additional statistics, like histogram data, precomputed percentiles, or service level objective (SLO) boundaries.
-See link:{concepts}#_timers[Timers] and link:{concepts}#_distribution_summaries[Distribution Summaries] in the Micrometer documentation for more information and examples, including memory footprint estimation for both types.
+See link:{concepts}/timers[Timers] and link:{concepts}/distribution-summaries[Distribution Summaries] in the Micrometer documentation for more information and examples, including memory footprint estimation for both types.
 
 [IMPORTANT]
 ====