From 0e74ad08cc4d6b3d06e59f1b3009ab1b0081fee7 Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Fri, 3 Nov 2023 20:05:35 +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 99a26d3c954..9ab633c50ad 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#how-to-use-ref) for more information. 
+Like resource dependencies, project dependencies are acyclic, meaning they only move in one direction. This prevents `ref` cycles (or loops), which lead to issues with your data workflows. For example, if project B depends on project A, a new model in project A could not import and use a public model from project B. Refer to [Project dependencies](/docs/collaborate/govern/project-dependencies#how-to-use-ref) for more information. 
 
 ## Define your project interfaces by splitting your DAG