diff --git a/docs/organization/integrations/integration-platform/public-integration.mdx b/docs/organization/integrations/integration-platform/public-integration.mdx
index e49164e22a039f..d0a0cb941c17e2 100644
--- a/docs/organization/integrations/integration-platform/public-integration.mdx
+++ b/docs/organization/integrations/integration-platform/public-integration.mdx
@@ -66,7 +66,7 @@ All public integrations can be installed via a fixed external url: `https://sent
 Public integrations generate [authentication tokens](/organization/integrations/integration-platform/#auth-tokens) after a successful [OAuth installation](#oauth-process).
 These tokens automatically expire every eight hours, meaning they must be refreshed manually.
 
-### Refreshing Tokens via Refresh Token (preferred)
+### Refreshing Tokens via Refresh Token (not recommended)
 
 In the initial installation, you'll need the grant code given to you in either the installation webhook request or the redirect URL, in addition to your integration's client ID and client Secret:
 
@@ -108,7 +108,7 @@ def refresh_token(install_id):
     return new_token
 ```
 
-### Refreshing Tokens Manually for Integrators
+### Refreshing Tokens Manually for Integrators (recommended)
 Sometimes technical anomalies can lead to token refreshing being committed on the Sentry side but then the token is lost in transmission on the way back. As a result, we've added a method for integrators to explicitly refresh and request a new token for their installers.
 
 This manual refresh method uses a different authorization scheme where you will need to send a JWT signed with your client secret to the previous