From 6b152a4905ce4b8d212519e3fff4ff99dbaf7e50 Mon Sep 17 00:00:00 2001
From: Michael Borland <98965906+mkborland@users.noreply.github.com>
Date: Mon, 7 Oct 2024 16:35:18 -0500
Subject: [PATCH] fix: broken hyperlink in guide.md (#272)

---
 docs/uds-packages/guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/uds-packages/guide.md b/docs/uds-packages/guide.md
index 4812ff1e..896c4896 100644
--- a/docs/uds-packages/guide.md
+++ b/docs/uds-packages/guide.md
@@ -58,7 +58,7 @@ Your goal is to integrate the Zarf package application with [UDS Core](https://g
 
 - [ ] If you haven't already, read the docs on [UDS Operator](https://uds.defenseunicorns.com/core/configuration/uds-operator/)
 
-- [ ] [UDS Package Practices](https://github.com/defenseunicorns/uds-common/blob/main/docs/uds-package-practices.md) provides an extensive list of best practices, considerations, and tasks for a package to be "Made for UDS"
+- [ ] [UDS Package Practices](https://github.com/defenseunicorns/uds-common/blob/main/docs/uds-packages/requirements/uds-package-requirements.md) provides an extensive list of best practices, considerations, and tasks for a package to be "Made for UDS"
 
 #### Checkout
 Your repository has a `uds-package.yaml` manifest added to the appropriate helm chart and you can deploy to a K3d Core Dev Slim cluster, via zarf package.