Merge branch 'master' into refactor-webdriver

Author: nakrovati

README.md

@@ -46,11 +46,11 @@ results might be for mixed browser versions, number of runs per benchmark may va
 
 ## Keyed vs non-keyed frameworks
 
-Some frameworks like react, vue.js or angular allow to create a 1:1-relationship between a data item and a DOM node by assigning a “key” attribute (or for angular specifying “trackBy” in *ngFor). If you use some identifier of the data as the key you get the “keyed” mode. Any update to the data will update the associated DOM node. If you reorder the list, the DOM nodes will be reordered accordingly.
+Some frameworks like React, Vue.js or Angular, allow you to create a 1:1 relationship between a data item and a DOM node by assigning a “key” attribute (or for Angular, specifying “trackBy” in *ngFor). If you use some identifier of the data as the key, you get the “keyed” mode. Any update to the data will update the associated DOM node. If you reorder the list, the DOM nodes will be reordered accordingly.
 
-The other mode is “non-keyed” and this is what e.g. vue.js uses by default for lists. In this mode a change to the data items can modify DOM nodes that were associated with other data before. This can be more performant, since costly DOM operations can be avoided (e.g. first removing old nodes, and the adding new nodes) and the existing DOM nodes are updated to display the new data. For react and angular using the item index as the key uses “non-keyed” mode for those frameworks.
+The other mode is “non-keyed” and this is what e.g. vue.js uses by default for lists. In this mode, a change to the data items can modify DOM nodes that were associated with other data before. This can be more performant, since costly DOM operations can be avoided (e.g. first removing old nodes and then adding new nodes) and the existing DOM nodes are updated to display the new data. For React and Angular, using the item index as the key uses “non-keyed” mode for those frameworks.
 
-Depending on your requirements the “non-keyed” mode can be a performance gain or can cause severe problems so one must choose carefully the mode and check that the framework supports that mode.
+Depending on your requirements, the “non-keyed” mode can be a performance gain or can cause severe problems, so one must carefully choose the mode and check that the framework supports that mode.
 
 Read more here: [https://www.stefankrause.net/wp/?p=342](https://www.stefankrause.net/wp/?p=342)
 
@@ -72,7 +72,7 @@ v20.8.0
 ```
 
 ## 1.2 Downloading the pre-built binaries and starting the server
-Builiding all frameworks can be challenging. There's a new way that allows to skip that and just run the benchmark without builiding all implementationss.
+building all frameworks can be challenging. There's a new way that allows to skip that and just run the benchmark without builiding all implementations.
 
 
 Start with checking out a tagged release like that. Pick the release that you want (e.g. chrome 100):
@@ -106,13 +106,13 @@ npm run results
 Open js-framework-benchmark/webdriver-ts-results/table.html in a browser and take a look at the results. You can open the result table with the link [http://localhost:8080/webdriver-ts-results/table.html](http://localhost:8080/webdriver-ts-results/table.html)
 
 
-Here's what you should do when the benchmark run was not sucessful. Let's assume the benchmark printed the following to the console:
+Here's what you should do when the benchmark run was not successful. Let's assume the benchmark printed the following to the console:
 ```
 ================================
 The following benchmarks failed:
 ================================
 Executing frameworks/non-keyed/ef-js and benchmark 04_select1k failed: No paint event found
-run was not completely sucessful Benchmarking failed with errors
+run was not completely successful Benchmarking failed with errors
 ```
 You'll now have to run the benchmark again for those that failed like that:
 ```

frameworks/keyed/angular-nozone/.browserslistrc renamed to frameworks/keyed/angular-cf-nozone/.browserslistrc

@@ -68,18 +68,18 @@
           "builder": "@angular-devkit/build-angular:dev-server",
           "configurations": {
             "production": {
-              "browserTarget": "angular:build:production"
+              "buildTarget": "angular:build:production"
             },
             "development": {
-              "browserTarget": "angular:build:development"
+              "buildTarget": "angular:build:development"
             }
           },
           "defaultConfiguration": "development"
         },
         "extract-i18n": {
           "builder": "@angular-devkit/build-angular:extract-i18n",
           "options": {
-            "browserTarget": "angular:build"
+            "buildTarget": "angular:build"
           }
         }
       }