diagram update

Author: devalog

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

@@ -107,39 +107,6 @@ 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.
 
-#### Architecture diagram
-
-```mermaid
-sequenceDiagram
-    participant U as User
-    participant F as Fern Docs
-    participant A as OAuth2 Provider
-    U->>F: Visit restricted page
-    F->>F: Check fern_token cookie
-    
-    alt Cookie exists
-        F->>F: Decode cookie
-        F->>F: Verify authentication credentials
-        Note over F: Attempt to refresh the token, if expired
-        
-        alt User is properly authenticated
-            F->>U: Show restricted content
-        else User is not properly authenticated
-            F->>U: User is shown a 404 page
-        end
-    else No cookie
-        F->>A: Redirect to `/authenticate` endpoint
-        A->>U: User authenticates
-        U->>F: Authorization code is returned
-        F->>A: Redirect to `/token` endpoint
-        A->>A: Validate token request
-        A->>F: Send authenticated access token
-        F->>F: Set fern_token cookie
-        F->>F: Verify authentication credentials
-        F->>U: Show restricted content
-    end
-```
-
 ### Setting up auto-populated API keys
 
 To enable API key injection, you'll need to: