 
     <p>For example, if you’d like your <code>cli.js</code> file to be executed when the user runs <code>myapp</code> on the command line, you could specify:</p>
 
-    <pre><code>{ "bin": { "myapp": "./cli.js" } }</code></pre>
+    <pre><code>"bin": { "myapp": "./cli.js" }</code></pre>
 
     <p>If you only have a single executable, and you’d like the command line program to have the same name as your package, you can just specify the file to be executed as a string:</p>
 

  <p>Packages can be found using the <code>npm search</code> command, or on <a href="http://npmjs.com">npmjs.com</a>.</p>

  <p>Version requirements are specified using <a href="http://ricostacruz.com/cheatsheets/semver.html">semver</a>.</p>
'''

context =
  'default': '''

    <p>Dev dependencies work exactly as <code>dependencies</code>, but they are not installed when a user installs your package without downloading the source (unless they provide the <code>--dev</code> option).</p>

    <p>It often makes sense to include build and test tools as dev dependencies, so end users don’t have to install them if their not required to use the package.</p>
  ''' + depInfo('devDependencies')

  'peerDependencies': '''
    <h4>Peer Dependencies</h4>
