Snowflake key pair auth now available for free and team tiers

src/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup.md

@@ -10,7 +10,7 @@ Set up Snowflake as your Reverse ETL source.
 At a high level, when you set up Snowflake for Reverse ETL, the configured user/role needs read permissions for any resources (databases, schemas, tables) the query needs to access. Segment keeps track of changes to your query results with a managed schema <br>(`__SEGMENT_REVERSE_ETL`), which requires the configured user to allow write permissions for that schema.
 
 > success ""
-> Segment now supports key-pair authentication for Snowflake Reverse ETL sources. Key-pair authentication is available for Business Tier users only.
+> Segment now supports key-pair authentication for Snowflake Reverse ETL sources.
 
 > info "Snowflake Reverse ETL sources support Segment's dbt extension"
 > If you have an existing dbt account with a Git repository, you can use [Segment's dbt extension](/docs/segment-app/extensions/dbt/) to centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes.

src/connections/storage/catalog/snowflake/index.md

@@ -91,9 +91,6 @@ GRANT CREATE SCHEMA ON DATABASE "SEGMENT_EVENTS" TO ROLE "SEGMENT";
 
 Create the user that Segment uses to connect to your warehouse. You can create a user that authenticates with a key pair, or you can create a user that authenticates using a password. For enhanced security, Segment recommends creating a user that authenticates with an encrypted key pair.
 
-> info "Key-pair authentication restricted to Business Tier users only"
-> Users on other plans can authenticate with Snowflake using a [username and password](#create-a-user-that-authenticates-with-a-username-and-password).
-
 #### Create a user that authenticates with a key pair
 If you are creating a user that will use a key pair to authenticate, you first must create a public key and then can create a new user. 
 
@@ -264,7 +261,7 @@ At this time, the Segment Snowflake destination is not compatible with Snowflake
 
 Segment recommends that you authenticate with your Snowflake warehouse using an encrypted key pair. Key-pair authentication uses PKCS#8 private keys, which are typically exchanged in the PEM base64-encoded format. 
 
-Although you can create up to two keys in Snowflake, Segment only supports authenticating with one key at a time. To change the key that is in Segment, return to your Snowflake destination's settings and upload a new key in the **Private Key** field.
+Although you can create up to two keys in Snowflake, Segment only supports authenticating with one key at a time. To change the key that's used to authenticate with Segment, return to your Snowflake destination's settings and upload a new key in the **Private Key** field.
 
 ### Auto Suspend and Auto Resume
 

src/unify/data-graph/setup-guides/snowflake-setup.md

@@ -156,7 +156,7 @@ To connect your warehouse to the Data Graph:
 - **Username**: The Snowflake user that Segment uses to run SQL in your warehouse. This user is referred to as `segment_connection_username` in the script below
 - **Authentication**: There are 2 supported authentication methods:
   - **Key Pair**: This is the recommended method of authentication. You would need to first create the user and assign it a key pair following the instructions in the [Snowflake docs](https://docs.snowflake.com/en/user-guide/key-pair-auth){:target="_blank"}. Then, follow the Segment docs above to set up Snowflake permissions and set the `segment_connections_username` variable in the SQL script to the user you just created
-  - **Password**: The password of the user above. This password is referred to as `segment_connection_password` in the script below.
+  - **Password**: The password of the user above. This password is referred to as `segment_connection_password` in the script below
 
 5. Test your connection, then click Save.