Update release instructions now that we have NPM

Author: aaronshekey

docs/product/guidelines/releasing.html

@@ -1,7 +1,7 @@
 ---
 layout: page
 title: Releasing Stacks
-description: The following is a guide to releasing a new version of Stacks and making it available in production on Core and Careers.
+description: The following is a guide to releasing a new version of Stacks and making it available in production on Stack Overflow and Careers.
 ---
 
 <section class="stacks-section">
@@ -19,7 +19,7 @@
 
 <section class="stacks-section">
     {% header "h2", "Ship the new version to Stack Overflow" %}
-    <p class="stacks-copy">In order for the new version of Stacks to be usable on Core and Careers, you’ll need to ship to both.</p>
-
-    <p class="stacks-copy">Within Core and Careers, run the <code class="stacks-code">update-stacks.bat</code> script within <code class="stacks-code">Tools/</code>. This will copy the files from the latest version of the Stacks repo. You’ll need to do this for both Core and Careers. The script will create a new branch, create a single commit with the updates from Stacks, push the new branch to the repo, and open your browser on the &ldquo;new pull request&rdquo; page.</p>
+    <p class="stacks-copy">In order for the new version of Stacks to be usable on Stack Overflow and Careers, you’ll need to ship to both.</p>
+    <p class="stacks-copy">Stack Overflow’s dependencies are now managed via NPM, so updating Stacks there is as simple as bumping the version number in <code class="stacks-code">package.json</code></p>
+    <p class="stacks-copy">Within the Careers repo, run the <code class="stacks-code">update-stacks.bat</code> script within the <code class="stacks-code">Tools</code> directory. This will copy the files from the latest version of the Stacks repo. The script will create a new branch, create a single commit with the updates from Stacks, push the new branch to the repo, and open your browser on the &ldquo;new pull request&rdquo; page.</p>
 </section>