From effc64ab00e87993a364176c4b16cf40ab9e7574 Mon Sep 17 00:00:00 2001
From: Abdullah Manzoor <42546451+misterabd@users.noreply.github.com>
Date: Mon, 15 Apr 2019 09:39:50 +0100
Subject: [PATCH] Update article.md

---
 1-js/06-advanced-functions/11-currying-partials/article.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/1-js/06-advanced-functions/11-currying-partials/article.md b/1-js/06-advanced-functions/11-currying-partials/article.md
index 5bb2e5df..b97e6a5f 100644
--- a/1-js/06-advanced-functions/11-currying-partials/article.md
+++ b/1-js/06-advanced-functions/11-currying-partials/article.md
@@ -65,9 +65,9 @@ alert( triple(5) ); // = mul(3, 5) = 15
 
 Why do we usually make a partial function?
 
-Here our benefit is that we created an independent function with a readable name (`double`, `triple`). We can use it and don't write the first argument of every time, cause it's fixed with `bind`.
+The benefit is that we can create an independent function with a readable name (`double`, `triple`). We can use it and not provide first argument of every time as it's fixed with `bind`.
 
-In other cases, partial application is useful when we have a very generic function, and want a less universal variant of it for convenience.
+In other cases, partial application is useful when we have a very generic function and want a less universal variant of it for convenience.
 
 For instance, we have a function `send(from, to, text)`. Then, inside a `user` object we may want to use a partial variant of it: `sendTo(to, text)` that sends from the current user.