diff --git a/website/docs/docs/build/models.md b/website/docs/docs/build/models.md
index fa2a002a3ef..437996ad655 100644
--- a/website/docs/docs/build/models.md
+++ b/website/docs/docs/build/models.md
@@ -6,7 +6,7 @@ pagination_next: "docs/build/sql-models"
 pagination_prev: null
 ---
 
-dbt Core and Cloud are composed of different moving parts working harmoniously. All of them are important to what dbt does — transforming data—the 'T' in ELT. When you execute `dbt run`, you are running a model that will transform your data without that data ever leaving your warehouse.
+dbt Core and Cloud are composed of different moving parts working harmoniously. All of them are important to what dbt does — transforming data—the 'T' in ETL. When you execute `dbt run`, you are running a model that will transform your data without that data ever leaving your warehouse.
 
 Models are where your developers spend most of their time within a dbt environment. Models are primarily written as a `select` statement and saved as a `.sql` file. While the definition is straightforward, the complexity of the execution will vary from environment to environment.  Models will be written and rewritten as needs evolve and your organization finds new ways to maximize efficiency.