aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuck <git@lucko.me>2020-04-25 20:39:00 +0100
committerGitHub <noreply@github.com>2020-04-25 20:39:00 +0100
commit20b34c16d796e5901381e3a5a6be42e5df3c03cf (patch)
treeff8a5766bce36f1a71963162955dcecc9c93e91b
parent706a8768b5fc536ed746788cd9c65c7254df6bb4 (diff)
downloadspark-20b34c16d796e5901381e3a5a6be42e5df3c03cf.tar.gz
spark-20b34c16d796e5901381e3a5a6be42e5df3c03cf.tar.bz2
spark-20b34c16d796e5901381e3a5a6be42e5df3c03cf.zip
Fix typo
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index d184097..d084ee4 100644
--- a/README.md
+++ b/README.md
@@ -66,7 +66,7 @@ These metrics include:
* **TPS** - ticks per second, to a more accurate degree indicated by the /tps command
* **Tick Durations** - how long each tick is taking (min, max and average)
* **CPU Usage** - how much of the CPU is being used by the server process, and by the overall system
-* **Memory Usage** - much much memory is being used by the process
+* **Memory Usage** - how much memory is being used by the process
* **Disk Usage** - how much disk space is free/being used by the system
As well as providing tick rate averages, spark can also **monitor individual ticks** - sending a report whenever a single tick's duration exceeds a certain threshold. This can be used to identify trends and the nature of performance issues, relative to other system or game events.