changed "pip install .[dev]" to include -e option since both it and "pip install ." install the package in site-libs but in different ways (#203)

Author: cchris28

docs/practices/precommit.rst

@@ -4,7 +4,7 @@ Pre-Commit
 What is it? Why do it?
 -------------------------------------------------------------------------------
 
-``pre-commit`` is installed when running ``pip install '.[dev]'``. It's an industry 
+``pre-commit`` is installed when running ``pip install -e '.[dev]'``. It's an industry 
 standard tool that executes a set of tests prior to completing a ``git commit`` action. 
 Using pre-commit enables a quick check of your code before it's committed and checked 
 by GitHub workflows. This cuts down on code feedback time, and allows for faster 
@@ -58,4 +58,4 @@ of these that are not useful for your project.
 
 
 Many other pre-commit hooks exist, a partial list can be found in the pre-commit 
-`documentation <https://pre-commit.com/hooks.html>`_.
+`documentation <https://pre-commit.com/hooks.html>`_.

docs/source/existing_project.rst

@@ -155,7 +155,7 @@ or missing dependencies.
 .. code:: bash
 
     >> pip install -e .
-    >> pip install .'[dev]'
+    >> pip install -e .'[dev]'
 
 .. note:: 
 

docs/source/new_project.rst

@@ -91,7 +91,7 @@ Use ``pip`` to install both the standard set of dependencies as well as the
     Lots of output
     ...
 
-    >> pip install '.[dev]'
+    >> pip install -e '.[dev]'
     ...
     Lots more output
     ...
@@ -144,4 +144,4 @@ Run the following command in your terminal.
     >> pre-commit install
 
 For more information about ``pre-commit`` including a list of the checks that 
-will be run before each commit, please see :doc:`pre-commit <../practices/precommit>`.
+will be run before each commit, please see :doc:`pre-commit <../practices/precommit>`.