From 69613663456d6aced8842e740a05dcd5d21ef71d Mon Sep 17 00:00:00 2001
From: samthurman <sam@samthurman.com>
Date: Wed, 16 Nov 2016 11:16:59 -0500
Subject: [PATCH] Updated node version update instructions

---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a1d01af2..60865a35 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -82,7 +82,7 @@ Release notes can be found in docs/\_posts/release-notes/. Release notes must
 be named `year`-`month`-`day`-`release number`.html and are written in Yaml front matter. Name your release concisely and consider the changes it includes. Jokes, on occasion, are OK. Please see existing release notes for examples.
 
 ### 3. Update Node Package Version
-In `package.json` update the `"version"` field to the new release number.
+Use the command `npm version [major|minor|patch]`. This will increment your package version by one using the semantic versioning scheme described in step 1. So for example if you are on solid version `1.2.1` and you use the command `npm version patch` you will update the version to `1.2.2`.
 
 ### 4. Generate Distribution Files
 `make dist` in the terminal.