Rewrite "here" links in the docs

Use descriptive link texts instead.

Signed-off-by: Tom Wieczorek <[email protected]>

Author: twz123

docs/contributors/testing.md

@@ -27,8 +27,8 @@ Please run the following style and formatting commands and fix/check-in any chan
 
 3. Checking the documentation
 
-   Verify any changes to the documentation by following the instructions
-   [here](docs.md#testing-docs-locally).
+   Follow the [instructions for testing the documentation
+   locally][testing-docs-locally] to verify any changes.
 
 4. Pre-submit Flight Checks
 
@@ -50,6 +50,8 @@ Please run the following style and formatting commands and fix/check-in any chan
 
    If you find that all tests passed, you may open a pull request upstream.
 
+[testing-docs-locally]: docs.md#testing-docs-locally
+
 ## Opening A Pull Request
 
 ### Draft Mode

docs/examples/ambassador-ingress.md

@@ -2,7 +2,9 @@
 
 You can configure k0s with the [Ambassador API Gateway](https://www.getambassador.io/products/api-gateway/) and a [MetalLB service loadbalancer](https://metallb.universe.tf/). To do this you leverage Helm's extensible bootstrapping functionality to add the correct extensions to the `k0s.yaml` file during cluster configuration.
 
-Note: Currently Ambassador API Gateway does not support Kubernetes v1.22 or above. See [here](https://github.com/emissary-ingress/emissary/issues/3735#issuecomment-916278895) for details.
+Note: Currently Ambassador API Gateway does not support Kubernetes v1.22 or
+above. See [this comment on emissary-ingress/emissary#3735](https://github.com/emissary-ingress/emissary/issues/3735#issuecomment-916278895)
+for details.
 
 ## Use Docker for non-native k0s platforms
 

docs/runtime.md

@@ -219,7 +219,10 @@ helm install nvidia-gpu-operator -n nvidia-gpu-operator \
 
 With this Helm chart values, NVIDIA GPU operator will deploy both driver and toolkit to the GPU nodes and additionally will configure containerd with NVIDIA specific runtime.
 
-**Note**: Detailed instruction on how to deploy NVIDIA GPU operator on your k0s cluster is available [here](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/getting-started.html).
+**Note**: Detailed installation instructions can be found in the [official
+NVIDIA GPU Operator documentation][install-nvidia-gpu-operator].
+
+[install-nvidia-gpu-operator]: https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/getting-started.html
 
 ## Using custom CRI runtimes
 

docs/system-requirements.md

@@ -62,8 +62,9 @@ For information on the required ports and protocols, refer to [networking](netwo
 
 ## External runtime dependencies
 
-k0s strives to be as independent from the OS as possible. The current and past
-external runtime dependencies are documented [here](external-runtime-deps.md).
+k0s strives to be as independent from the operating system as possible. See the
+dedicated section on [external runtime dependencies](external-runtime-deps.md)
+for details on current and past requirements.
 
 To run some automated compatiblility checks on your system, use
 [`k0s sysinfo`](cli/k0s_sysinfo.md).

hack/ostests/README.md

@@ -44,8 +44,9 @@ export AWS_SESSION_TOKEN=...
 export AWS_REGION=...
 ```
 
-Select the desired cluster configuration for OpenTofu. Again, just an example,
-other ways described [here][tf-config].
+Select the desired cluster configuration for OpenTofu. This is just one example;
+other methods of passing configuration options are covered in the [official
+OpenTofu documentation][tf-config].
 
 ```shell
 export TF_VAR_os=alpine_3_21