From fed336092dd2f6a63747400a38a7b7d6ed8f9d4c Mon Sep 17 00:00:00 2001
From: Myles Borins <mborins@us.ibm.com>
Date: Tue, 12 Jan 2016 16:07:29 -0800
Subject: [PATCH] docs: fix npm command in releases.md

---
 doc/releases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/releases.md b/doc/releases.md
index 53aa4d53fb9157..47e874a9666031 100644
--- a/doc/releases.md
+++ b/doc/releases.md
@@ -248,7 +248,7 @@ Your release should be available at <https://nodejs.org/dist/vx.y.z/> and <https
 
 There is an automatic build that is kicked off when you promote new builds, so within a few minutes nodejs.org will be listing your new version as the latest release. However, the blog post is not yet fully automatic.
 
-Create a new blog post by running the [nodejs.org release-post.js script](https://github.com/nodejs/nodejs.org/blob/master/scripts/release-post.js). This script will use the promoted builds and changelog to generate the post. Run `npm serve` to preview the post locally before pushing to the [nodejs.org](https://github.com/nodejs/nodejs.org) repo.
+Create a new blog post by running the [nodejs.org release-post.js script](https://github.com/nodejs/nodejs.org/blob/master/scripts/release-post.js). This script will use the promoted builds and changelog to generate the post. Run `npm run serve` to preview the post locally before pushing to the [nodejs.org](https://github.com/nodejs/nodejs.org) repo.
 
 * You can add a short blurb just under the main heading if you want to say something important, otherwise the text should be publication ready.
 * The links to the download files won't be complete unless you waited for the ARMv6 builds. Any downloads that are missing will have `*Coming soon*` next to them. It's your responsibility to manually update these later when you have the outstanding builds.