docs: Trim support email from Platform docs

sources/platform/actors/publishing/testing.mdx

@@ -29,7 +29,7 @@ passes the majority of test runs in the next 7 days, it will be marked as health
 ## What if my Actor cannot comply with the test logic
 
 Actors that require some sort of authentication will always fail the tests despite being fully functional. Also, some Actors inherently run for longer than 5 minutes.
-If that's the case with your Actor, please contact support at [support@apify.com](mailto:support@apify.com) and explain your specific use case that justifies why the Actor should be excluded from the automated tests.
+If that's the case with your Actor, [contact support](http://apify.com/contact) and explain your specific use case that justifies why the Actor should be excluded from the automated tests.
 
 ## Advanced Actor testing
 

sources/platform/collaboration/organization_account/index.md

@@ -61,4 +61,4 @@ For information on [adding members and assigning roles](./setup.md), see the Set
 
 Actor and task runs are billed to the account they are started from. **Always make sure you start your runs from the correct account** to avoid having an organization's runs billed to your personal account.
 
-To find out about organization pricing, get in touch at [support@apify.com](mailto:support@apify.com?subject=Organization%20account%20pricing) or [visit the pricing page](https://apify.com/pricing).
+To learn about organization pricing, [contact support](http://apify.com/contact) or [visit the pricing page](https://apify.com/pricing).

sources/platform/integrations/actors/integration_ready_actors.md

@@ -87,8 +87,8 @@ In the above example, we're focusing on accessing a run's default dataset, but t
 
 To allow other users to use your Actor as an integration, all you need to do is [publish it in Apify Store](/platform/actors/publishing), so users can then integrate it using the **Connect Actor or task** button on the **Integrations** tab of any Actor. While publishing the Actor is enough, there are two ways to make it more visible to users.
 
-For Actors that are generic enough to be used with most other Actors, it's possible to have them listed under **Generic integrations** in the **Integrations** tab. This includes (but is not limited to) Actors that upload datasets to databases, send notifications through various messaging systems, create issues in ticketing systems, etc. To have your Actor listed under the generic integrations, [contact support](mailto:support@apify.com?subject=Actor%20generic%20integration).
+For Actors that are generic enough to be used with most other Actors, it's possible to have them listed under **Generic integrations** in the **Integrations** tab. This includes (but is not limited to) Actors that upload datasets to databases, send notifications through various messaging systems, create issues in ticketing systems, etc. To have your Actor listed under the generic integrations, [contact support](http://apify.com/contact).
 
-Some Actors can only be integrated with a few or even just one other Actor. Let's say that you have an Actor that's capable of scraping profiles from a social network. It makes sense to show it for Actors that produce usernames from the social network but not for Actors that produce lists of products. In this case, it's possible to have the Actor listed as **Specific to this Actor** under the Actor's **Integrations** tab. To have your Actor listed as specific to another Actor, [contact support](mailto:support@apify.com?subject=Actor%specific%20integration).
+Some Actors can only be integrated with a few or even just one other Actor. Let's say that you have an Actor that's capable of scraping profiles from a social network. It makes sense to show it for Actors that produce usernames from the social network but not for Actors that produce lists of products. In this case, it's possible to have the Actor listed as **Specific to this Actor** under the Actor's **Integrations** tab. To have your Actor listed as specific to another Actor, [contact support](http://apify.com/contact).
 
 ![Specific vs generic integrations](./images/specific_vs_generic_integrations.png)