Apply suggestions from code review

Co-authored-by: Ly Nguyen <[email protected]>

website/docs/reference/global-configs/adapter-behavior-changes.md

@@ -9,7 +9,7 @@ pagination_prev: null
 ---
 
 
-Some adapters may show behavior changes when certain flags are enabled. Refer to the following sections for each respective adapter.
+Some adapters can display behavior changes when certain flags are enabled. The following sections contain details about these adapter-specific behavior changes. 
 
 
 <div className="grid--3-col">

website/docs/reference/global-configs/redshift-changes.md

@@ -1,11 +1,11 @@
 ---
-title: "Redshift adapter behavior changes"
+title: "Amazon Redshift adapter behavior changes"
 id: "redshift-changes"
 sidebar: "Redshift"
 ---
 
-## restrict_direct_pg_catalog_access
+## The restrict_direct_pg_catalog_access flag
 
-Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter and used Postgres tables for metadata access. With this flag enabled, the adapter will use the Redshift API (through the Python client) if available, or query Redshift's `information_schema` tables instead of using `pg_` tables.
+Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter and used Postgres tables for metadata access. When this flag is enabled, the adapter uses the Redshift API (through the Python client) if available, or queries Redshift's `information_schema` tables instead of using the `pg_` tables.
 
-While we don't expect any user-noticeable behavior changes due to this change, out of caution we are gating it behind a behavior-change flag and encouraging users to test it before it becomes the default for everyone.
+While you shouldn't notice any behavior changes due to this change, however, to be cautious dbt Labs is gating it behind a behavior-change flag and encouraging you to test it before it becoming the default.