From df5e1cafd38869151e85422509106cfe80eae9d5 Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Fri, 29 Sep 2023 16:51:13 +0100
Subject: [PATCH] Update
 website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md

---
 .../docs/guides/dbt-ecosystem/sl-partner-integration-guide.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md
index 6fba399512d..b0718a6484d 100644
--- a/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md
+++ b/website/docs/guides/dbt-ecosystem/sl-partner-integration-guide.md
@@ -114,7 +114,7 @@ For better analysis, it's best to have the context of the metrics close to where
 These are recommendations on how to evolve a Semantic Layer integration and not a strict runbook.
 
 **Stage 1 - The basic**
-* Supporting and using the new [JDBC](/docs/dbt-cloud-apis/sl-jdbc) is the first step. Refer to the [dbt Semantic Layer APIs](/docs/dbt-cloud-apis/sl-api-overview) for more technical details. 
+* Supporting and using the new [JDBC](/docs/dbt-cloud-apis/sl-jdbc) or [GraphQL](/docs/dbt-cloud-apis/sl-graphql) is the first step. Refer to the [dbt Semantic Layer APIs](/docs/dbt-cloud-apis/sl-api-overview) for more technical details. 
 
 **Stage 2 - More discoverability and basic querying**
 * Support listing metrics defined in the project