From ad707c1271398416cd11ff9a673e0c76b0459bbf Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Wed, 14 Feb 2024 12:00:16 -0700
Subject: [PATCH] Update sl-manifest.md

---
 website/docs/docs/dbt-cloud-apis/sl-manifest.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/dbt-cloud-apis/sl-manifest.md b/website/docs/docs/dbt-cloud-apis/sl-manifest.md
index 03fc35f9c11..ef4e330a38e 100644
--- a/website/docs/docs/dbt-cloud-apis/sl-manifest.md
+++ b/website/docs/docs/dbt-cloud-apis/sl-manifest.md
@@ -19,7 +19,7 @@ dbt creates an [artifact](/reference/artifacts/dbt-artifacts) file called the _S
 
 By using the semantic manifest produced by dbt Core, MetricFlow will instantiate a data flow plan and generate SQL from Semantic Layer query requests. It's a valuable reference that you can use to understand the structure and details of your data models.
 
-Similar to the [`manifest.json` file](/reference/artifacts/manifest-json), the `semantic_manifest.json` file also lives in the [target directory](/reference/project-configs/target-path) of your dbt project. This is where dbt stores various artifacts (such as compiled models and tests) generated during the execution of your project.
+Similar to the [`manifest.json` file](/reference/artifacts/manifest-json), the `semantic_manifest.json` file also lives in the [target directory](/reference/project-configs/target-path) of your dbt project where dbt stores various artifacts (such as compiled models and tests) generated during the execution of your project.
 
 ## How it's produced