Fix up links

docs/src/main/asciidoc/extension-maturity-matrix.adoc

@@ -27,7 +27,7 @@ It's completely OK to publish a first version of an extension that doesn't handl
 Also note that this list only includes the technical features of your extension.
 You might also want to think about how you share your extension, and how it presents itself to the world.
 The link:https://hub.quarkiverse.io/checklistfornewprojects/[new extension checklist] on the Quarkiverse Hub has a useful list of ways extensions can participate in the ecosystem.
-It's also a good idea to spend some time on the metadata in the link:https://quarkus.io/version/main/guides/extension-metadata#quarkus-extension-yaml[`quarkus-extension.yaml` file], which is used by Quarkus tooling.
+It's also a good idea to spend some time on the metadata in the xref:extension-metadata#quarkus-extension-yaml[`quarkus-extension.yaml` file], which is used by Quarkus tooling.
 
 Here are some pointers on how to achieve those capabilities.
 
@@ -76,15 +76,15 @@ To provide a Dev Service, use the `DevServicesResultBuildItem` build item. See t
 
 === Basic Dev UI
 
-Every extension gets a tile in the Dev UI. The default tile displays what's in the xref:extension-metadata[extension metadata], so it's a good idea to spend a bit of time getting the metadata right.
+Every extension gets a tile in the Dev UI. The default tile pulls information from the xref:extension-metadata.adoc[extension metadata], which is another reason to spend a bit of time getting the metadata right.
 
-Extensions also use Dev UI hooks to present extra information to users. For example, the tile could include a link to an external console, or an internal page which presents simple text metrics. See the xref:dev-ui.adoc[Dev UI for extension developers] guide.
+Extensions also use Dev UI hooks to present extra information to users. For example, the tile could include a link to an external console, or an internal page which presents simple text metrics. See the xref:dev-ui[Dev UI for extension developers] guide.
 
 
 === Rich Dev UI
 
 Some extensions provide extremely sophisticated Dev UIs.
-For example, they might allow users to interact with the running application, xref:dev-ui#hot-reload[respond to reloads], visualise application metrics, or xref:dev-ui#add-a-log-to-the-footer[stream an application-specific log].
+For example, they might allow users to interact with the running application, xref:dev-ui.adoc#hot-reload[respond to reloads], visualise application metrics, or xref:dev-ui.adoc#add-a-log-to-the-footer[stream an application-specific log].
 The xref:dev-ui.adoc[Dev UI for extension developers] guide also explains these more advanced options.
 
 === Joyful programming model
@@ -141,7 +141,7 @@ See, for example, https://quarkus.io/extensions/io.quarkiverse.quarkus-elasticse
 
 === Replace CDI Beans With Synthetic Ones
 
-Quarkus allows extensions to create xref:https://quarkus.io/guides/cdi-integration#synthetic_beans[synthetic beans].
+Quarkus allows extensions to create xref:cdi-integration#synthetic_beans[synthetic beans].
  These reduce the number of CDI beans at runtime, which improves memory footprint.
 
 == Operations