fixes broken links

Author: paulsavoie

docs/artifact-configuration/reference.md

@@ -623,7 +623,7 @@ Use cases for raw signatures include:
 
 * Signing for lightweight verification, e.g. on embedded systems 
 * Creating signature blocks for subsequent use with other tools and formats
-* [Signing _Cosign_ metadata files](/signing-containers/cosign)
+* [Signing _Cosign_ metadata files](/signing-containers#cosign)
 
 Raw signing is a [detached](#detached-signing-methods) signing method and must be used in `<zip-file>` elements.
 
@@ -751,7 +751,7 @@ The restrictions can be applied to file elements, [file set elements](syntax#fil
 
 ## SLSA attestations {#create-provenance-file}
 
-SignPath can create SLSA attestations for any of the supported build systems. See the [definition](/origin-verification/slsa-attestations) for more details.
+SignPath can create SLSA attestations for any of the supported build systems. See the [definition](/slsa-attestations) for more details.
 
 Creating a SLSA attestation requires multiple directives:
 

docs/crypto-providers/notation.md

@@ -68,7 +68,7 @@ See [SignPath Crypto Providers](/crypto-providers/#crypto-provider-configuration
 
 ### Usage
 
-* The available [configuration values](/documentation/crypto-providers#crypto-provider-configuration) can also be passed in via the command line arguments `--plugin-config "Key=<Value>"`. 
+* The available [configuration values](/crypto-providers#crypto-provider-configuration) can also be passed in via the command line arguments `--plugin-config "Key=<Value>"`. 
 * The notation _key id_ is comprised of the _project slug_ and _signing policy slug_, separated by a forward slash, e.g. `"MyProject/release-signing"`
 
 {% raw %}

docs/origin-verification/index.md

@@ -31,7 +31,7 @@ Verification of reproducability depends on the CI system used. Typical verificat
 * **No manual overrides** of critical build settings in CI system's build job
 * **Prevent caching** from previous (possibly unverified) builds
 
-In order to use origin verification, a [Trusted Build System](trusted-build-systems) must be configured and linked to the project.
+In order to use origin verification, a [Trusted Build System](/trusted-build-systems) must be configured and linked to the project.
 
 {:.panel.tip}
 > **Use origin verification restrictions**

docs/signing-containers/docker-content-trust.md

@@ -9,7 +9,7 @@ description: Documentation for signing Docker images with SignPath using Docker
 {:.panel.warning}
 > **Docker Content Trust (DCT) is deprecated**
 >
-> Docker Content Trust (DCT) is deprecated. Please consider using [Notary (Notation)](/signing-containers/notation) (recommended for Enterprises) or [Cosign](/signing-containers/cosign) (recommended for OSS projects).
+> Docker Content Trust (DCT) is deprecated. Please consider using [Notary (Notation)](/signing-containers#notation) (recommended for Enterprises) or [Cosign](/signing-containers#cosign) (recommended for OSS projects).
 
 ## Overview