aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJonas Karlsson <jonas.karlsson@qt.io>2021-02-17 15:08:53 +0100
committerJonas Karlsson <jonas.karlsson@qt.io>2021-02-25 13:29:51 +0000
commit7ef9d3700c967b8f67f078d86ca0ef2c7e041fa5 (patch)
tree84a83e229fbe633f54ceb5459fa6743a566ab25a
parent3f74ef5f41a24dc1ee91cca876d29777cf636fa2 (diff)
Readme: fix typos
Task-Id: QTBUG-78695 Change-Id: If7e8e5e9d631d9eb84bbdc3fd7c02e01ab24440c Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>
-rw-r--r--benchmarks/benchmarks.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/benchmarks/benchmarks.md b/benchmarks/benchmarks.md
index dace5dd..f8884b9 100644
--- a/benchmarks/benchmarks.md
+++ b/benchmarks/benchmarks.md
@@ -39,7 +39,7 @@ timing out and hanging, as well as on high-end hardware without acheiving 60fps
## The root level declarations
In the example above, we're testing the creation speed of the `Rectangle` delegate, so we're using `CreationBenchmark`.
-There are three types of rool level declarations allowed:
+There are three types of root level declarations allowed:
- Benchmark
- The basic QMLBench type.
- Good for testing performance of operations with fixed durations, such as animations.
@@ -65,7 +65,7 @@ There are three types of rool level declarations allowed:
In general, it is good practice to set both values so the benchmark can be used with any shell type.
### count
-Used in `susained-fps shell` mode. The benchmark will alter this value trying to achieve 60fps
+Used in `sustained-fps shell` mode. The benchmark will alter this value trying to achieve 60fps
(or rather, the screen's refresh rate). Set this value to as a starting point for the benchmark to
try first.