fix nits

Author: devalog

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

@@ -31,6 +31,8 @@ To enable this feature, you need to configure authentication so that Fern can se
 2. After successful authentication, your system must set a cookie called `fern_token` in the user's browser.
 3. This token should be a [JWT](https://jwt.io) encrypted with a secret key that we provide. The JWT should contain the user's API key.
 
+<Note> See [Role-based access control](/docs/authentication/rbac#architecture-diagrams) for a diagram of the JWT flow.</Note>
+
 The JWT should have a structure similar to:
 
 <CodeBlocks>
@@ -107,6 +109,8 @@ To enable this feature, you need to configure OAuth authentication so that Fern
 1. After successful authentication, your OAuth provider redirects back to Fern with an authorization code, which Fern exchanges for an access token at your token endpoint.
 1. Fern uses this token to retrieve the user's API key and automatically populates it in the API Explorer.
 
+<Note> See [Role-based access control](/docs/authentication/rbac#architecture-diagrams) for a diagram of the OAuth flow.</Note>
+
 #### Setting up auto-populated API keys
 
 To enable API key injection, you'll need to:

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

@@ -29,7 +29,7 @@ Below, we walk through each of the steps required to configure RBAC with either
 ### Architecture diagrams
 
 <Tabs>
-  <Tab title="RBAC with JWT">
+  <Tab title="JWT" toc={true}>
 ```mermaid
 sequenceDiagram
     participant U as User
@@ -64,7 +64,7 @@ sequenceDiagram
 ```
 
   </Tab>
-  <Tab title="RBAC with OAuth">
+  <Tab title="OAuth" toc={true}>
 
 ```mermaid
 sequenceDiagram