update

Author: SathishKumarHS

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

@@ -16,7 +16,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.
+* **OAuth 2.0 :** 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 tokens (JSON) for broader service integrations.
 
 ## Access levels

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

@@ -2,13 +2,13 @@ OAuth 2.0 (Open Authorization) is a widely adopted standard for authorization th
 
 For comprehensive information about the OAuth specification, refer to the official documentation: [OAuth 2.0](https://oauth.net/2/).
 
-## Using OAuth keyrings
+## Using OAuth 2.0 keyrings
 
 1. **Define the keyring:** Within your snap-in manifest, define a keyring specifically for OAuth credentials. DevRev offers pre-defined keyring types for popular services like Slack or Jira, simplifying the process.
 
 2. **Provide credentials:** During development, you'll provide your developer keyring of type `oauth-secret` which contains client ID and client secret for the chosen service within the keyring definition. These credentials are securely stored and not distributed with your published snap-in.
 
-3. **OAuth flow:** When your snap-in needs to access user data from the external service, it initiates the OAuth flow. This typically involves redirecting the user to the service's login page and then back to your snap-in after successful authorization.
+3. **OAuth 2.0 flow:** When your snap-in needs to access user data from the external service, it initiates the OAuth flow. This typically involves redirecting the user to the service's login page and then back to your snap-in after successful authorization.
 
 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.
 

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

@@ -114,6 +114,7 @@ keyring_types:
         - id: <field_id_2>
           name: <field_name>
           description: <field_description>
+      # The token_verification section is used to verify the token provided by the user.
       token_verification: # The token_verification section is used to verify the token provided by the user.
         url: <url> # The URL to which the token will be sent for verification.
         method: <method> # The HTTP method to be used for the verification request.