diff --git a/readme.md b/readme.md
index 407c9e272c13f599516d51cad671f286818a4df2..2f1c80ce6c9ec0762e63818235063810567391bf 100644
--- a/readme.md
+++ b/readme.md
@@ -1,29 +1,31 @@
 
 # Python - Virtual Environment Example
 
-## Author
-Brandon Rodriguez
-
 ## Description
 Explanation of Python virtual environments, plus helper bash script.
 
 ## Bash Helper Script
-To use the bash helper script, copy the contents of `helper_script.sh` and append it to the `bashrc` file located in
+To use the bash helper script, copy the contents of `helper_script.sh` and append it to the `.bashrc` file located in
 your user's home directory.
 
 This script will modify the cd command to automatically detect and load/unload virtual environments when traversing
 folders.
 
 ## Virtual Environments
-Virtual Environments are a way separate Python package installations, to prevent conflicts between different projects.
+Virtual Environments are a way to separate Python package installations, in order to prevent conflicts between different
+project setups.
+
+Through Virtual Environments, you can also easily access different Python versions between different projects.
 
-Through Virtual Environments, you can even easily access different Python versions between different projects.
-For example, you could have a Python3.7 installation for Django, a Python3.5 installation for wxPython, and a Python2.7 installation for general script usage.
+For example, you could have a Python3.7 installation for Django, a Python3.5 installation for wxPython, and a Python2.7
+installation for general script usage.
 
-As of writing this, there are two recommended ways to setup Virtual Environments: the `virtualenv` Python package or the `venv` package.
+As of writing this, there are two recommended ways to setup Virtual Environments: the `virtualenv` Python package or the
+`venv` package.
 
 ### Venv
-The `venv` package is generally shipped with Python3, although some OS distros separate it into a distro package (for example, on Ubuntu, install with `apt install python3-venv`).
+The `venv` package is generally shipped with Python3, although some OS distros separate it into a distro package (for
+example, on Ubuntu, install with `apt install python3-venv`).
 
 This method will only work with Python version 3 or higher.
 
@@ -54,11 +56,13 @@ Either of the above methods should essentially provide the same result.
         * Ex: `. ./my_env/Scripts/activate`
     * To unload an environment, use `deactivate`.
 
-Another way to check is through the `which python`, `which pip`, `python -V`, and `pip -V` commands.
+You can verify the environment loaded through the `which python`, `which pip`, `python -V`, and `pip -V` commands.
 
 ## Organizing Virtual Environments
 There are two general practices for organizing virtual environments.
 
+Generally speaking, most prefer to use the second option, which creates a new environment for each project.
+
 ### Multiple Environments in a Central Location
 This method involves creating all your virtual environments in a single location (for example, `~/Env/`).
 
@@ -71,7 +75,7 @@ above commands.
 ### An Environment for Each Project
 This method involves creating an environment (labeled `.venv`) at the root of every project.
 
-For example, if you might have `/my_project/.venv`, and would repeat for every Python project.
+For example, you might have `/my_project/.venv`, and would repeat for every Python project.
 
 The benefit of this method is that you can set up your console to automatically load the environment on cd (see attached
 helper script). However, if you have multiple projects that use the same packages, you'll still need to create separate