summaryrefslogtreecommitdiff
path: root/docs/Memory-Usage.md
diff options
context:
space:
mode:
authorYehonal <yehonal.azeroth@gmail.com>2020-05-14 16:57:53 +0200
committerGitHub <noreply@github.com>2020-05-14 16:57:53 +0200
commitb6cbbdde19be5229915baf5d764ce062c22102e1 (patch)
tree06720d78f5a5774fde26c25d8a3b405b8506875e /docs/Memory-Usage.md
parent5657c7b2e488be01e936897a52430b2374b7dbc8 (diff)
downloadwiki-b6cbbdde19be5229915baf5d764ce062c22102e1.tar.gz
wiki-b6cbbdde19be5229915baf5d764ce062c22102e1.tar.bz2
wiki-b6cbbdde19be5229915baf5d764ce062c22102e1.zip
Update Memory-Usage.md
Diffstat (limited to 'docs/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 e450200..08f2572 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 event hough you've few online players, if they explore the entire maps, those maps won't be unloaded from the RAM.
+It means 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