linter fixes

Author: fhennig

modules/guides/pages/enabling-verification-of-image-signatures.adoc

@@ -94,4 +94,4 @@ There's a lot more to learn about how keyless signing and verification works. We
 * https://docs.sigstore.dev/signing/overview/
 * https://docs.sigstore.dev/policy-controller/overview/
 * https://www.chainguard.dev/unchained/life-of-a-sigstore-signature
-* https://blog.sigstore.dev/why-you-cant-use-sigstore-without-sigstore-de1ed745f6fc/
+* https://blog.sigstore.dev/why-you-cant-use-sigstore-without-sigstore-de1ed745f6fc/

modules/guides/pages/viewing-and-verifying-sboms.adoc

@@ -77,4 +77,4 @@ kubectl label namespace stackable policy.sigstore.dev/include=true
 ----
 
 The Policy Controller checks all newly created Pods in this namespace that run any image matching `+++**+++.stackable.tech/+++**+++` (this matches images provided by Stackable) and ensures that these images have an attested SBOM that's been signed by a Stackable Github Action. If no SBOM is present or its signature is invalid or missing, the policy will deny the pod creation.
-For a more detailed explanation of the policy options, please refer to the https://docs.sigstore.dev/policy-controller/overview/#configuring-image-patterns[Sigstore documentation].
+For a more detailed explanation of the policy options, please refer to the https://docs.sigstore.dev/policy-controller/overview/#configuring-image-patterns[Sigstore documentation].