CONTRIBUTING.md

@@ -9,7 +9,7 @@
 ## Fork Clone Workflow
 - The standard workflow for contributing on GitHub is called **Fork/Clone**.  For those who may not be familiar, here is a brief summary and some reference links.  
   - *We assume you are familiar with **git** basics: `git clone`, `git commit`, etc*.
-- Note: a "Fork" is just a `git clone` *that is created on, and that lives on, GitHub*.  You create a fork using the **Fork** button on GitHub: This allows GitHub to track the relationship between the original github repository, and your Fork.
+- Note: a "Fork" is just a `git clone` *that is created on, and that lives on, GitHub.com*.  You create a fork using the **Fork** button on GitHub: This allows GitHub to track the relationship between the original github repository, and your Fork.  (In that sense a "fork" is slightly more than just a plain "clone", but only as much as GitHub.com adds some tracking and other minor features to make integration easier).
 - The basic workflow is:
   1. Create a **Fork** of the mplfinance repository.  (See references below for details.)  The fork will exist under *your* github account.  
   2. **Clone** *your* Fork to your local machine (`git clone`).
@@ -31,6 +31,7 @@
 - I am not super strict about adhearing to every aspect of PEP 8, *nor am I lenient*.  I tend to walk the middle of the road: If something is a good and common, then it should be adheared to.  
 - Here are a few items that I (perhaps uniquely) tend to care about in particular:
   - If you write code, please don't use tabs; rather use spaces.
+  - If you work on a pre-existing code file, please try to more-or-less emulate the style that already exists in that file.
   - If you add a significant feature --that is, a feature for which explaining its usage takes more than just a few sentences-- please also create a "tutorial notebook" for that feature.  **[For examples of tutorial notebooks, please see the jupyter notebooks in the examples folder.](https://github.com/matplotlib/mplfinance/tree/master/examples)**
   - If you add a significant feature, please also create a regression test file **[in the tests folder](https://github.com/matplotlib/mplfinance/tree/master/tests)**, similar to the other regression tests that are there.  *Often, the simplest way to do this is to take a few of the examples from the feature's "tutorial notebook"* (see previous point).
-  - If you work on a pre-existing code file, please try to more-or-less emulate the style that already exists in that file.
+