From 0d8f0745a41128e67a3d649c73c4eb0c377808bc Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Tue, 12 Nov 2024 15:45:35 +0000
Subject: [PATCH] Update
 website/docs/reference/global-configs/behavior-changes.md

Co-authored-by: nataliefiann <120089939+nataliefiann@users.noreply.github.com>
---
 website/docs/reference/global-configs/behavior-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/reference/global-configs/behavior-changes.md b/website/docs/reference/global-configs/behavior-changes.md
index 6b9a16f43d..b3162c6478 100644
--- a/website/docs/reference/global-configs/behavior-changes.md
+++ b/website/docs/reference/global-configs/behavior-changes.md
@@ -174,4 +174,4 @@ Set the flag is set to `True` if you have a custom microbatch macro set up in yo
 
 If you have a custom microbatch macro and the flag is left as `False`, dbt will issue a deprecation warning.
 
-Previously, users needed to set the `DBT_EXPERIMENTAL_MICROBATCH` environment variable to `True` to prevent unintended interactions with existing custom incremental strategies. But this is no longer necessary, and setting `DBT_EXPERMINENTAL_MICROBATCH` will no longer have an effect on runtime functionality.
+Previously, users needed to set the `DBT_EXPERIMENTAL_MICROBATCH` environment variable to `True` to prevent unintended interactions with existing custom incremental strategies. But this is no longer necessary, as setting `DBT_EXPERMINENTAL_MICROBATCH` will no longer have an effect on runtime functionality.