From c7b503fda3b3ed06ac711364e4e726bddfb427d6 Mon Sep 17 00:00:00 2001
From: Kenneth Reitz <me@kennethreitz.org>
Date: Tue, 16 May 2017 12:06:15 -0400
Subject: [PATCH] Update README.rst

---
 README.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.rst b/README.rst
index 6c9a52f7..856d1c68 100644
--- a/README.rst
+++ b/README.rst
@@ -30,7 +30,7 @@ Pipenv automatically creates and manages the virtualenvs of your projects, as we
 
 The propblems that Pipenv seeks to solve are multi-faceted:
 
-- When using Pipenv, you no longer need to use pip and virtualenv seperately. They work together.
+- When using Pipenv, you no longer need to use ``pip`` and ``virtualenv`` seperately. They work together.
 - Managing a ``requirements.txt`` file `can be problematic <https://www.kennethreitz.org/essays/a-better-pip-workflow>`_, so Pipenv uses the upcoming ``Pipfile`` and ``Pipfile.lock`` instead, which is superior for basic use cases.