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 17f0970a769..99a26d3c954 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. 
+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