From 4d39385226099c2c20eedea4a82cca410e307031 Mon Sep 17 00:00:00 2001
From: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
Date: Fri, 20 Sep 2024 13:38:55 +0100
Subject: [PATCH] Update
 website/docs/reference/resource-properties/constraints.md

Co-authored-by: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
---
 website/docs/reference/resource-properties/constraints.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/website/docs/reference/resource-properties/constraints.md b/website/docs/reference/resource-properties/constraints.md
index aae537b1bff..6fad45fa02a 100644
--- a/website/docs/reference/resource-properties/constraints.md
+++ b/website/docs/reference/resource-properties/constraints.md
@@ -88,7 +88,6 @@ The structure of a constraint is:
 
 In [dbt Cloud Versionless](/docs/dbt-versions/upgrade-dbt-version-in-cloud#versionless), you can use the improved syntax to define foreign keys, which uses `ref`. This feature will be available in the upcoming 1.9 release. The recommended syntax means:
 
-### What's better about this syntax?
 
 dbt automatically resolves references to other models, ensuring they: