Skip to content

Commit ffd324b

Browse files
committed
Merge branch 'Dnyanu76-patch-1'
2 parents 90c9791 + 43aad4a commit ffd324b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ v20.8.0
7272
```
7373

7474
## 1.2 Downloading the pre-built binaries and starting the server
75-
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.
75+
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.
7676

7777

7878
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
106106
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)
107107

108108

109-
Here's what you should do when the benchmark run was not sucessful. Let's assume the benchmark printed the following to the console:
109+
Here's what you should do when the benchmark run was not successful. Let's assume the benchmark printed the following to the console:
110110
```
111111
================================
112112
The following benchmarks failed:
113113
================================
114114
Executing frameworks/non-keyed/ef-js and benchmark 04_select1k failed: No paint event found
115-
run was not completely sucessful Benchmarking failed with errors
115+
run was not completely successful Benchmarking failed with errors
116116
```
117117
You'll now have to run the benchmark again for those that failed like that:
118118
```

0 commit comments

Comments
 (0)