Apply suggestions from code review

Co-authored-by: Devin Logan <[email protected]>

Author: Swimburger

fern/products/sdks/overview/typescript/publishing-to-npm.mdx

@@ -106,19 +106,18 @@ groups:
 
 ## Configure authentication
 
-Choose how you want to authenticate with npmjs when publishing. **OpenID Connect (OIDC) is strongly recommended** for security.
+Choose how you want to authenticate with npmjs when publishing. 
 
-<Note>
-**Starting in early 2025**, npmjs.org is deprecating long-lived authentication tokens for publishing from CI/CD workflows. OIDC-based authentication is recommended.
-</Note>
+<Warning>
+**Starting in early 2025**, npmjs.org is deprecating long-lived authentication tokens for publishing from CI/CD workflows. **OpenID Connect (OIDC) authentication is strongly recommended** for security.
+</Warning>
 
 <AccordionGroup>
 <Accordion title="OIDC authentication (Recommended)">
 
 OIDC-based publishing (also known as "trusted publishing") is the most secure way to publish. With OIDC, you don't need to manage authentication tokens - npmjs trusts your GitHub repository to publish directly.
 
-<Info>
-**Requirements:**
+<Info title="Prerequisites">
 - Fern TypeScript SDK generator version `3.12.0` or later
 - Fern CLI version `0.94.0` or later (only required for local generation with `--local`)
 </Info>
@@ -156,7 +155,7 @@ OIDC-based publishing (also known as "trusted publishing") is the most secure wa
 	fern generate --group ts-sdk
 	```
 
-	Or push your `generators.yml` changes and let the Fern GitHub Action generate it for you.
+	This creates a `.github/workflows/ci.yml` file that's configured to use OIDC for npmjs publishing. Alternatively, you can push your `generators.yml` changes and let the Fern GitHub Action generate the workflow for you.
 
 	This creates a `.github/workflows/ci.yml` file that's configured to use OIDC for npm publishing.
 
@@ -202,7 +201,7 @@ Provenance attestations aren't generated for packages published from private rep
 <Accordion title="Token-based authentication (Legacy)">
 
 <Warning>
-**This method is being deprecated by npmjs.org in early 2025.** OIDC-based authentication is strongly recommended instead. Long-lived authentication tokens can be exposed in logs, compromised, and are difficult to manage and rotate.
+**This method is being deprecated by npmjs.org in early 2025.** Long-lived authentication tokens can be exposed in logs, compromised, and are difficult to manage and rotate. [OIDC-based authentication is strongly recommended instead](#migrating-from-token-based-to-oidc-publishing). 
 </Warning>
 
 <Steps>