From fa02b7a42c6c23b3e5fda0b2bf4968e2a77aff4e Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Thu, 25 Apr 2024 06:32:02 -0600
Subject: [PATCH] Upgrade instructions for model names that contain spaces
 (#5351)

[Preview](https://docs-getdbt-com-git-dbeatty10-patch-1-dbt-labs.vercel.app/docs/dbt-versions/core-upgrade/upgrading-to-v1.8#spaces-in-dbt-model-names)

## What are you changing in this pull request and why?
resolves #5347

## Checklist
- [x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
---
 .../docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
index 6460c210958..73950e78565 100644
--- a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
+++ b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md
@@ -88,6 +88,8 @@ We will begin deprecating support for spaces in dbt model names in v1.8 (raising
 - Spaces in a model name make it impossible to `--select` the model name because the argument gets split into pieces over spaces very early in the pipeline.
 - Most warehouses do not accept a table, or other object, with a space in its name.
 
+To upgrade, replace any spaces in the model file name with an underscore and update any associated YAML that contains the model name to match. You can keep spaces in the database table name by configuring a [custom `alias`](/docs/build/custom-aliases#usage).
+
 ## Quick hits
 
 - [Global config flags](/reference/global-configs/about-global-configs) are deprecated from the [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file and should be moved to the [`dbt_project.yml`](/reference/dbt_project.yml).