[GR-39276] Broken links check with absolutize.rb.

PullRequest: graal/12281

Author: olyagpl

docs/getting-started/graalvm-enterprise/get-started-graalvm-enterprise.md

@@ -25,7 +25,7 @@ You can get Oracle GraalVM Enterprise Edition by:
 Choose your operating system and proceed to the installation steps for your specific platform:
 
 * Oracle Cloud 
-  * [OCI Compute with Oracle Linux 7/8](oci/installation-compute-instance-yum.md)
+  * [OCI Compute with Oracle Linux 7/8](oci/installation-compute-instance-with-OL.md)
   * [OCI DevOps Build Pipelines](oci/installation-devops-build-pipeline.md)
 * [Linux](installation-linux.md)
 * [Linux ARM64](installation-linux-aarch64.md)

docs/getting-started/graalvm-enterprise/oci/installation-devops-build-pipeline.md

@@ -27,6 +27,7 @@ The way to work with a build pipeline is to add statements to a [build specifica
 To install and use GraalVM Enterprise in the DevOps build pipeline, update your build specification file as follows:
 
 1. Add the command to install GraalVM Enterprise with Native Image and Java Development Kit (JDK):
+
     ```yml
     steps:
     - type: Command
@@ -60,9 +61,31 @@ To install and use GraalVM Enterprise in the DevOps build pipeline, update your
 
 Here is an example of a complete [build specification file](https://github.com/oracle-devrel/oci-devops-examples/blob/main/oci-build-examples/oci_devops_build_with_graalenterprise/build_spec.yaml).
 
+Use  the `yum list` command to get a list of all the GraalVM Enterprise RPMs available. For instance, use the following command to list all the available GraalVM Enterprise 22.x JDK17 components:
+
+```shell
+yum list graalvm22-ee-17*
+
+graalvm22-ee-17-native-image.x86_64        22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-espresso.x86_64            22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-javascript.x86_64          22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-jdk.x86_64                 22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-libpolyglot.x86_64         22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-llvm.x86_64                22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-llvm-toolchain.x86_64      22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-nodejs.x86_64              22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-polyglot.x86_64            22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-python.x86_64              22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-ruby.x86_64                22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-tools.x86_64               22.2.0-1.el7       ol7_oci_included
+graalvm22-ee-17-wasm.x86_64                22.2.0-1.el7       ol7_oci_included
+...
+```
+
 To try this feature out, use the sample project: [Using GraalVM Enterprise in OCI DevOps Build Pipelines](https://github.com/oracle-devrel/oci-devops-examples/tree/main/oci-build-examples/oci_devops_build_with_graalenterprise). It describes how to set up GraalVM Enterprise in OCI DevOps service, create a build pipeline, add build stages, and so on.
 
 ### Related Documentation
 
 * [OCI DevOps: Using GraalVM Enterprise in DevOps Build Pipelines](https://docs.oracle.com/en-us/iaas/Content/devops/using/graalvm.htm)
-* [OCI Build Examples: Using GraalVM Enterprise in OCI DevOps Build Pipelines](https://github.com/oracle-devrel/oci-devops-examples/tree/main/oci-build-examples/oci_devops_build_with_graalenterprise)
+* [OCI Build Examples: Using GraalVM Enterprise in OCI DevOps Build Pipelines](https://github.com/oracle-devrel/oci-devops-examples/tree/main/oci-build-examples/oci_devops_build_with_graalenterprise)
+* [OCI Build Examples: Using GraalVM Enterprise in OCI DevOps to build a Micronaut REST App](https://github.com/oracle-devrel/oci-devops-examples/tree/main/oci-build-examples/oci_devops_graalee_micronaut)

docs/reference-manual/native-image/guides/containerise-native-executable-with-docker.md

@@ -79,10 +79,10 @@ For that, we will use `ghcr.io/graalvm/jdk:ol8-java17` which is a size compact G
     The difference will be more visible if you build a Docker image of the same Spring Boot application containing a JAR file instead of a native executable, and compare images startup times and file sizes. 
 
 On Linux, you can shrink your container size even more.
-With GraalVM Native Image you have the ability to build a statically linked native executable by packaging the native executable directly into an empty Docker image, also known as a scratch container. Continue to [Build a Static or Mostly-Static Native Executable guide](build-static-executable.md) to learn more.
+With GraalVM Native Image you have the ability to build a statically linked native executable by packaging the native executable directly into an empty Docker image, also known as a scratch container. Continue to [Build a Static or Mostly-Static Native Executable guide](build-static-and-mostly-static-executable.md) to learn more.
 
 ### Related Documentation
 
 * [GraalVM Native Image, Spring and Containerisation](https://luna.oracle.com/lab/fdfd090d-e52c-4481-a8de-dccecdca7d68)
 * [GraalVM Community Images](../../../getting-started/graalvm-community/container-images/graalvm-ce-container-images.md)
-* [Build a Static or Mostly-Static Native Executable](build-static-executable.md)
+* [Build a Static or Mostly-Static Native Executable](build-static-and-mostly-static-executable.md)

docs/reference-manual/native-image/guides/use-reachability-metadata-repository-gradle.md

@@ -23,8 +23,6 @@ For the Java application used in this guide the first two approaches are applica
 This guide demonstrates how to build a native executable with the [Tracing agent](#build-a-native-executable-with-the-agent) and using the [GraalVM Reachability Metadata Repository](https://github.com/oracle/graalvm-reachability-metadata).
 The goal is to show users the difference, and prove how using shared metadata can simplify the work.
 
-<!-- [Describe what the demo application is about] -->
-
 We recommend that you follow the instructions and create the application step-by-step. Alternatively, you can go right to the [completed example](https://github.com/graalvm/native-build-tools/tree/master/samples/metadata-repo-integration).
 
 > You must have [GraalVM installed with Native Image support](../README.md#install-native-image). 

docs/tools/vscode/graalvm/README.md

@@ -250,7 +250,7 @@ Your application will:
   * Achieve peak performance with no warmup time
   * Have improved security by reducing attack surfaces and thwarting reverse engineering
 
-Find more information in [Building Native Executables](#building-native-executables) below. 
+Find more information in [Building Native Executables](#debugging-native-executables) below. 
 
 ### Configuration with Tracing Agent
 
@@ -406,4 +406,4 @@ The GraalVM Extension for VS Code recommends the following extensions:
 
 ### Privacy Policy
 
-Read the [Oracle Privacy Policy](https://www.oracle.com/legal/privacy/privacy-policy.html) to learn more.
+Read the [Oracle Privacy Policy](https://www.oracle.com/legal/privacy/privacy-policy.html) to learn more.