From 576dcd49236fdf07d9fa5a5cdfe77e90428b1814 Mon Sep 17 00:00:00 2001
From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com>
Date: Fri, 25 Oct 2024 12:15:57 -0700
Subject: [PATCH] Apply suggestions from code review

---
 website/snippets/_state-modified-compare.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/snippets/_state-modified-compare.md b/website/snippets/_state-modified-compare.md
index 35a8bb72616..c7bba1c8bdf 100644
--- a/website/snippets/_state-modified-compare.md
+++ b/website/snippets/_state-modified-compare.md
@@ -1,3 +1,3 @@
-The state directory needs to be built with dbt v1.9 or higher, or [Versionless](/docs/dbt-versions/versionless-cloud) dbt Cloud along with setting `state_modified_compare_more_unrendered_values` to true within your dbt_project.yml.
+You need to build the state directory using dbt v1.9 or higher, or [Versionless](/docs/dbt-versions/versionless-cloud) dbt Cloud, and you need to set `state_modified_compare_more_unrendered_values` to `true` within your dbt_project.yml.
 
-If the state directory is built with an older dbt version or if the `state_modified_compare_more_unrendered_values` behavior change flag was either not set or set to `false`, you need to rebuild the state directory to avoid false positives during state comparison with `state:modified`.
+If the state directory was built with an older dbt version or if the `state_modified_compare_more_unrendered_values` behavior change flag was either not set or set to `false`, you need to rebuild the state directory to avoid false positives during state comparison with `state:modified`.