Fixed release process document npm section.

Accidentally checked in the first draft before deciding not to use
the npm prepublish lifecycle script.

Part of issue #134.

Author: stevenbenner

doc/release-process.md

@@ -55,7 +55,7 @@ The events that fire during the tooltip life cycle are also considered to be par
 
 	First, verify that the package to be release to npm contains the expected files in the expected structure. Run `grunt build:npm && npm pack`. This will generate the appropriate dist folder contents and create the tgz package. Look over the tgz package to make sure everything looks good.
 
-	Now publish the new release to the npm repository by running the `npm publish` command. This will automatically run the `grunt build:npm` task via the npm precommit script.
+	Now publish the new release to the npm repository by running the `npm publish` command. This will **NOT** automatically run the `grunt build:npm`, **make sure that is run before publish!** ([npm#10074](https://github.com/npm/npm/issues/10074)).
 
 7. **Add new release to GitHub repo**