From 0f159674e1987836c4ffea9e1b48e1c245963462 Mon Sep 17 00:00:00 2001
From: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
Date: Tue, 16 Jul 2024 14:18:48 +0100
Subject: [PATCH] Update website/docs/guides/customize-schema-alias.md

---
 website/docs/guides/customize-schema-alias.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/guides/customize-schema-alias.md b/website/docs/guides/customize-schema-alias.md
index 9a327c4f085..dbbfaaefd66 100644
--- a/website/docs/guides/customize-schema-alias.md
+++ b/website/docs/guides/customize-schema-alias.md
@@ -74,7 +74,7 @@ In dbt Cloud, we recommend environment variables as they can be set at the envir
 - Or as an alternative to environment variables, you can use `target.name`. For more information, you can refer to [About target variables](/reference/dbt-jinja-functions/target). 
 
 
-<Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/custom-schema-env-var-targetname.png" title="Custom schema environmental variables target name." />
+<Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/Environment Variables/custom-schema-env-var.png" title="Custom schema environmental variables target name." />
 
 To allow the database/schema/object name to depend on the current branch, you can use the out of the box `DBT_CLOUD_GIT_BRANCH` environment variable in dbt Cloud [special environment variables](/docs/build/environment-variables#special-environment-variables).