small corrections

Author: bc-devrev

fern/docs/pages/references/keyrings/developer_keyring.mdx

@@ -4,7 +4,7 @@ Unlike other keyrings that store user credentials, developer keyrings are design
 
 ## Snap-in secrets
 
-A `snap_in_secret` is a simple way to store any plain text secret your snap_in requires. It's ideal for sensitive information that doesn't require complex formatting.
+A snap-in secret is a simple way to store any plain text secret your snap_in requires. It's ideal for sensitive information that doesn't require complex formatting.
 
 To create a snap-in secret in the UI, go to the snap-in page **Connection** tab and find the `snap_in_secret` keyring type.
 
@@ -16,7 +16,7 @@ echo \"<SECRET>\" | devrev developer_keyring create snap-in-secret <KEYRING NAME
 
 ## OAuth secrets
 
-An `oauth_secret` is specifically designed to store OAuth client credentials securely. It allows you to define two separate fields:
+The OAuth secret is specifically designed to store OAuth client credentials securely. It requires two fields:
 
   * `client_id`: The client ID provided by the OAuth provider.
   * `client_secret`: The client secret provided by the OAuth provider.

fern/docs/pages/references/keyrings/introduction.mdx

@@ -17,7 +17,7 @@ Think of keyrings as secure vaults within your snap-in, acting as a middleman be
 ## Supported credential types
 
 * **OAuth:** Streamline connections with popular services like Slack and Jira using pre-defined OAuth keyrings.
-* **Secrets:** Store various secret configurations, including personal access tokens (PATs) and Multi-field Token (JSON) for broader service integrations.
+* **Secrets:** Store various secret configurations, including personal access tokens (PATs) and multi-field tokens (JSON) for broader service integrations.
 
 ## Access levels
 

fern/docs/pages/references/keyrings/oauth_config.mdx

@@ -12,9 +12,7 @@ For comprehensive information about the OAuth specification, refer to the offici
 
 4. **Access tokens:** Upon successful authorization, the service provides your snap-in with an access token. This token is used to access user data on the service's behalf without requiring the user's password again.
 
-5. **Refreshing tokens:** A key benefit of using keyrings for OAuth is that they can handle refreshing access tokens automatically. Most OAuth implementations issue a refresh token alongside the access token. This refresh token can be used to obtain a new access token before the current one expires.
-    - if refresh_token is not provided, the user will need to re-authorize the connection after the access token expires.
-    - if refresh_token is expires, the user will need to re-authorize the connection after the access token expires.
+5. **Refreshing tokens:** A key benefit of using keyrings for OAuth is that they can handle refreshing access tokens automatically. Most OAuth implementations issue a refresh token alongside the access token. This refresh token can be used to obtain a new access token before the current one expires. If the token is not provided or is expired, the user will need to re-authorize the connection.
 
 6. **Revoking tokens:** For enhanced security, you can also configure your keyring to revoke access tokens when they are no longer needed. This ensures that even if a token is compromised, it can't be used to access user data.