diff --git a/docs/installation.md b/docs/installation.md
index e6fcec58..fca90719 100644
--- a/docs/installation.md
+++ b/docs/installation.md
@@ -161,6 +161,6 @@ that ensures all commands have access to your installed packages with `$ pipenv
 - Pipenv automatically maps projects to their specific virtualenvs.
 - By default, the virtualenv is stored globally with the name of the project’s root directory plus the hash of the full path to the project's root (e.g., `my_project-a3de50`).
 - Should you change your project's path, you break such a default mapping and pipenv will no longer be able to find and to use the project's virtualenv.
-- If you must move or rename a directory managed by pipenv, run 'pipenv --rm' before renaming or moving your project directory. Then, after renaming or moving the directory run 'pipenv install' to recreate the virtualenv. 
+- If you must move or rename a directory managed by pipenv, run 'pipenv --rm' before renaming or moving your project directory. Then, after renaming or moving the directory run 'pipenv install' to recreate the virtualenv.
 - Customize this behavior with `PIPENV_CUSTOM_VENV_NAME` environment variable.
 - You might also prefer to set `PIPENV_VENV_IN_PROJECT=1` in your .env or .bashrc/.zshrc (or other shell configuration file) for creating the virtualenv inside your project's directory.
diff --git a/docs/virtualenv.md b/docs/virtualenv.md
index 30c297f6..7e5eca37 100644
--- a/docs/virtualenv.md
+++ b/docs/virtualenv.md
@@ -26,5 +26,5 @@ The logical place to specify this would be in a user's `.env` file in the root o
 By default pipenv creates a virtualenv for your project and gives it a name. The default name is how pipenv maps the individual project to the correct virtualenv. Pipenv names the virtualenv with the name of the project’s root directory plus the hash of the full path to the project's root (e.g., `my_project-a3de50`).
 
 If you rename or move the project folder this will change the project path.  Then, pipenv will no longer be able to find your virtualenv and it will make a new virtualenv. This leaves you with the old virtualenv still lying around on you system.  Luckily the fix is simple.
-- Run 'pipenv --rm' *before* renaming or moving your project directory 
-- Then, after renaming or moving the directory run 'pipenv install' to recreate the virtualenv
\ No newline at end of file
+- Run 'pipenv --rm' *before* renaming or moving your project directory
+- Then, after renaming or moving the directory run 'pipenv install' to recreate the virtualenv