edits [netlify-build]

Author: stayseesong

src/_data/sidenav/strat.yml

@@ -197,3 +197,7 @@ sections:
     title: Analytics-Node.js
   - path: /connections/sources/catalog/libraries/server/node/quickstart/
     title: Quickstart Node.js
+  - path: /connections/sources/catalog/libraries/server/node/classic/
+    title: Analytics-Node.js Classic
+  - path: /connections/sources/catalog/libraries/server/node/migration/
+    title: Analytics-Node.js Migration Guide

src/connections/sources/catalog/libraries/server/node/index.md

@@ -19,7 +19,7 @@ All of Segment's server-side libraries are built for high-performance, so you ca
 > warning ""
 > Make sure you're using a version of Node that's 14 or higher. 
 
-1. Run the following to add Segment's Node library module to your `package.json`.
+1. Run the relevant command to add Segment's Node library module to your `package.json`.
 
     ```bash
     # npm
@@ -43,7 +43,7 @@ All of Segment's server-side libraries are built for high-performance, so you ca
 
   Be sure to replace `YOUR_WRITE_KEY` with your actual **Write Key** which you can find in Segment by navigating to: **Connections > Sources** and selecting your source and going to the **Settings** tab.
 
-  This creates an instance of `Analytics` that you can use to send data to Segment for your project. The default initialization settings are production-ready and queue 20 messages before sending any requests. In development you might want to use [development settings](/docs/connections/sources/catalog/libraries/server/node/#development).
+  This creates an instance of `Analytics` that you can use to send data to Segment for your project. The default initialization settings are production-ready and queue 20 messages before sending any requests. 
 
 
 ## Basic tracking methods
@@ -96,7 +96,7 @@ Field | Details
 `userId` _String, optional_ | The ID for this user in your database. _Note: at least one of `userId` or `anonymousId` must be included in any identify call._
 `anonymousId` _String, optional_ | An ID associated with the user when you don't know who they are (for example, [the anonymousId generated by `analytics.js`](/docs/connections/sources/catalog/libraries/website/javascript/#anonymous-id)). _Note: You must include at least one of `userId` or `anonymousId` in all identify calls._
 `traits` _Object, optional_ | A dictionary of [traits](/docs/connections/spec/identify#traits) you know about the user. Things like: `email`, `name` or `friends`.
-`timestamp` _Date, optional_ | A JavaScript date object representing when the identify took place. If the identify just happened, leave it out and we'll use the server's time. If you're importing data from the past make sure you to send a `timestamp`.
+`timestamp` _Date, optional_ | A JavaScript date object representing when the identify took place. If the identify just happened, leave it out as Segment uses the server's time. If you're importing data from the past make sure to send a `timestamp`.
 `context` _Object, optional_ | A dictionary of extra [context](https://segment.com/docs/connections/spec/common/#context) to attach to the call. _Note: `context` differs from `traits` because it is not attributes of the user itself._
 
 Find details on the **identify method payload** in Segment's [Spec](/docs/connections/spec/identify/).
@@ -359,12 +359,12 @@ analytics.on('track', (ctx) => console.log(ctx))
 ```
 
 ## Plugin architecture
-When you develop against Analytics 2.0, the plugins you write can augment functionality, enrich data, and control the flow and delivery of events. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done.
+When you develop against [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), the plugins you write can augment functionality, enrich data, and control the flow and delivery of events. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done.
 
 Though middlewares function the same as plugins, it's best to use plugins as they are easier to implement and are more testable.
 
 ### Plugin categories
-Plugins are bound by Analytics 2.0 which handles operations such as observability, retries, and error handling. There are two different categories of plugins:
+Plugins are bound by Analytics.js 2.0 which handles operations such as observability, retries, and error handling. There are two different categories of plugins:
 * **Critical Plugins**: Analytics.js expects this plugin to be loaded before starting event delivery. Failure to load a critical plugin halts event delivery. Use this category sparingly, and only for plugins that are critical to your tracking.
 * **Non-critical Plugins**: Analytics.js can start event delivery before this plugin finishes loading. This means your plugin can fail to load independently from all other plugins. For example, every Analytics.js destination is a non-critical plugin. This makes it possible for Analytics.js to continue working if a partner destination fails to load, or if users have ad blockers turned on that are targeting specific destinations.
 
@@ -455,7 +455,7 @@ await analytics.register(pluginA, pluginB, pluginC)
 Deregister a plugin by using: 
 
 ```js
-await analytics.dereigsrer("pluginNameA", "pluginNameB") // takes strings
+await analytics.deregister("pluginNameA", "pluginNameB") // takes strings
 ```
 
 ## Selecting Destinations

src/connections/sources/catalog/libraries/server/node/migration.md

@@ -0,0 +1,90 @@
+---
+title: Analytics for Node.js Migration Guide
+repo: analytics-next
+strat: node-js
+---
+
+> info ""
+> This version of Analytics for Node.js is in beta and Segment is actively working on this feature. Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature. 
+
+If you're using the [classic version of Analytics Node.js](/docs/connections/sources/catalog/libraries/server/node/classic), follow these steps to upgrade to the [latest version of Analytics Node.js](/connections/sources/catalog/libraries/server/node/). 
+
+1. Change the named imports.
+
+    <br> Before:
+    ```javascript  
+    import Analytics from 'analytics-node'
+    ```
+
+    After:
+    ```javascript
+    import { Analytics } from '@segment/analytics-node'
+    ```
+2. Change instantiation to have an object as the first argument.
+
+    <br> Before:
+    ```javascript  
+    var analytics = new Analytics('YOUR_WRITE_KEY');
+    ```
+
+    After:
+    ```javascript
+    const analytics = new Analytics({ writeKey: '<MY_WRITE_KEY>' })
+    ```
+3. Change flushing to [graceful shutdown](/docs/connections/sources/catalog/libraries/server/node//#graceful-shutdown). 
+
+     <br> Before:
+    ```javascript  
+    await analytics.flush(function(err, batch) {
+        console.log('Flushed, and now this program can exit!');
+    });
+    ```
+
+    After:
+    ```javascript
+    await analytics.closeAndFlush()
+    ```
+
+### Differences to note between the classic and updated version     
+
+* The callback call signature changed. 
+
+    <br>Before:
+    ```javascript  
+    (err, batch) => void
+    ```
+
+    After:
+    ```javascript
+    (err, ctx) => void
+    ```
+* The `flushAt` configuration option changed to `maxEventsInBatch`.
+
+#### Removals
+The updated Analytics Node.js removed these configuration options:
+- `enable`
+- `errorHandler` (see the docs on [error handling](/docs/connections/sources/catalog/libraries/server/node//#error-handling) for more information)
+
+The updated Analytics Node.js library removed undocumented behavior around `track` properties 
+
+Before:
+    
+```javascript  
+analytics.track({
+ ...
+ event: 'Ultimate Played',
+ myProp: 'abc'
+})
+```
+
+After:
+
+```javascript
+analytics.track({
+ ...
+ event: 'Ultimate Played',
+ properties:  {
+   myProp: 'abc'
+ }
+})
+```