[DOCS] Corrected and simplified CTAs for getting customer support

docs/docusaurus/versioned_docs/version-0.18/resources/get_support.md

@@ -8,27 +8,19 @@ Great Expectations (GX) relies on an active user community for its continued suc
 
 ## Try solving your issue first
 
-The following are some recommendations for resolving issues on your own. Resolving issues on your own builds your own knowledge and provides you with an opportunity to share that knowledge with the community. 
+The following are some recommendations for resolving issues on your own. Resolving issues on your own builds your own knowledge and provides you with an opportunity to share that knowledge with the community.
 
 ### Search the GX documentation
 
 Search the docs you're using currently for an answer to your issue or question.
 
 If you're new to GX Cloud, review [About GX Cloud](/cloud/about_gx.md) or [Try GX Cloud](/cloud/try_gx_cloud.md).
 
-If you're new to GX OSS, try the [Quickstart](/oss/tutorials/quickstart.md) or one of the specific getting started guides such as [Get started with Great Expectations and Databricks](/oss/tutorials/getting_started/how_to_use_great_expectations_in_databricks.md), or [Get started with Great Expectations and SQL](/oss/tutorials/getting_started/how_to_use_great_expectations_with_sql.md).  
-
-### Search with your favorite search engine
-
-It's very likely that someone, somewhere has previously encountered or solved the issue you're currently experiencing. Open a browser and perform a keyword search in your preferred search engine to discover resources outside GX documentation. 
-
-### Try it out
-
-If you're wondering what might happen when you implement a solution, try it out! If you attempt a solution in your development environment, users are unaffected and unaware of what you're up to. Sneaky. 
+If you're new to GX OSS, try the [Quickstart](/oss/tutorials/quickstart.md) or one of the specific getting started guides such as [Get started with Great Expectations and Databricks](/oss/tutorials/getting_started/how_to_use_great_expectations_in_databricks.md), or [Get started with Great Expectations and SQL](/oss/tutorials/getting_started/how_to_use_great_expectations_with_sql.md).
 
 ## Ask the right questions and provide the right information
 
-Taking the time to formulate your questions properly and providing all the relevant background information can save time and improve response times. The following are some recommendations that will help the GX Developer Advocates (DAs) and other community members help you. 
+Taking the time to formulate your questions properly and providing all the relevant background information can save time and improve response times. The following are some recommendations that will help the GX Developer Advocates (DAs) and other community members help you.
 
 ### Include all the relevant information
 
@@ -42,24 +34,12 @@ Clearly explain the issue you're experiencing, or the problem you're trying to s
 
 - A detailed explanation of what you're trying to resolve including what attempts you've made on your own to date.
 
-### Don't post in multiple channels and use threads
-
-When posting questions or asking for help in one of the GX Slack channels, don't post in multiple channels. Instead, select a single, relevant channel and post your message there. When responding to a post, use threads. If you need to post large code blocks, post them in a thread to avoid overwhelming the channel.
-
-### Don't tag individual users
+## GX Cloud Support
 
-Even if you've previously developed a rapport with a specific GX DA, or a community member, don't tag them in new Slack posts. GX DA and community member availability varies. Also, the GX DAs operate on a rotation schedule to ensure equal time working with the open source community, and you never know who is available or who has the knowledge to solve your issue. Tagging specific users can limit the scope of the response. Also, the community is typically very responsive and helpful. If you don't get a response within a reasonable time, review your post and ensure you've framed your questions correctly and provided the necessary background information. If you don't get a response, or it's unhelpful, try an alternate medium to resolve your issue.
+- If you've encountered an error you can't resolve, first try creating a new topic on the [GX Discourse - GX Cloud Support](https://discourse.greatexpectations.io/c/oss-support/11) forum. This is the recommended option as answers aren't removed after 90 days, and you're likely to get a quicker response.
+- You can also email us at support@greatexpectations.io or create a ticket on our [support portal](https://support.greatexpectations.io).
 
-## Select the correct medium for questions and support
-
-GX provides the following resources for questions and support:
-
-- If you've encountered an error you can't resolve, get support on the [GX Discourse forum](https://discourse.greatexpectations.io/c/oss-support/11). This is the recommended option as answers aren't removed after 90 days, and you're likely to get a quicker response. GX OSS and GX Cloud specific channels are available. 
-
-- If you want to chat with community members about general issues and solutions, join the [GX Slack community](https://greatexpectationstalk.slack.com/archives/CUTCNHN82). To discuss GX Cloud issues, join the [GX Cloud Slack community](https://greatexpectationstalk.slack.com/archives/C051D941XAL). 
-
-- You can create a ticket on our [support portal](https://support.greatexpectations.io).
+## GX OSS Support
 
+- If you want to chat with community members about general issues and solutions, join the [GX Slack community](https://greatexpectationstalk.slack.com/archives/CUTCNHN82). To discuss GX Cloud issues, join the [GX Cloud Slack community](https://greatexpectationstalk.slack.com/archives/C051D941XAL).
 - If you've found a bug, open an issue in one of the [GX GitHub repositories](https://github.com/great-expectations).
-
-