From 3955844f140a33cd8096a9aa3536672fd7e165e2 Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Thu, 7 Nov 2019 11:51:47 +0300 Subject: [PATCH] minor --- 1-js/01-getting-started/1-intro/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/01-getting-started/1-intro/article.md b/1-js/01-getting-started/1-intro/article.md index 1d2997e0..7537a46b 100644 --- a/1-js/01-getting-started/1-intro/article.md +++ b/1-js/01-getting-started/1-intro/article.md @@ -38,7 +38,7 @@ Engines are complicated. But the basics are easy. 2. Then it converts ("compiles") the script to the machine language. 3. And then the machine code runs, pretty fast. -The engine applies optimizations at each step of the process. It even watches the compiled script as it runs, analyzes the data that flows through it, and applies optimizations to the machine code based on that knowledge. When it's done, scripts run quite fast. +The engine applies optimizations at each step of the process. It even watches the compiled script as it runs, analyzes the data that flows through it, and further optimizes the machine code based on that knowledge. ``` ## What can in-browser JavaScript do?