summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYehonal <yehonal.azeroth@gmail.com>2020-05-14 16:57:08 +0200
committerGitHub <noreply@github.com>2020-05-14 16:57:08 +0200
commit5657c7b2e488be01e936897a52430b2374b7dbc8 (patch)
tree35a50fadc05c443d1ff848e5b0134c9e89e9fdc3
parentf09028eed1c07f3241dbf1dc74ea8f33dd7531c7 (diff)
downloadwiki-5657c7b2e488be01e936897a52430b2374b7dbc8.tar.gz
wiki-5657c7b2e488be01e936897a52430b2374b7dbc8.tar.bz2
wiki-5657c7b2e488be01e936897a52430b2374b7dbc8.zip
Update Memory-Usage.md
-rw-r--r--docs/Memory-Usage.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Memory-Usage.md b/docs/Memory-Usage.md
index a258485..e450200 100644
--- a/docs/Memory-Usage.md
+++ b/docs/Memory-Usage.md
@@ -13,7 +13,7 @@ AzerothCore is based on SunwellCore (a fork from TC). SunwellCore was a public s
We recommend at least 16 GB as the server will gradually cache the world maps as the players explore them which finally takes up to at least 11 GB of RAM usage.
-That's mean that eventhough you've few players online, if they explore the entire maps they won't be unloaded from the RAM.
+That's mean that event hough you've few online players, if they explore the entire maps, those maps won't be unloaded from the RAM.
It's an architectural choice granting "high performances" on heavy usage.
We can also try to explain you it with a draw