wording updates

Author: devalog

fern/products/docs/pages/api-references/autopopulate-api-key.mdx

@@ -18,7 +18,7 @@ With this feature, you can **create new users of your API** directly from within
 API key injection can work in two different ways depending on your company's authentication setup: **JWT or OAuth**. 
 
 * **JWT Flow:** You handle the entire auth flow and just give Fern a JWT cookie
-* **OAuth Flow:** You give Fern access, and Fern directly handles the OAuth handshake process
+* **OAuth Flow:** You give Fern access, and Fern directly initiates the OAuth handshake process
 
 <AccordionGroup>
 <Accordion title="JWT" toc={true}>

fern/products/docs/pages/authentication/overview.mdx

@@ -7,9 +7,9 @@ Fern offers two methods of authentication, Single Sign-On (SSO) and Role-Based A
 
 **For most situations, we recommend using RBAC** for granular access control over your documentation. RBAC works well for sites with multiple audiences (internal teams, partners, customers) and supports API key injection to auto-populate code examples.
 
-**SSO is simpler** but only provides basic login functionality - it doesn't support role-based permissions or API key injection. SSO works well for internal-only documentation where everyone should see the same content.
+**SSO is simpler** but only provides basic login functionality - it doesn't support RBAC or API key injection. SSO works well for internal-only documentation where everyone should see the same content.
 
-**API Key Injection** (available with RBAC only) can be set up using either JWT or OAuth, depending on your existing authentication system.
+**API Key Injection** can be set up using either JWT or OAuth, depending on your existing authentication system.
 
 Learn more about Fern's authentication options: