Make additional updates

Author: devalog

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

@@ -49,7 +49,7 @@ Publish your public-facing Fern Typescript SDK to the [npm registry](https://www
 
 	  <Step title="Configure `output` location">
 
-		Next, change the output location in `generators.yml` from `local-file-system` (the default) to `npm`:
+		Next, change the output location in `generators.yml` from `local-file-system` (the default) to `npm` to indicate that Fern should publish your package directly to the npm registry:
 
 	    ```yaml title="TypeScript" {6-7}
 	    groups: 
@@ -65,7 +65,7 @@ Publish your public-facing Fern Typescript SDK to the [npm registry](https://www
 
 	  <Step title="Add a unique package name">
 
-	     Your package name must be unique in the npm repository, otherwise releasing your SDK to npm will fail. Update your package name if you haven't done so already:
+	     Your package name must be unique in the npm repository, otherwise publishing your SDK to npm will fail. Update your package name if you haven't done so already:
 
 
 ```yaml title="TypeScript" {8}
@@ -102,19 +102,21 @@ ts-sdk:
 	  </Step>
   </Steps>
 
-## Create an npm token
+## Set up npm publishing authentication
 
 <Steps>
 
-	<Step title="Log In">
+	<Step title="Log into npm">
 
 	Log into [npm](https://www.npmjs.com/) or create a new account. 
 
 	</Step>
 
 	<Step title="Navigate to Access Tokens">
 
-	Click on your profile picture, select **Edit Profile**, and then select **Access Tokens**. 
+	1.    Click on your profile picture. 
+	1.    Select **Edit Profile**.
+	1.    Select **Access Tokens**. 
 
 	</Step>
 
@@ -129,7 +131,30 @@ ts-sdk:
 	<img src="assets/npm-automation-token.png" alt="Creating NPM Automation Token" />
 	</Frame>
 
-	<Warning>When you click **Generate Token**, you’ll be returned to the **Access Tokens** dashboard. A box on the top of the dashboard will confirm that you successfully created a new token and prompt you to copy your token id. Make sure you save this id, as you'll need to add it to your GitHub repository in the later on.</Warning>
+	<Warning>When you click **Generate Token**, you’ll be returned to the **Access Tokens** dashboard. A box on the top of the dashboard will confirm that you successfully created a new token and prompt you to copy your token id. Make sure you save this id, as you'll need to add it to your GitHub repository and `generators.yml` later on.</Warning>
+
+	</Step>
+
+	<Step title="Add npm Token to your GitHub Repository">
+
+	<Info>
+	Using GitLab? Follow [these steps](/learn/docs/developer-tools/gitlab#add-a-token-to-gitlab) instead. 
+	</Info>
+
+	1.    Open your repository in GitHub. 
+	1.    Click on the **Settings** tab in your repository.
+	1.    Under the **Security** section and **Secrets and variables** subsection, select **Actions**. 
+
+		  <Info>You can also use the url `https://github.com/<your-repo>/settings/secrets/actions`.</Info>
+
+	1.    Select **New repository secret**. 
+		  <Frame>
+			<img src="assets/github-secret.png" alt="Adding GitHub Repository Secret" />
+			</Frame>
+
+	1.    Name your secret `NPM_TOKEN`.
+	1.    Add the corresponding token you generated in the [previous step](#generate-token).
+	1.    Click **Add secret**. 
 
 	</Step>
 
@@ -154,40 +179,6 @@ ts-sdk:
 
 </Steps>
 
-## Add npm Token to your GitHub Repository
-
-<Info>
-Using GitLab? Follow [these steps](/learn/docs/developer-tools/gitlab#add-a-token-to-gitlab). 
-</Info>
-
-<Steps>
- 
-	<Step title="Open Repository">
-
-	Open your repository in GitHub. 
-
-	</Step>
-
-	<Step title="Add a Secret for your npm Token">
-
-	Click on the **Settings** tab in your repository. Then, under the **Security** section, open **Secrets and variables** > **Actions**. 
-
-	<Frame>
-	<img src="assets/github-secret.png" alt="Adding GitHub Repository Secret" />
-	</Frame>
-
-	You can also use the url `https://github.com/<your-repo>/settings/secrets/actions`.
-
-
-	1.    Select **New repository secret**. 
-	1.    Name your secret `NPM_TOKEN`.
-	1.    Add the corresponding token you generated above.
-	1.    Click **Add secret**. 
-
-	</Step>
-
-</Steps>
-
 ## Release your SDK to NPM
 
   At this point, you're ready to generate a release for your SDK.
@@ -196,7 +187,7 @@ Using GitLab? Follow [these steps](/learn/docs/developer-tools/gitlab#add-a-toke
 
 	<Step title="Set npm environment variable">
 
-	Set the NPM_TOKEN environment variable on your local machine:
+	Set the `NPM_TOKEN` environment variable on your local machine:
 
 	```bash
 	export NPM_TOKEN=your-actual-npm-token
@@ -206,7 +197,7 @@ Using GitLab? Follow [these steps](/learn/docs/developer-tools/gitlab#add-a-toke
 
 	<Step title="Generate your release">
 
-	Run the following command to regenerate your SDK and publish it on npm:
+	Regenerate your SDK and publish it on npm:
 
 	```bash
 	fern generate --version <version>