From eeca775306a2f5bcb910f634802ae9c4f05de08a Mon Sep 17 00:00:00 2001
From: Jack Evoniuk <45554423+Evoniuk@users.noreply.github.com>
Date: Sun, 24 Feb 2019 03:24:31 -0800
Subject: [PATCH] missing word

---
 .../05-native-prototypes/article.md                             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/1-js/07-object-oriented-programming/05-native-prototypes/article.md b/1-js/07-object-oriented-programming/05-native-prototypes/article.md
index 4777f356..f0dac564 100644
--- a/1-js/07-object-oriented-programming/05-native-prototypes/article.md
+++ b/1-js/07-object-oriented-programming/05-native-prototypes/article.md
@@ -123,7 +123,7 @@ During the process of development we may have ideas which new built-in methods w
 
 Prototypes are global, so it's easy to get a conflict. If two libraries add a method `String.prototype.show`, then one of them overwrites the other one.
 
-In modern programming, there is only one case when modifying native prototypes is approved. That's polyfills. In other words, if there's a method in JavaScript specification that is not yet supported by our JavaScript engine (or any of those that we want to support), then may implement it manually and populate the built-in prototype with it.
+In modern programming, there is only one case when modifying native prototypes is approved. That's polyfills. In other words, if there's a method in JavaScript specification that is not yet supported by our JavaScript engine (or any of those that we want to support), then we may implement it manually and populate the built-in prototype with it.
 
 For instance: