   '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>
+    <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",

    <p>Some rules:</p>
    <ul>
      <li>The name must be shorter than 214 characters. This includes the scope for scoped packages.
      <li>The name can't start with a dot or an underscore.
      <li>New packages must not have uppercase letters in the name.
      <li>The name ends up being part of a URL, an argument on the command line, and a folder name. Therefore, the name can't contain any non-URL-safe characters.
    </ul>

    <p>Some tips:</p>
    <ul>
      <li>Don't use the same name as a core Node module.
      <li>Don't put "js" or "node" in the name.  It's assumed that it's js, since you're writing a package.json file, and you can specify the engine using the "engines" field.
      <li>The name will probably be passed as an argument to require(), so it should be something short, but also reasonably descriptive.
      <li>You may want to check the <a href="https://npmjs.com">npm registry</a> to see if there's something by that name already, before you get too attached to it.
    </ul>

    <p>A name can be optionally prefixed by a scope, e.g. <code>@myorg/mypackage</code>.</p>

    <p>Specify the place where your code lives.</p>

    <p>For example:</p>

    <pre><code>{
      "type": "git",
      "url": "https://github.com/npm/npm.git"
    }</code></pre>

    <p>The URL should be a publicly available (perhaps read-only) url that can be handed
    directly to a VCS program without any modification. It should not be a url to an
    html project page that you put in your browser. It’s for computers.</p>

    <p>For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
    shortcut syntax you use for <code>npm install</code>:</p>
