From 7c97edc67ccd2643d66651286cd6c54371e5d429 Mon Sep 17 00:00:00 2001 From: Mau Di Bert Date: Sat, 2 Mar 2019 08:54:52 -0300 Subject: [PATCH] typo --- 1-js/06-advanced-functions/09-call-apply-decorators/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/06-advanced-functions/09-call-apply-decorators/article.md b/1-js/06-advanced-functions/09-call-apply-decorators/article.md index 3f86b0d3..75c510d1 100644 --- a/1-js/06-advanced-functions/09-call-apply-decorators/article.md +++ b/1-js/06-advanced-functions/09-call-apply-decorators/article.md @@ -305,7 +305,7 @@ If we look more closely, there's a minor difference between such uses of `call` So, these calls complement each other. Where we expect an iterable, `call` works, where we expect an array-like, `apply` works. -And if `args` is both iterable and array-like, like a real array, then we technically could use any of them, but `apply` will probably be faster, because it's a single operation. Most JavaScript engines internally optimize is better than a pair `call + spread`. +And if `args` is both iterable and array-like, like a real array, then we technically could use any of them, but `apply` will probably be faster, because it's a single operation. Most JavaScript engines internally optimize it better than a pair `call + spread`. One of the most important uses of `apply` is passing the call to another function, like this: