From 5242bba5431f455c33ab9a7d8284e7fca434fbeb Mon Sep 17 00:00:00 2001
From: PMB79 <44287599+PMB79@users.noreply.github.com>
Date: Wed, 7 Nov 2018 22:40:42 +0000
Subject: [PATCH] Correction of grammar. (#22146)

---
 guide/english/python/virtual-environments/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/guide/english/python/virtual-environments/index.md b/guide/english/python/virtual-environments/index.md
index 00c43ea53c..ec07f18bf6 100644
--- a/guide/english/python/virtual-environments/index.md
+++ b/guide/english/python/virtual-environments/index.md
@@ -4,9 +4,9 @@ title: Virtual Environments
 
 ## Virtual Environments
 
-Virtual environments can be described as isolated installation directories. This isolation allows you to localized the installation of your project's dependencies, without forcing you to install them system-wide.
+Virtual environments can be described as isolated installation directories. This isolation allows you to localize the installation of your project's dependencies, without forcing you to install them system-wide.
 
-Imagine you have two applications App1 and App2. Both require the package Pak, but with different versions. If you install Pak version 2.3 for App1, you would not be able to run App2, because it requires version 3.1. Here is when virtual environments come in handy.
+Imagine you have two applications App1 and App2. Both require the package Pak, but each requires a different version. If you install Pak version 2.3 for App1, you would not be able to run App2, because it requires version 3.1. Here is when virtual environments come in handy.
 
 Benefits:
 * You can have multiple environments, with multiple sets of packages, without conflicts among them. This way, different projects' requirements can be satisfied at the same time.