Always use npm-blah(1) in the md, convert appropriately

HTML gets a hyperlink, manpage gets 'npm help blah' text

18 files changed, 69 insertions, 72 deletions

diff --git a/html/doc/coding-style.html b/html/doc/coding-style.html
index a244d9797..593ec02b8 100644
--- a/html/doc/coding-style.html
+++ b/html/doc/coding-style.html
@@ -486,7 +486,7 @@ report what's happening so that it's easier to track down where a fault
 occurs.</p>
 
 <p>Use appropriate log levels.  The default log() function logs at the
-"info" level.  See <code>npm help config</code> and search for "loglevel".</p>
+"info" level.  See <code><a href="config.html">npm config</a></code> and search for "loglevel".</p>
 
 <h2 id="Case-naming-etc">Case, naming, etc.</h2>
 
@@ -546,4 +546,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help coding-style - 2011-11-04 08:09:40 -->
+<!-- npm help coding-style - 2011-30-04 08:09:01 -->
diff --git a/html/doc/config.html b/html/doc/config.html
index c7ec058c2..f12093b00 100644
--- a/html/doc/config.html
+++ b/html/doc/config.html
@@ -431,7 +431,7 @@ npm ls --global --parseable --long --loglevel info</code></pre>
 
 <h2 id="Per-Package-Config-Settings">Per-Package Config Settings</h2>
 
-<p>When running scripts (see <code>npm help scripts</code>)
+<p>When running scripts (see <code><a href="scripts.html">npm scripts</a></code>)
 the package.json "config" keys are overwritten in the environment if
 there is a config param of <code>&lt;name&gt;[@&lt;version&gt;]:&lt;key&gt;</code>.  For example, if
 the package.json has this:</p>
@@ -491,7 +491,7 @@ have their <code>build</code> directories automatically ignored.</p>
 
 <ul><li>Default: Windows: <code>~/npm-cache</code>, Posix: <code>~/.npm</code></li><li>Type: path</li></ul>
 
-<p>The location of npm's cache directory.  See <code>npm help cache</code></p>
+<p>The location of <a href="'s cache directory.  See <code>npm-cache.html">npm 's cache directory.  See <code>npm-cache</a></code></p>
 
 <h3 id="color">color</h3>
 
@@ -542,7 +542,7 @@ set.</p>
 
 <p>Operates in "global" mode, so that packages are installed into the
 <code>prefix</code> folder instead of the current working directory.  See
-<code>npm help folders</code> for more on the differences in behavior.</p>
+<code><a href="folders.html">npm folders</a></code> for more on the differences in behavior.</p>
 
 <ul><li>packages are installed into the <code>prefix/node_modules</code> folder, instead of the
 current working directory.</li><li>bin files are linked to <code>prefix/bin</code></li><li>man pages are linked to <code>prefix/share/man</code></li></ul>
@@ -802,7 +802,7 @@ will fail.</p>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
 
 <p>Set to show short usage output (like the -H output)
-instead of complete help when doing <code>npm help</code>.</p>
+instead of complete help when doing <code><a href="help.html">npm help</a></code>.</p>
 
 <h3 id="user">user</h3>
 
@@ -885,4 +885,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help config - 2011-11-04 08:09:40 -->
+<!-- npm help config - 2011-30-04 08:09:01 -->
diff --git a/html/doc/developers.html b/html/doc/developers.html
index 9d7d51925..79f4f0a4d 100644
--- a/html/doc/developers.html
+++ b/html/doc/developers.html
@@ -353,10 +353,7 @@ that your users will do to install your program.</p>
 
 <p>These are man pages.  If you install npm, you should be able to
 then do <code>man npm-thing</code> to get the documentation on a particular
-topic.</p>
-
-<p>Any time you see "see <a href="whatever.html">npm whatever</a>", you can do <code>man npm-whatever</code>
-or <code>npm help whatever</code> to get at the docs.</p>
+topic, or <code>npm help thing</code> to see the same information.</p>
 
 <h2 id="What-is-a-package">What is a `package`</h2>
 
@@ -458,10 +455,7 @@ bring in your module's main module.</p>
 
 <p>and then follow the prompts.</p>
 
