Fix broken links in docs

See gh-33209

spring-boot-project/spring-boot-docs/src/docs/asciidoc/getting-started/installing.adoc

@@ -82,7 +82,7 @@ You can download the Spring CLI distribution from the Spring software repository
 Cutting edge
 https://repo.spring.io/snapshot/org/springframework/boot/spring-boot-cli/[snapshot distributions] are also available.
 
-Once downloaded, follow the {github-raw}/spring-boot-project/spring-boot-cli/src/main/content/INSTALL.txt[INSTALL.txt] instructions from the unpacked archive.
+Once downloaded, follow the {github-raw}/spring-boot-project/spring-boot-tools/spring-boot-cli/src/main/content/INSTALL.txt[INSTALL.txt] instructions from the unpacked archive.
 In summary, there is a `spring` script (`spring.bat` for Windows) in a `bin/` directory in the `.zip` file.
 Alternatively, you can use `java -jar` with the `.jar` file (the script helps you to be sure that the classpath is set correctly).
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/native-image/advanced-topics.adoc

@@ -93,7 +93,7 @@ You need to ensure that all jars are listed (the command above uses `find` and `
 
 [[native-image.advanced.using-the-tracing-agent]]
 === Using the Tracing Agent
-The GraalVM native image https://www.graalvm.org/reference-manual/native-image/Agent/[tracing agent] allows you to intercept reflection, resources or proxy usage on the JVM in order to generate the related hints.
+The GraalVM native image {graal-native-image-docs}/metadata/AutomaticMetadataCollection[tracing agent] allows you to intercept reflection, resources or proxy usage on the JVM in order to generate the related hints.
 Spring should generate most of these hints automatically, but the tracing agent can be used to quickly identify the missing entries.
 
 When using the agent to generate hints for a native image, there are a couple of approaches:
@@ -128,7 +128,7 @@ To use them as input, copy them into the `src/main/resources/META-INF/native-ima
 The next time you build the native image, GraalVM will take these files into consideration.
 
 There are more advanced options which can be set on the native image tracing agent, for example filtering the recorded hints by caller classes, etc.
-For further reading, please see https://www.graalvm.org/reference-manual/native-image/Agent/[the official documentation].
+For further reading, please see {graal-native-image-docs}/metadata/AutomaticMetadataCollection[the official documentation].
 
 
 

spring-boot-project/spring-boot-docs/src/docs/asciidoc/native-image/introducing-graalvm-native-images.adoc

@@ -27,7 +27,7 @@ The main differences are:
 * There is no lazy class loading, everything shipped in the executables will be loaded in memory on startup.
 * There are some limitations around some aspects of Java applications that are not fully supported.
 
-TIP: The {graal-native-image-docs}/Limitations/[Native Image Compatibility and Optimization Guide] section of the GraalVM reference documentation provide more details about GraalVM limitations.
+TIP: The {graal-native-image-docs}/metadata/Compatibility/[Native Image Compatibility Guide] section of the GraalVM reference documentation provide more details about GraalVM limitations.