From 2007ba3dcd4bc7155fe5879da324b9fd559388a4 Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Fri, 3 Nov 2023 19:21:57 +0000
Subject: [PATCH] Update
 website/docs/guides/best-practices/how-we-mesh/mesh-2-structures.md

---
 .../docs/guides/best-practices/how-we-mesh/mesh-2-structures.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/guides/best-practices/how-we-mesh/mesh-2-structures.md b/website/docs/guides/best-practices/how-we-mesh/mesh-2-structures.md
index 24dc94a6e3d..17f0970a769 100644
--- a/website/docs/guides/best-practices/how-we-mesh/mesh-2-structures.md
+++ b/website/docs/guides/best-practices/how-we-mesh/mesh-2-structures.md
@@ -20,7 +20,7 @@ At a high level, you’ll need to decide:
 
 ### Cycle detection
 
-Currently, project dependencies only work in a one-way direction. This helps you avoid indefinite project `ref` cycles (or loops) and issues with your data workflows. For example, the `jaffle_finance"` project can't introduce a new model that depends on `jaffle_marketing.roi_by_channel`. Refer to [Project dependencies](/docs/collaborate/govern/project-dependencies#:~:text=...-,Cycle%20detection%3A,-Currently%2C%20%22project%22%20dependencies) for more information. 
+Currently, project dependencies only work in a one-way direction. This helps you avoid indefinite project `ref` cycles (or loops) and issues with your data workflows. For example, the `jaffle_finance"` project can't introduce a new model that depends on `jaffle_marketing.roi_by_channel`. Refer to [Project dependencies](/docs/collaborate/govern/project-dependencies#how-to-use-ref) for more information. 
 
 ## Define your project interfaces by splitting your DAG