[doc] Updating CONTRIBUTING

CONTRIBUTING.md

@@ -57,8 +57,8 @@ You can contact him through:
   * Discord
   * [Reddit](https://www.reddit.com/user/chapt3r/)
 
-Otherwise, here are some general guidelines for determining what types of changes 
-are okay to contribute:
+Otherwise, here are some general guidelines for determining what types of
+changes are okay to contribute:
 
 ##### Contributions that Will Most Likely Be Accepted
 * Bug Fixes
@@ -88,12 +88,16 @@ the following rules:
    the changes to the UI
  - If your changes affect Netscript, provide some
    scripts that can be used to test the Netscript changes.
- - Do not check in any bundled files (`dist\*.bundle.js`). These will be
-   updated as part of official releases.
+ - Ensure you have run `npm run lint` to make sure your changes conform to the
+   rules enforced across the code base. The command will fail if any of the
+   linters find a violation.
+ - Do not check in any bundled files (`dist\*.bundle.js`) or the `index.html`
+   in the root of the repository. These will be updated as part of official
+   releases.
 
 ## As a Documentor
-To contribute to BitBurner documentation, you will need to have Python
-installed, along with [Sphinx](http://www.sphinx-doc.org).
+To contribute to and view your changes to the BitBurner documentation, you will
+need to have Python installed, along with [Sphinx](http://www.sphinx-doc.org).
 
 Before submitting your code for a pull request, please try to follow these
 rules:
@@ -103,3 +107,5 @@ rules:
  - Rebase your branch if necessary
  - When submitting the pull request, make sure that the base fork is
    _danielyxie/bitburner_ and the base is _dev_.
+ - Do not check in any generated files under `doc\`. The documentation is built
+   automatically by ReadTheDocs.