Merge pull request #33504 from ebullient/docs-errors

Fix propagation of native category

docs/src/main/asciidoc/cache.adoc

@@ -764,7 +764,7 @@ Each cache declared using the <<#annotations-api,annotations caching API>> can b
 [NOTE]
 ====
 The cache metrics collection will only work if your application depends on a `quarkus-micrometer-registry-*` extension.
-See the xref:micrometer.adoc[Micrometer metrics guide] to learn how to use Micrometer in Quarkus.
+See the xref:telemetry-micrometer.adoc[Micrometer metrics guide] to learn how to use Micrometer in Quarkus.
 ====
 
 The cache metrics collection is disabled by default.

docs/src/main/asciidoc/deploying-to-kubernetes.adoc

@@ -3,9 +3,10 @@ This guide is maintained in the main Quarkus repository
 and pull requests should be submitted there:
 https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
+[id="deploy-kubernetes"]
 = Kubernetes extension
 include::_attributes.adoc[]
-:categories: cloud
+:categories: cloud, native
 :summary: This guide covers how to deploy a native application on Kubernetes.
 
 Quarkus offers the ability to automatically generate Kubernetes resources based on sane defaults and user-supplied configuration using https://github.com/dekorateio/dekorate/[dekorate].

docs/src/main/asciidoc/deploying-to-openshift.adoc

@@ -3,9 +3,10 @@ This guide is maintained in the main Quarkus repository
 and pull requests should be submitted there:
 https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
+[id="deploy-openshift"]
 = Deploying on OpenShift
 include::_attributes.adoc[]
-:categories: cloud
+:categories: cloud, native
 :summary: This guide covers how to deploy a native application on OpenShift.
 
 This guide covers generating and deploying OpenShift resources based on sane default and user supplied configuration.

docs/src/main/asciidoc/getting-started-testing.adoc

@@ -3,9 +3,10 @@ This guide is maintained in the main Quarkus repository
 and pull requests should be submitted there:
 https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
+[id="testing"]
 = Testing Your Application
 include::_attributes.adoc[]
-:categories: core
+:categories: core, native, tooling
 :summary: This guide covers testing in JVM mode, native mode, and injection of resources into tests
 :numbered:
 :sectnums:

docs/src/main/asciidoc/getting-started.adoc

@@ -472,7 +472,7 @@ Furthermore, users can supply a custom banner by placing the banner file in `src
 == Non Application endpoints
 
 Various Quarkus extensions contribute non-application endpoints that provide different kinds of information about the application.
-Examples of such extensions are the xref:smallrye-health.adoc[health], xref:micrometer.adoc[metrics], xref:openapi-swaggerui.adoc[OpenAPI] and info extensions.
+Examples of such extensions are the xref:smallrye-health.adoc[health], xref:telemetry-micrometer.adoc[metrics], xref:openapi-swaggerui.adoc[OpenAPI] and info extensions.
 
 These non application endpoints are normally accessible under the `/q` prefix like so:
 

docs/src/main/asciidoc/gradle-tooling.adoc

@@ -3,12 +3,15 @@ This guide is maintained in the main Quarkus repository
 and pull requests should be submitted there:
 https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
-= Building Quarkus apps with Gradle
+[id="gradle-tooling"]
+= Quarkus and Gradle
 include::_attributes.adoc[]
-:categories: tooling
-:summary: This guide covers: Gradle configuration, creating a new project, dealing with extensions, development mode, debugging, import in your IDE, building a native image, and build a container friendly executable
+:categories: tooling, native
+:summary: Develop and build your Quarkus application with Gradle
 :devtools-no-maven:
 
+Use Gradle to create a new project, add or remove extensions, launch development mode, debug your application, and build your application into a jar, native executable, or container-friendly executable. Import your project into your favorite IDE using Gradle project metadata.
+
 [[project-creation]]
 == Creating a new project
 

docs/src/main/asciidoc/grpc-service-consumption.adoc

@@ -372,7 +372,7 @@ The default priority, used if the interceptor does not implement the `Prioritize
 
 === Enabling metrics collection
 
-gRPC client metrics are automatically enabled when the application also uses the xref:micrometer.adoc[`quarkus-micrometer`] extension.
+gRPC client metrics are automatically enabled when the application also uses the xref:telemetry-micrometer.adoc[`quarkus-micrometer`] extension.
 Micrometer collects the metrics of all the gRPC clients used by the application.
 
 As an example, if you export the metrics to Prometheus, you will get:

docs/src/main/asciidoc/grpc-service-implementation.adoc

@@ -371,7 +371,7 @@ dependencies {
 
 === Enabling metrics collection
 
-gRPC server metrics are automatically enabled when the application also uses the xref:micrometer.adoc[`quarkus-micrometer`] extension.
+gRPC server metrics are automatically enabled when the application also uses the xref:telemetry-micrometer.adoc[`quarkus-micrometer`] extension.
 Micrometer collects the metrics of all the gRPC services implemented by the application.
 
 As an example, if you export the metrics to Prometheus, you will get:

docs/src/main/asciidoc/hibernate-orm.adoc

@@ -814,7 +814,7 @@ For more information about Hibernate Envers, see link:https://hibernate.org/orm/
 
 [[metrics]]
 == Metrics
-Either xref:micrometer.adoc[Micrometer] or xref:microprofile-metrics.adoc[SmallRye Metrics] are
+Either xref:telemetry-micrometer.adoc[Micrometer] or xref:microprofile-metrics.adoc[SmallRye Metrics] are
 capable of exposing metrics that Hibernate ORM collects at runtime. To enable exposure of Hibernate metrics
 on the `/q/metrics` endpoint, make sure your project depends on a metrics extension and set the configuration property `quarkus.hibernate-orm.metrics.enabled` to `true`.
 When using link:microprofile-metrics[SmallRye Metrics], metrics will be available under the `vendor` scope.

docs/src/main/asciidoc/kafka-streams.adoc

@@ -1249,7 +1249,7 @@ content-length: 265
 This guide has shown how you can build stream processing applications using Quarkus and the Kafka Streams APIs,
 both in JVM and native modes.
 For running your KStreams application in production, you could also add health checks and metrics for the data pipeline.
-Refer to the Quarkus guides on xref:micrometer.adoc[Micrometer], xref:smallrye-metrics.adoc[SmallRye Metrics], and xref:smallrye-health.adoc[SmallRye Health] to learn more.
+Refer to the Quarkus guides on xref:telemetry-micrometer.adoc[Micrometer], xref:smallrye-metrics.adoc[SmallRye Metrics], and xref:smallrye-health.adoc[SmallRye Health] to learn more.
 
 == Configuration Reference
 

docs/src/main/asciidoc/maven-tooling.adoc

@@ -3,12 +3,15 @@ This guide is maintained in the main Quarkus repository
 and pull requests should be submitted there:
 https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc
 ////
-= Building applications with Maven
+[id="maven-tooling"]
+= Quarkus and Maven
 include::_attributes.adoc[]
-:categories: tooling
-:summary: This guide covers: Maven configuration, creating a new project, dealing with extensions, development mode, debugging, import in your IDE, building a native image, and build a container friendly executable
+:categories: tooling, native
+:summary: Develop and build your Quarkus application with Maven
 :devtools-no-gradle:
 
+Use Maven to create a new project, add or remove extensions, launch development mode, debug your application, and build your application into a jar, native executable, or container-friendly executable. Import your project into your favorite IDE using Maven project metadata.
+
 [[project-creation]]
 == Creating a new project