From 4c4bb5b7ef39a404ea1849d73e3f45dcb927b804 Mon Sep 17 00:00:00 2001
From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
Date: Thu, 21 Dec 2023 14:03:41 -0500
Subject: [PATCH] Update website/docs/docs/cloud/migration.md

Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com>
---
 website/docs/docs/cloud/migration.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/docs/cloud/migration.md b/website/docs/docs/cloud/migration.md
index 0ec9e4c4d26..12b4026ff9f 100644
--- a/website/docs/docs/cloud/migration.md
+++ b/website/docs/docs/cloud/migration.md
@@ -10,7 +10,7 @@ dbt Labs is in the process of migrating dbt Cloud to a new **cell-based architec
 
 There is some preparation required to ensure a successful migration.
 
-Migrations are being scheduled on a per-account basis. _If you have not received any communication (either via a banner or email notification) about a migration date, you do not need to take any action at this time._ dbt Labs will share migration date information with you, with appropriate advance notice, before we complete any migration steps in the dbt Cloud backend.
+Migrations are being scheduled on a per-account basis. _If you haven't received any communication (either with a banner or by email) about a migration date, you don't need to take any action at this time._ dbt Labs will share migration date information with you, with appropriate advance notice, before we complete any migration steps in the dbt Cloud backend.
 
 This document outlines the steps that you must take to prevent service disruptions before your environment is migrated over to the cell-based architecture. This will impact areas such as login, IP restrictions, and API access.