-<p>This is documented better in <a href="adduser.html">npm adduser</a>.  So do this to get the
-details:</p>
-
-<pre><code>npm help adduser</code></pre>
+<p>This is documented better in <a href="adduser.html">npm adduser</a>.</p>
 
 <h2 id="Publish-your-package">Publish your package</h2>
 
@@ -511,4 +505,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help developers - 2011-11-04 08:09:41 -->
+<!-- npm help developers - 2011-30-04 08:09:01 -->
diff --git a/html/doc/edit.html b/html/doc/edit.html
index a0ff6e32c..c38a24a60 100644
--- a/html/doc/edit.html
+++ b/html/doc/edit.html
@@ -346,7 +346,7 @@ input.submit, input#submit, input.button, button, input[type=submit] {
 <h2 id="DESCRIPTION">DESCRIPTION</h2>
 
 <p>Opens the package folder in the default editor (or whatever you've
-configured as the npm <code>editor</code> config -- see <code>npm help config</code>.)</p>
+configured as the <a href=" <code>editor</code> config -- see <code>npm-config.html">npm  <code>editor</code> config -- see <code>npm-config</a></code>.)</p>
 
 <p>After it has been edited, the package is rebuilt so as to pick up any
 changes in compiled packages.</p>
@@ -383,4 +383,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help edit - 2011-11-04 08:09:41 -->
+<!-- npm help edit - 2011-30-04 08:09:01 -->
diff --git a/html/doc/faq.html b/html/doc/faq.html
index 99a5773cd..fb212261a 100644
--- a/html/doc/faq.html
+++ b/html/doc/faq.html
@@ -356,7 +356,7 @@ do what it says and post a bug with all the information it asks for.</p>
 
 <h2 id="Where-does-npm-put-stuff">Where does npm put stuff?</h2>
 
-<p>See <code>npm help folders</code></p>
+<p>See <code><a href="folders.html">npm folders</a></code></p>
 
 <p>tl;dr:</p>
 
@@ -388,7 +388,7 @@ npm config set global true</code></pre>
 <p>This is not recommended.</p>
 
 <p>Many things <strong>will not work</strong> if you do this.  Make sure you read and
-understand <code>npm help config</code> and <code>npm help global</code> before you complain
+understand <code><a href="config.html">npm config</a></code> and <code><a href="global.html">npm global</a></code> before you complain
 about things being broken.</p>
 
 <p>When you realize what a mistake it was, do this to switch back:</p>
@@ -467,12 +467,12 @@ an argument to <code>git checkout</code>.  The default is <code>master</code>.</
 
 <h2 id="How-can-I-use-npm-for-development">How can I use npm for development?</h2>
 
-<p>See <code>npm help developers</code> and <code>npm help json</code>.</p>
+<p>See <code><a href="developers.html">npm developers</a></code> and <code><a href="json.html">npm json</a></code>.</p>
 
 <p>You'll most likely want to <code>npm link</code> your development folder.  That's
 awesomely handy.</p>
 
-<p>To set up your own private registry, check out <code>npm help registry</code>.</p>
+<p>To set up your own private registry, check out <code><a href="registry.html">npm registry</a></code>.</p>
 
 <h2 id="Can-I-list-a-url-as-a-dependency">Can I list a url as a dependency?</h2>
 
@@ -482,11 +482,11 @@ that has a package.json in its root, or a git url.
 
 <h2 id="How-do-I-symlink-to-a-dev-folder-so-I-don-t-have-to-keep-re-installing">How do I symlink to a dev folder so I don't have to keep re-installing?</h2>
 
-<p>See <code>npm help link</code></p>
+<p>See <code><a href="link.html">npm link</a></code></p>
 
 <h2 id="The-package-registry-website-What-is-that-exactly">The package registry website.  What is that exactly?</h2>
 
-<p>See <code>npm help registry</code>.</p>
+<p>See <code><a href="registry.html">npm registry</a></code>.</p>
 
 <h2 id="What-s-up-with-the-insecure-channel-warnings">What's up with the insecure channel warnings?</h2>
 
@@ -555,4 +555,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help faq - 2011-11-04 08:09:42 -->
+<!-- npm help faq - 2011-30-04 08:09:01 -->
diff --git a/html/doc/folders.html b/html/doc/folders.html
index 351c98a21..8879c2e8a 100644
--- a/html/doc/folders.html
+++ b/html/doc/folders.html
@@ -383,7 +383,7 @@ When installing locally, this means that you can
 
 <h3 id="Cache">Cache</h3>
 
