removed trailing slashes

docs/airgapped-docs/introduction.md

@@ -8,7 +8,7 @@ As our product is still at Initial Operation Capability (IOC), there are some ex
 
 - Installation and packaging is still in progress and improving.
 
-If you see issues and areas for improvement, please submit Github issues [here](https://github.com/rancherfederal/carbide-charts/issues/).
+If you see issues and areas for improvement, please submit Github issues [here](https://github.com/rancherfederal/carbide-charts/issues).
 
 ## What is this?
 

docs/intro.md

@@ -8,10 +8,10 @@ Carbide is Rancher Government's hardened distribution of the SUSE Rancher produc
 
 Rancher Carbide is tactically built with the following enhancements over the community version:
 
-- [SLSA 3 compliant](https://slsa.dev/) secure build process hosted on Azure Government
+- [SLSA 3 compliant](https://slsa.dev) secure build process hosted on Azure Government
 - Digitally Signed Container Images. Every container hosted in our registry has been digitally [signed](https://rancherfederal.github.io/carbide-docs/docs/registry-docs/validating-images) by Rancher Government Solutions. Verifiable trust is baked into everything we do.
 - [Software Bill of Materials](https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwiW0KSchfL5AhWPkIkEHf6QASQQFnoECAkQAQ&url=https%3A%2F%2Fwww.cisa.gov%2Fsbom&usg=AOvVaw2_RntIRhhNuizqtvNQxmyP) (SBOM) support in every container image
-- Container [Attestations](https://www.testifysec.com/blog/what-is-a-supply-chain-attestation/)
+- [Container Attestations](https://www.testifysec.com/blog/what-is-a-supply-chain-attestation)
 - Container Vulnerability Scans
 - Authenticated Registry hosted on Azure Government Container Registry
 - STIGATRON: Day 2 security operator powered by Rancher Government's DISA STIGs

docs/registry-docs/introduction.md

@@ -9,7 +9,7 @@ As our product is still in the IOC phase, there are some expectations to level-s
 
 **DISCLAIMER**:  The Secured Registry (rgcrprod.azurecr.us) is _not_ intended to be used as the primary registry for running Kubernetes clusters. It is only intended as the acquisition point to obtain the Carbide secured images. Customers should seed their own private OCI registries, and use that registry for their Kubernetes clusters.
 
-If you see issues and areas for improvement, please submit Github issues [here](https://github.com/rancherfederal/carbide-docs/issues/).
+If you see issues and areas for improvement, please submit Github issues [here](https://github.com/rancherfederal/carbide-docs/issues).
 
 ## What is this?
 Here at Rancher Government Solutions, we take the security of our products seriously.  Products like `rke2` are tailor built to address the "secure by default" needs of the federal government, while still maintaining the same ease of deployments that our users have come to love from Rancher products.

docs/registry-docs/prereqs.md

@@ -17,7 +17,7 @@ The Carbide Secured Registry (rgcrprod.azurecr.us) is _not_ intended to be used
 curl -sfL https://get.hauler.dev | bash
 ```
 
-**Supply Chain Tool: [cosign](https://docs.sigstore.dev/)**
+**Supply Chain Tool: [cosign](https://docs.sigstore.dev)**
 
 ```bash
 # example installation steps
@@ -28,7 +28,7 @@ sudo mv cosign-linux-amd64 /usr/local/bin/cosign
 sudo chmod 755 /usr/local/bin/cosign
 ```
 
-**Container Tool: [helm](https://helm.sh/docs/)**
+**Container Tool: [helm](https://helm.sh/docs)**
 
 ```bash
 # example installation steps

docs/registry-docs/rancher-config.md

@@ -118,7 +118,7 @@ configs:
 
 ### Usage with `Rancher`
 
-Follow Rancher's [Installation Guide](https://rancher.com/docs/rancher/v2.5/en/installation/install-rancher-on-k8s/), adding in the following steps to use our [Carbide Helm Chart](https://github.com/rancherfederal/carbide-charts) and the `helm install` command.
+Follow Rancher's [Installation Guide](https://rancher.com/docs/rancher/v2.5/en/installation/install-rancher-on-k8s), adding in the following steps to use our [Carbide Helm Chart](https://github.com/rancherfederal/carbide-charts) and the `helm install` command.
 
 When installing Rancher, to utilize the private registry, you'll need to set the following values in your Helm values:
 

docs/registry-docs/uninstall-rancher.md

@@ -62,7 +62,7 @@ See the [RKE2/K3s Uninstall](uninstall-kubernetes.md) documentation.
 
 ### Reverting `Rancher` Chart
 
-Follow Rancher's [Installation Guide](https://rancher.com/docs/rancher/v2.7/en/installation/install-rancher-on-k8s/), you can revert to using DockerHub images by removing values from the Helm upgrade command.
+Follow Rancher's [Installation Guide](https://rancher.com/docs/rancher/v2.7/en/installation/install-rancher-on-k8s), you can revert to using DockerHub images by removing values from the Helm upgrade command.
 
 ```bash
 helm upgrade rancher rancher-latest/rancher \

docs/stigatron-docs/introduction.md

@@ -8,7 +8,7 @@ As our product is still at Initial Operation Capability (IOC), there are some ex
 
 - Installation and packaging is still in progress and improving.
 
-If you see issues and areas for improvement, please submit Github issues [here](https://github.com/rancherfederal/carbide-charts/issues/).
+If you see issues and areas for improvement, please submit Github issues [here](https://github.com/rancherfederal/carbide-charts/issues).
 
 ## What is this?