Update access_token_error.md (#4949)

## What are you changing in this pull request and why?
Refreshing the docs on access_token error in dbt Cloud

website/docs/faqs/Troubleshooting/access_token_error.md

@@ -1,21 +1,21 @@
 ---
 title: I'm receiving an `access_token` error when trying to run queries in the IDE.
 description: "Reauthenticate warehouse when seeing `access_token` error"
-sidebar_label: '`access_token` error in the IDE'
+sidebar_label: 'Receiving `access_token` error in the IDE'
 id: access_token_error
 
 ---
 
-If you're seeing the below error when you try to run queries in the IDE, have no fear - we'll do our best to get you unstuck with the following steps! 
+If you're seeing a database error labeled `access_token` when you try to run queries in the IDE, this means your [OAuth](/docs/cloud/manage-access/set-up-snowflake-oauth) connection between Snowflake and dbt Cloud has expired.
 
- `access_token`
+To fix this, you'll need to re-connect the two tools.
 
-In order to resolve the issue, you'll want to:
+Your Snowflake administrator can [configure](/docs/cloud/manage-access/set-up-snowflake-oauth#create-a-security-integration) the refresh tokens' validity, which has a maximum 90-day validity period.
 
-1. Go to you Profile (upper right corner of dbt Cloud)
-2. Click on the correct warehouse connection under "Credentials"
-3. Click "Connect Snowflake Account" green button in the "Development Credentials" section. This drives you through reauthentication through the SSO flow. 
-
-If you've tried the step above and are still experiencing this behavior - reach out to the Support team at [email protected] and we'll be happy to help!
+To resolve the issue, complete the following steps:
 
+1. Go to your **Profile settings** page (accessible from the gear icon at the upper right corner of dbt Cloud).
+2. Click on the correct warehouse connection under **Credentials**.
+3. Click the green **Reconnect Snowflake Account** button in the **Development Credentials** section. This drives you through reauthentication through the SSO flow. 
 
+If you've tried the step above and are still experiencing this behavior, reach out to the Support team at [email protected] for further assistance.