-<p>See <code>npm help cache</code>.  Cache files are stored in <code>~/.npm</code> on Posix, or
+<p>See <code><a href="cache.html">npm cache</a></code>.  Cache files are stored in <code>~/.npm</code> on Posix, or
 <code>~/npm-cache</code> on Windows.</p>
 
 <p>This is controlled by the <code>cache</code> configuration param.</p>
@@ -516,7 +516,7 @@ not be included in the package tarball.</p>
 
 <p>This allows a package maintainer to install all of their dependencies
 (and dev dependencies) locally, but only re-publish those items that
-cannot be found elsewhere.  See <code>npm help json</code> for more information.</p>
+cannot be found elsewhere.  See <code><a href="json.html">npm json</a></code> for more information.</p>
 </div>
 <script>
 els = Array.prototype.slice.call((wrapper = document.getElementById("wrapper"))
@@ -546,4 +546,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help folders - 2011-11-04 08:09:42 -->
+<!-- npm help folders - 2011-30-04 08:09:02 -->
diff --git a/html/doc/get.html b/html/doc/get.html
index a5787a139..f4bb59905 100644
--- a/html/doc/get.html
+++ b/html/doc/get.html
@@ -431,7 +431,7 @@ npm ls --global --parseable --long --loglevel info</code></pre>
 
 <h2 id="Per-Package-Config-Settings">Per-Package Config Settings</h2>
 
-<p>When running scripts (see <code>npm help scripts</code>)
+<p>When running scripts (see <code><a href="scripts.html">npm scripts</a></code>)
 the package.json "config" keys are overwritten in the environment if
 there is a config param of <code>&lt;name&gt;[@&lt;version&gt;]:&lt;key&gt;</code>.  For example, if
 the package.json has this:</p>
@@ -491,7 +491,7 @@ have their <code>build</code> directories automatically ignored.</p>
 
 <ul><li>Default: Windows: <code>~/npm-cache</code>, Posix: <code>~/.npm</code></li><li>Type: path</li></ul>
 
-<p>The location of npm's cache directory.  See <code>npm help cache</code></p>
+<p>The location of <a href="'s cache directory.  See <code>npm-cache.html">npm 's cache directory.  See <code>npm-cache</a></code></p>
 
 <h3 id="color">color</h3>
 
@@ -542,7 +542,7 @@ set.</p>
 
 <p>Operates in "global" mode, so that packages are installed into the
 <code>prefix</code> folder instead of the current working directory.  See
-<code>npm help folders</code> for more on the differences in behavior.</p>
+<code><a href="folders.html">npm folders</a></code> for more on the differences in behavior.</p>
 
 <ul><li>packages are installed into the <code>prefix/node_modules</code> folder, instead of the
 current working directory.</li><li>bin files are linked to <code>prefix/bin</code></li><li>man pages are linked to <code>prefix/share/man</code></li></ul>
@@ -802,7 +802,7 @@ will fail.</p>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
 
 <p>Set to show short usage output (like the -H output)
-instead of complete help when doing <code>npm help</code>.</p>
+instead of complete help when doing <code><a href="help.html">npm help</a></code>.</p>
 
 <h3 id="user">user</h3>
 
@@ -885,4 +885,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help get - 2011-11-04 08:09:42 -->
+<!-- npm help get - 2011-30-04 08:09:02 -->
diff --git a/html/doc/global.html b/html/doc/global.html
index 103325432..1ea055322 100644
--- a/html/doc/global.html
+++ b/html/doc/global.html
@@ -383,7 +383,7 @@ When installing locally, this means that you can
 
 <h3 id="Cache">Cache</h3>
 
-<p>See <code>npm help cache</code>.  Cache files are stored in <code>~/.npm</code> on Posix, or
+<p>See <code><a href="cache.html">npm cache</a></code>.  Cache files are stored in <code>~/.npm</code> on Posix, or
 <code>~/npm-cache</code> on Windows.</p>
 
 <p>This is controlled by the <code>cache</code> configuration param.</p>
@@ -516,7 +516,7 @@ not be included in the package tarball.</p>
 
 <p>This allows a package maintainer to install all of their dependencies
 (and dev dependencies) locally, but only re-publish those items that
-cannot be found elsewhere.  See <code>npm help json</code> for more information.</p>
+cannot be found elsewhere.  See <code><a href="json.html">npm json</a></code> for more information.</p>
 </div>
 <script>
 els = Array.prototype.slice.call((wrapper = document.getElementById("wrapper"))
@@ -546,4 +546,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help global - 2011-11-04 08:09:43 -->
+<!-- npm help global - 2011-30-04 08:09:02 -->
diff --git a/html/doc/help-search.html b/html/doc/help-search.html
index 7b311eb06..94ac8799b 100644
--- a/html/doc/help-search.html
+++ b/html/doc/help-search.html
@@ -393,4 +393,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help help-search - 2011-11-04 08:09:43 -->
+<!-- npm help help-search - 2011-30-04 08:09:02 -->
diff --git a/html/doc/install.html b/html/doc/install.html
index 8076c28b6..57c7ba351 100644
--- a/html/doc/install.html
+++ b/html/doc/install.html
@@ -375,14 +375,14 @@ must either be "." or contain a "/" in it.</p><p>Example:</p><pre><code>npm inst
 Fetch the tarball url, and then install it.  In order to distinguish between
 this and other options, the argument must start with "http://" or "https://"</p><p>Example:</p><pre><code>npm install http://github.com/waveto/node-crypto/tarball/v0.0.5</code></pre></li><li><p>npm install <code>&lt;name&gt;</code>:
 Do a <code>&lt;name&gt;@&lt;tag&gt;</code> install, where <code>&lt;tag&gt;</code> is the "tag" config. (See
-<code>npm help config</code>)</p><p>Example:</p><pre><code>npm install sax</code></pre></li><li><p>npm install <code>&lt;name&gt;@&lt;tag&gt;</code>:
+<code><a href="config.html">npm config</a></code>)</p><p>Example:</p><pre><code>npm install sax</code></pre></li><li><p>npm install <code>&lt;name&gt;@&lt;tag&gt;</code>:
 Install the version of the package that is referenced by the specified tag.
 If the tag does not exist in the registry data for that package, then this
 will fail.</p><p>Example:</p><pre><code>npm install sax@stable</code></pre></li><li><p>npm install <code>&lt;name&gt;@&lt;version&gt;</code>:
 Install the specified version of the package.  This will fail if the version
 has not been published to the registry.</p><p>Example:</p><pre><code>npm install sax@0.1.1</code></pre></li><li><p>npm install <code>&lt;name&gt;@&lt;version range&gt;</code>:
 Install a version of the package matching the specified version range.  This
-will follow the same rules for resolving dependencies described in <code>npm help json</code>.</p><p>Note that most version ranges must be put in quotes so that your shell will
+will follow the same rules for resolving dependencies described in <code><a href="json.html">npm json</a></code>.</p><p>Note that most version ranges must be put in quotes so that your shell will
 treat it as a single argument.</p><p>Example:</p><pre><code>npm install sax@"&gt;=0.1.0 &lt;0.2.0"</code></pre></li></ul>
 
 <p>You may combine multiple arguments, and even multiple types of arguments.
@@ -398,12 +398,12 @@ local copy exists on disk.</p>
 <pre><code>npm install sax --force</code></pre>
 
 <p>The <code>--global</code> argument will cause npm to install the package globally
-rather than locally.  See <code>npm help global</code>.</p>
+rather than locally.  See <code><a href="global.html">npm global</a></code>.</p>
 
 <p>The <code>--link</code> argument will cause npm to link global installs into the
 local space in some cases.</p>
 
-<p>See <code>npm help config</code>.  Many of the configuration params have some
+<p>See <code><a href="config.html">npm config</a></code>.  Many of the configuration params have some
 effect on installation, since that's most of what npm does.</p>
 
 <h2 id="SEE-ALSO">SEE ALSO</h2>
@@ -438,4 +438,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help install - 2011-11-04 08:09:43 -->
+<!-- npm help install - 2011-30-04 08:09:02 -->
diff --git a/html/doc/json.html b/html/doc/json.html
index d0d9b3583..3960a60e3 100644
--- a/html/doc/json.html
+++ b/html/doc/json.html
@@ -345,7 +345,7 @@ input.submit, input#submit, input.button, button, input[type=submit] {
 file.  It must be actual JSON, not just a JavaScript object literal.</p>
 
 <p>A lot of the behavior described in this document is affected by the config
-settings described in <code>npm help config</code>.</p>
+settings described in <code><a href="config.html">npm config</a></code>.</p>
 
 <h2 id="DEFAULT-VALUES">DEFAULT VALUES</h2>
 
@@ -600,7 +600,7 @@ html project page that you put in your browser.  It's for computers.</p>
 at various times in the lifecycle of your package.  The key is the lifecycle
 event, and the value is the command to run at that point.</p>
 
-<p>See <code>npm help scripts</code> to find out more about writing package scripts.</p>
+<p>See <code><a href="scripts.html">npm scripts</a></code> to find out more about writing package scripts.</p>
 
 <h2 id="config">config</h2>
 
@@ -615,7 +615,7 @@ instance, if a package had the following:</p>
 <code>npm_package_config_port</code> environment variable, then the user could
 override that by doing <code>npm config set foo:port 8001</code>.</p>
 
-<p>See <code>npm help config</code> and <code>npm help scripts</code> for more on package
+<p>See <code><a href="config.html">npm config</a></code> and <code><a href="scripts.html">npm scripts</a></code> for more on package
 configs.</p>
 
 <h2 id="dependencies">dependencies</h2>
@@ -690,8 +690,8 @@ the external test or documentation framework that you use.</p>
 
 <p>These things will be installed whenever the <code>--dev</code> configuration flag
 is set.  This flag is set automatically when doing <code>npm link</code>, and can
-be managed like any other npm configuration param.  See <code>npm help
-config</code> for more on the topic.</p>
+be managed like any other <a href=" configuration param.  See <code>npm-config.html">npm  configuration param.  See <code>npm-config</a></code>
+for more on the topic.</p>
 
 <h2 id="bundledDependencies">bundledDependencies</h2>
 
@@ -749,7 +749,7 @@ the global public registry by default.</p>
 <p>Any config values can be overridden, but of course only "tag" and
 "registry" probably matter for the purposes of publishing.</p>
 
-<p>See <code>npm help config</code> to see the list of config options that can be
+<p>See <code><a href="config.html">npm config</a></code> to see the list of config options that can be
 overridden.</p>
 </div>
 <script>
@@ -780,4 +780,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help json - 2011-11-04 08:09:44 -->
+<!-- npm help json - 2011-30-04 08:09:02 -->
diff --git a/html/doc/npm.html b/html/doc/npm.html
index e509efc71..ca240af2e 100644
--- a/html/doc/npm.html
+++ b/html/doc/npm.html
@@ -360,14 +360,14 @@ programs.</p>
 <p>You probably got npm because you want to install stuff.</p>
 
 <p>Use <code>npm install blerg</code> to install the latest version of "blerg".  Check out
-<code>npm help install</code> for more info.  It can do a lot of stuff.</p>
+<code><a href="install.html">npm install</a></code> for more info.  It can do a lot of stuff.</p>
 
 <p>Use the <code>npm search</code> command to show everything that's available.
 Use <code>npm ls</code> to show everything you've installed.</p>
 
 <h2 id="DIRECTORIES">DIRECTORIES</h2>
 
-<p>See <code>npm help folders</code> to learn about where npm puts stuff.</p>
+<p>See <code><a href="folders.html">npm folders</a></code> to learn about where npm puts stuff.</p>
 
 <p>In particular, npm has two modes of operation:</p>
 
@@ -385,7 +385,7 @@ operate in global mode instead.</p>
 following help topics:</p>
 
 <ul><li>json:
-Make a package.json file.  See <code>npm help json</code>.</li><li>link:
+Make a package.json file.  See <code><a href="json.html">npm json</a></code>.</li><li>link:
 For linking your current working code into Node's path, so that you
 don't have to reinstall every time you make a change.  Use
 <code>npm link</code> to do this.</li><li>install:
@@ -413,14 +413,14 @@ If the <code>globalconfig</code> option is set in the cli, env, or user config,
 then that file is parsed instead.</li><li>Defaults:<br />npm's default configuration options are defined in
 lib/utils/config-defs.js.  These must not be changed.</li></ul>
 
-<p>See <code>npm help config</code> for much much more information.</p>
+<p>See <code><a href="config.html">npm config</a></code> for much much more information.</p>
 
 <h2 id="CONTRIBUTIONS">CONTRIBUTIONS</h2>
 
 <p>Patches welcome!</p>
 
 <ul><li>code:
-Read through <code>npm help coding-style</code> if you plan to submit code.
+Read through <code><a href="coding.html">npm coding</a>-style</code> if you plan to submit code.
 You don't have to agree with it, but you do have to follow it.</li><li>docs:
 If you find an error in the documentation, edit the appropriate markdown
 file in the "doc" folder.  (Don't worry about generating the man page.)</li></ul>
@@ -453,7 +453,10 @@ will no doubt tell you to put the output in a gist or email.</p>
 
 <h2 id="AUTHOR">AUTHOR</h2>
 
-<p>Isaac Z. Schlueter :: isaacs :: <a href="http://twitter.com/izs">@izs</a> :: <a href="mailto:i@izs.me">i@izs.me</a></p>
+<p><a href="http://blog.izs.me/">Isaac Z. Schlueter</a> ::
+<a href="https://github.com/isaacs/">isaacs</a> ::
+<a href="http://twitter.com/izs">@izs</a> ::
+<a href="mailto:i@izs.me">i@izs.me</a></p>
 </div>
 <script>
 els = Array.prototype.slice.call((wrapper = document.getElementById("wrapper"))
@@ -483,4 +486,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help npm - 2011-13-04 08:09:44 -->
+<!-- npm help npm - 2011-30-04 08:09:02 -->
diff --git a/html/doc/rebuild.html b/html/doc/rebuild.html
index d1826127f..c8438ab19 100644
--- a/html/doc/rebuild.html
+++ b/html/doc/rebuild.html
@@ -354,7 +354,7 @@ the new binary.</p>
 
 <h2 id="CONFIGURATION">CONFIGURATION</h2>
 
-<p>See <code>npm help build</code></p>
+<p>See <code><a href="build.html">npm build</a></code></p>
 </div>
 <script>
 els = Array.prototype.slice.call((wrapper = document.getElementById("wrapper"))
@@ -384,4 +384,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help rebuild - 2011-11-04 08:09:46 -->
+<!-- npm help rebuild - 2011-30-04 08:09:03 -->
diff --git a/html/doc/registry.html b/html/doc/registry.html
index 5ca29163c..f6777aa71 100644
--- a/html/doc/registry.html
+++ b/html/doc/registry.html
@@ -357,7 +357,7 @@ are CouchDB users, stored in the <a href="http://isaacs.couchone.com/_users">htt
 database.</p>
 
 <p>The registry URL is supplied by the <code>registry</code> config parameter.  See
-<code>npm help config</code> for more on managing npm's configuration.</p>
+<code><a href="config.html">npm config</a></code> for more on managing npm's configuration.</p>
 
 <h2 id="Can-I-run-my-own-private-registry">Can I run my own private registry?</h2>
 
@@ -380,7 +380,7 @@ published at all, or
 <code>"publishConfig":{"registry":"http://my-internal-registry.local"}</code>
 to force it to be published only to your internal registry.</p>
 
-<p>See <code>npm help json</code> for more info on what goes in the package.json file.</p>
+<p>See <code><a href="json.html">npm json</a></code> for more info on what goes in the package.json file.</p>
 
 <h2 id="Will-you-replicate-from-my-registry-into-the-public-one">Will you replicate from my registry into the public one?</h2>
 
@@ -452,4 +452,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help registry - 2011-11-04 08:09:46 -->
+<!-- npm help registry - 2011-30-04 08:09:03 -->
diff --git a/html/doc/scripts.html b/html/doc/scripts.html
index ee57f47cf..b3cfa39e0 100644
--- a/html/doc/scripts.html
+++ b/html/doc/scripts.html
@@ -483,7 +483,7 @@ Except for uninstall/deactivate scripts, this will cause the npm action
 to fail, and potentially be rolled back.  If the failure is minor or
 only will prevent some optional features, then it's better to just
 print a warning and exit successfully.</li><li>Try not to use scripts to do what npm can do for you.  Read through
-<code>npm help json</code> to see all the things that you can specify and enable
+<code><a href="json.html">npm json</a></code> to see all the things that you can specify and enable
 by simply describing your package appropriately.  In general, this will
 lead to a more robust and consistent state.</li><li>Inspect the env to determine where to put things.  For instance, if
 the <code>npm_config_binroot</code> environ is set to <code>/home/user/bin</code>, then don't
@@ -520,4 +520,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help scripts - 2011-11-04 08:09:47 -->
+<!-- npm help scripts - 2011-30-04 08:09:03 -->
diff --git a/html/doc/set.html b/html/doc/set.html
index 064340294..ff24dc292 100644
--- a/html/doc/set.html
+++ b/html/doc/set.html
@@ -431,7 +431,7 @@ npm ls --global --parseable --long --loglevel info</code></pre>
 
 <h2 id="Per-Package-Config-Settings">Per-Package Config Settings</h2>
 
-<p>When running scripts (see <code>npm help scripts</code>)
+<p>When running scripts (see <code><a href="scripts.html">npm scripts</a></code>)
 the package.json "config" keys are overwritten in the environment if
 there is a config param of <code>&lt;name&gt;[@&lt;version&gt;]:&lt;key&gt;</code>.  For example, if
 the package.json has this:</p>
@@ -491,7 +491,7 @@ have their <code>build</code> directories automatically ignored.</p>
 
 <ul><li>Default: Windows: <code>~/npm-cache</code>, Posix: <code>~/.npm</code></li><li>Type: path</li></ul>
 
-<p>The location of npm's cache directory.  See <code>npm help cache</code></p>
+<p>The location of <a href="'s cache directory.  See <code>npm-cache.html">npm 's cache directory.  See <code>npm-cache</a></code></p>
 
 <h3 id="color">color</h3>
 
@@ -542,7 +542,7 @@ set.</p>
 
 <p>Operates in "global" mode, so that packages are installed into the
 <code>prefix</code> folder instead of the current working directory.  See
-<code>npm help folders</code> for more on the differences in behavior.</p>
+<code><a href="folders.html">npm folders</a></code> for more on the differences in behavior.</p>
 
 <ul><li>packages are installed into the <code>prefix/node_modules</code> folder, instead of the
 current working directory.</li><li>bin files are linked to <code>prefix/bin</code></li><li>man pages are linked to <code>prefix/share/man</code></li></ul>
@@ -802,7 +802,7 @@ will fail.</p>
 <ul><li>Default: false</li><li>Type: Boolean</li></ul>
 
 <p>Set to show short usage output (like the -H output)
-instead of complete help when doing <code>npm help</code>.</p>
+instead of complete help when doing <code><a href="help.html">npm help</a></code>.</p>
 
 <h3 id="user">user</h3>
 
@@ -885,4 +885,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help set - 2011-11-04 08:09:48 -->
+<!-- npm help set - 2011-30-04 08:09:03 -->
diff --git a/html/doc/submodule.html b/html/doc/submodule.html
index 5dc67d7ba..334f964fd 100644
--- a/html/doc/submodule.html
+++ b/html/doc/submodule.html
@@ -362,7 +362,7 @@ dependencies into the submodule folder.</p>
 
 <h2 id="SEE-ALSO">SEE ALSO</h2>
 
-<ul><li>npm help json</li><li>git help submodule</li></ul>
+<ul><li><a href="json.html">npm json</a></li><li>git help submodule</li></ul>
 </div>
 <script>
 els = Array.prototype.slice.call((wrapper = document.getElementById("wrapper"))
@@ -392,4 +392,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help submodule - 2011-11-04 08:09:48 -->
+<!-- npm help submodule - 2011-30-04 08:09:03 -->
diff --git a/html/doc/view.html b/html/doc/view.html
index 0587e0df6..f63134639 100644
--- a/html/doc/view.html
+++ b/html/doc/view.html
@@ -393,7 +393,7 @@ can do this:</p>
 
 <p>"Person" fields are shown as a string if they would be shown as an
 object.  So, for example, this will show the list of npm contributors in
-the shortened string format.  (See <code>npm help json</code> for more on this.)</p>
+the shortened string format.  (See <code><a href="json.html">npm json</a></code> for more on this.)</p>
 
 <pre><code>npm view npm contributors</code></pre>
 
@@ -443,4 +443,4 @@ document.body.appendChild(toc)
 
 </script>
 </body></html>
-<!-- npm help view - 2011-11-04 08:09:49 -->
+<!-- npm help view - 2011-30-04 08:09:03 -->