summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorOdysseas Lamtzidis <odyslam@gmail.com>2020-12-14 21:30:24 +0200
committerGitHub <noreply@github.com>2020-12-14 12:30:24 -0700
commit27723d8df9a64870827951313dbd5e03810942d5 (patch)
tree5492671dd158be1f486709eaf9753e5f7db235a2
parent84b66311c89aac700d5d637da2a99e1037692dea (diff)
fix typo in performance.md (#10386)
diminuitive --> diminutive
-rw-r--r--docs/guides/configure/performance.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/guides/configure/performance.md b/docs/guides/configure/performance.md
index 50087877b6..954a03cb20 100644
--- a/docs/guides/configure/performance.md
+++ b/docs/guides/configure/performance.md
@@ -18,7 +18,7 @@ single core.
But not everyone has such powerful systems at their disposal. For example, you might run the Agent on a cloud VM with
only 512 MiB of RAM, or an IoT device like a [Raspberry Pi](/docs/guides/monitor/pi-hole-raspberry-pi.md). In these
-cases, reducing Netdata's footprint beyond its already diminuitive size can pay big dividends, giving your services more
+cases, reducing Netdata's footprint beyond its already diminutive size can pay big dividends, giving your services more
horsepower while still monitoring the health and the performance of the node, OS, hardware, and applications.
## Prerequisites