From e5b56bdaca329f188dffa600703698c31b4d6f3d Mon Sep 17 00:00:00 2001
From: UncleGedd <42304551+UncleGedd@users.noreply.github.com>
Date: Thu, 14 Jul 2022 09:27:46 -0500
Subject: [PATCH] fixes link in docs

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

diff --git a/docs/4-user-guide/2-zarf-packages/1-zarf-packages.md b/docs/4-user-guide/2-zarf-packages/1-zarf-packages.md
index 3e19a977c9..5e56d195d1 100644
--- a/docs/4-user-guide/2-zarf-packages/1-zarf-packages.md
+++ b/docs/4-user-guide/2-zarf-packages/1-zarf-packages.md
@@ -80,7 +80,7 @@ Zarf packages are split into smaller chunks called 'components'. These component
 
 :::
 
-The process of defining a package is covered in the [Creating Your Own Package](https://google.com) page. Assuming you have a package already defined, building the package itself is fairly simple.
+The process of defining a package is covered in the [Creating Your Own Package](../../13-walkthroughs/0-creating-a-zarf-package.md) page. Assuming you have a package already defined, building the package itself is fairly simple.
 
 `zarf package create` will look for a `zarf.yaml` file in the current directory and build the package from that file. Behind the scenes, this is pulling down all the resources it needs from the internet and placing them in a temporary directory, once all the necessary resources of retrieved, Zarf will create the tarball of the temp directory and clean up the temp directory.