The --empty flag

[matthewshaver]

What are you changing in this pull request and why?

Updates the run and build command references to include the --empty flag.

Checklist

Uncomment when publishing docs for a prerelease version of dbt:

• Add versioning components, as described in Versioning Docs

• Add a note to the prerelease version Migration Guide

• Review the Content style guide so my content adheres to these guidelines.

• For docs versioning, review how to version a whole page and version a block of content.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 26, 2024 4:27pm

[MichelleArk]

dbt will build the project and models, parse the files to identify changes, but won't actually execute the SQL against the target data warehouse.

I don't think this is technically correct. Perhaps:
"dbt will still execute the model SQL against the target data warehouse, but will avoid expensive reads of input data. This ensures your models will build properly and validates dependencies."

[mirnawong1]

lgtm and since it's approved already, only non blocker that i think will be helpful for users is adding a 'why is this useful or important in the 'build' and 'run' pages:

This validates dependencies and ensures your models will build properly. Using the --empty flag enhances performance and helps with warehouse costs (not sure if that's right?)