From 3e0281fa0655c9bb35f68f3d045b60e08a0ac3b9 Mon Sep 17 00:00:00 2001 From: ShroXd Date: Wed, 20 Jan 2021 11:19:42 +0800 Subject: [PATCH] docs: update src/guide/optimizations.md --- src/guide/optimizations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guide/optimizations.md b/src/guide/optimizations.md index 46303af8c5..b85fe35766 100644 --- a/src/guide/optimizations.md +++ b/src/guide/optimizations.md @@ -10,7 +10,7 @@ Now that we know how watchers are updating the components, you might ask how tho -We make a copy of the DOM in JavaScript called the Virtual DOM, we do this because touching the DOM with JavaScript is computationally expensive. While performing updates in JavaScript is cheap, finding the required DOM nodes and updating them with JS is expensive. So we batch calls, and change the DOM all at once. +We make a copy of the DOM in JavaScript called the Virtual DOM, we do this because touching the DOM with JavaScript is computationally expensive. While performing updates in JavaScript is cheap, finding the required DOM nodes and updating them with JavaScript is expensive. So we batch calls, and change the DOM all at once. The Virtual DOM is a lightweight JavaScript object, created by a render function. It takes three arguments: the element, an object with data, props, attrs and more, and an array. The array is where we pass in the children, which have all these arguments too, and then they can have children and so on, until we build a full tree of elements.