From b808953888af8198b1ab7356eff324fa1bfda583 Mon Sep 17 00:00:00 2001 From: Amine BIRANI EL-HBAK <72027309+aminebeh@users.noreply.github.com> Date: Wed, 21 Feb 2024 00:45:50 +0100 Subject: [PATCH] chore(docs): Fix little typo in custom-schemas page --- website/docs/docs/build/custom-schemas.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/build/custom-schemas.md b/website/docs/docs/build/custom-schemas.md index 24cd4194a1c..958f15b8c89 100644 --- a/website/docs/docs/build/custom-schemas.md +++ b/website/docs/docs/build/custom-schemas.md @@ -200,7 +200,7 @@ When using this macro, you'll need to set the target name in your production job In the `generate_schema_name` macro examples shown in the [built-in alternative pattern](#a-built-in-alternative-pattern-for-generating-schema-names) section, the `target.name` context variable is used to change the schema name that dbt generates for models. If the `generate_schema_name` macro in your project uses the `target.name` context variable, you must ensure that your different dbt environments are configured accordingly. While you can use any naming scheme you'd like, we typically recommend: * **dev** — Your local development environment; configured in a `profiles.yml` file on your computer. -* **ci** — A [continuous integration](/docs/cloud/git/connect-github) environment running on pull pequests in GitHub, GitLab, and so on. +* **ci** — A [continuous integration](/docs/cloud/git/connect-github) environment running on pull requests in GitHub, GitLab, and so on. * **prod** — The production deployment of your dbt project, like in dbt Cloud, Airflow, or [similar](/docs/deploy/deployments). If your schema names are being generated incorrectly, double-check your target name in the relevant environment.