   'config(\.PROPERTY)?': '''
     <h4>Config</h4>
 
-    <p>npm supports configuration variables which can be set by the user using <code>npm config</code>.  The <code>config</code> option can be used to set defaults for these options.</p>
-
-    <p>Config variables are available as environment variables.  For example, if you had the config:</p>
+    <p>npm supports configuration variables which can be set by the user using <code>npm config</code>. The <code>config</code> option can be used to set defaults for these options.</p>
+
+    <p>Config variables are available as environment variables. For example, if you had the config:</p>
 
     <pre><code>"config": {
       "port": 8080

  'default': '''
    <h4>package.json</h4>

    <p>All npm packages contain a file, usually in the project root, called package.json - this file holds various metadata relevant to the project. This file is used to give information to npm that allows it to identify the project as well as handle the project's dependencies. It can also contain other metadata such as a project description, the version of the project in a particular distribution, license information, even configuration data - all of which can be vital to both npm and to the end users of the package. The package.json file is normally located at the root directory of a Node.js project.</p>

    <pre><code>{
      "name": "App",

      <li>A GitHub repo (<code>visionmedia/mocha#4727d357ea</code>)
    </ul>

    <p>As in those examples, it’s usually a good idea to specify a specific commit or tag when using git URLs (by appending the identifier after the “#” symbol).</p>
  '''

  'bundledDependencies(\.INDEX)?': '''
    <h4>Bundled Dependencies</h4>

    <p>Occasionally it’s helpful to include a local copy of a dependency (it’s folder in <code>node_modules/</code>) with the project when it’s published.</p>

    <p>Bundled dependencies are specified as an array of package names, like:</p>

