clean up

Author: moeodeh3

authentication/email.mdx

@@ -157,58 +157,42 @@ const response = await client.emailAuth({
 });
 ```
 
-**Auth Proxy Update: appName becomes a required parameter (12/8/2025)**
+### Breaking Change: `appName` Required
 
 <Warning>
-  **Auth Proxy: appName becomes a required parameter**
+  **Effective December 8, 2025**
+  
+  Beginning the week of December 8, 2025, all email-based OTP and recovery activities will require the `appName` parameter. Existing SDK versions will continue working, but upgrading without setting an `appName` will break email-based flows.
+
+<CardGroup cols={2}>
+  <Card title="Auth Proxy Users" icon="server">
+    **Affected:** Anyone using Auth Proxy without `appName` set
+    
+    **Action:** Set `appName` under [email configuration](https://app.turnkey.com/dashboard/walletKit)
+  </Card>
+  <Card title="Server SDK Users" icon="code">
+    **Affected:** Users calling `init_otp_auth`, `init_otp`, `email_recovery`, or `email_auth` without `appName`
+    
+    **Action:**<br/>
+    • For `email_recovery` or `email_auth`: include `appName` in your request<br/>
+    • For `init_otp` or `init_otp_auth`: update your API call to match the new input structure when upgrading to the latest server-SDK
+  </Card>
+</CardGroup>
+
+<Accordion title="Policy activity type updates">
+  If you manage email flows with policies, update to the new activity types:
+
+  | Flow | Old Activities | New Activity |
+  |------|---------------|--------------|
+  | EMAIL_AUTH | `ACTIVITY_TYPE_EMAIL_AUTH`, `ACTIVITY_TYPE_EMAIL_AUTH_V2` | `ACTIVITY_TYPE_EMAIL_AUTH_V3` |
+  | INIT_OTP_AUTH | `ACTIVITY_TYPE_INIT_OTP_AUTH`, `ACTIVITY_TYPE_INIT_OTP_AUTH_V2` | `ACTIVITY_TYPE_INIT_OTP_AUTH_V3` |
+  | INIT_OTP | `ACTIVITY_TYPE_INIT_OTP` | `ACTIVITY_TYPE_INIT_OTP_V2` |
+  | INIT_USER_EMAIL_RECOVERY | `ACTIVITY_TYPE_INIT_USER_EMAIL_RECOVERY` | `ACTIVITY_TYPE_INIT_USER_EMAIL_RECOVERY_V2` |
+</Accordion>
 
-  \
-  Beginning the week of **December 8 2025**, all new versionf of email-based OTP and recovery activities will **require the appName parameter**. Until this point the appName is optional. We’re releasing a new major version of our <u>server SDKs</u> which will introduce a **major version bump.**
-
-  - The **appName** will become a **required** field in updated email activities
-
-  Existing SDK versions will continue working, but upgrading without setting an **appName** will break email-based flows.\
-  \
-  **<u>Who is Affected</u>**\
-  **Auth Proxy users**: Anyone using the Auth Proxy without an appName set
-
-  **Server SDK users:** 
-
-  - Users who do not specify an appName, and/or
-  - Any user calling email-based flows, including:
-    - Init_otp_auth
-    - Init_otp
-    - Email_recovery
-    - Email_auth
-
-  **<u>What You Will Need To Do</u>**
-
-  **Auth Proxy users:**
-
-  - Ensure there is an **appName** set under email configuration, [<u>here</u>](https://app.turnkey.com/dashboard/walletKit)
-
-  **Server-SDK users:**
-
-  - For those using email_recovery or email_auth
-    - Ensure you include an **AppName** in your request
-  - For those using init_otp or init_otp_auth:  When upgrading to the newest server-SDK (a major version), you **must** update your API call to match the new input structure
-
-  **If you are using policies to manage email flows:**
-
-  - EMAIL_AUTH 
-    - **Old activities:** ACTIVITY_TYPE_EMAIL_AUTH, ACTIVITY_TYPE_EMAIL_AUTH_V2
-    - **New activity**: ACTIVITY_TYPE_EMAIL_AUTH_V3
-  - INIT_OTP_AUTH
-    - **Old activities**: ACTIVITY_TYPE_INIT_OTP_AUTH, ACTIVITY_TYPE_INIT_OTP_AUTH_V2
-    - **New activity**: ACTIVITY_TYPE_INIT_OTP_AUTH_V3
-  - INIT_OTP 
-    - **Old activity**: ACTIVITY_TYPE_INIT_OTP 
-    - **New activity**: ACTIVITY_TYPE_INIT_OTP_V2
-  - INIT_USER_EMAIL_RECOVERY
-    - **Old activity**: ACTIVITY_TYPE_INIT_USER_EMAIL_RECOVERY
-    - **New activity**: ACTIVITY_TYPE_INIT_USER_EMAIL_RECOVERY_V2
 </Warning>
 
+
 ### Email templates
 
 We also support custom HTML email templates for [Enterprise](https://www.turnkey.com/pricing) clients on the **Scale** tier. This allows you to inject arbitrary data from a JSON string containing key-value pairs. In this case, the `emailCustomization` variable may look like: