fixing links

site/linkinator.config.json

@@ -1,4 +1,4 @@
 {
-  "skip": "https.*",
+  "skip": "^(https://.*github.com)",
   "verbosity": "error"
 }

site/package.json

@@ -13,8 +13,7 @@
     "build": "rm -rf dist && astro check && astro build",
     "preview": "astro preview",
     "astro": "astro",
-    "link-check": "linkinator --recurse dist/ --config linkinator.config.json",
-    "linkinator": "linkinator"
+    "link-check": "linkinator --recurse dist/ --config linkinator.config.json"
   },
   "dependencies": {
     "@astrojs/check": "^0.5.10",

site/src/content/docs/ref/tools.mdx

@@ -38,7 +38,7 @@ Zarf vendors in [Syft](https://github.com/anchore/syft), a "CLI tool and library
 
 ## k9s
 
-> command: [`zarf tools k9s`](/commands/zarf_tools_k9s)
+> command: [`zarf tools k9s`](/commands/zarf_tools_monitor)
 >
 > aliases: `k9s`, `monitor`, `m`
 

site/src/content/docs/tutorials/7-publish-and-deploy.mdx

@@ -18,7 +18,7 @@ In this tutorial, we are going to run through how to publish a Zarf package to a
 For following along locally, please ensure the following prerequisites are met:
 
 - Zarf binary installed on your `$PATH`: ([Installing Zarf](/getting-started/install/))
-- Access to a [Registry supporting the OCI Distribution Spec](https://oras.land/implementors/#registries-supporting-oci-artifacts), this tutorial will be using Docker Hub
+- Access to a [Registry supporting the OCI Distribution Spec](https://oras.land/docs/compatible_oci_registries#registries-supporting-oci-artifacts), this tutorial will be using Docker Hub
 - Access to a cluster that has been [initialized with zarf](/tutorials/1-initializing-a-k8s-cluster/).
 
 ## Working with OCI Packages
@@ -128,7 +128,7 @@ You attempted to publish a package with no version metadata.
 <iframe src="/tutorials/troubleshoot_version_required_no_version.html" width="100%" height="300px"></iframe>
 
 1. Open the zarf.yaml file.
-2. Add a version attribute to the [package metadata](https://docs.zarf.dev/docs/user-guide/zarf-schema#metadata)
+2. Add the version attribute to the package metadata.
 3. Recreate the package with the `zarf package create` command.
 4. Publish the package.  The filename will now have the version as part of it.