summaryrefslogtreecommitdiffstats
path: root/doc/requirements.rst
diff options
context:
space:
mode:
authorZuzana Ansorgova <zuzana.ansorgova@nic.cz>2015-07-01 13:05:17 +0200
committerZuzana Ansorgova <zuzana.ansorgova@nic.cz>2015-07-01 13:05:17 +0200
commit82464724a712da3e13c36996abe052c7947ff1cc (patch)
treea2bfd3b3da4c424ddb21e12d04719d0a189b8838 /doc/requirements.rst
parentdoc: fix typo in module name (diff)
downloadknot-82464724a712da3e13c36996abe052c7947ff1cc.tar.xz
knot-82464724a712da3e13c36996abe052c7947ff1cc.zip
doc: documentation fixes
Diffstat (limited to 'doc/requirements.rst')
-rw-r--r--doc/requirements.rst14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/requirements.rst b/doc/requirements.rst
index aa7560d36..0a8cf1a8b 100644
--- a/doc/requirements.rst
+++ b/doc/requirements.rst
@@ -13,9 +13,9 @@ installations, and a commodity server or a virtual solution will be
sufficient in most cases.
However, please note that there are some scenarios that will require
-administrator attention and testing of exact requirements before
-deploying Knot DNS in production. These cases include deployment for a
-large number of zones (DNS hosting), a large number of records in one
+administrator's attention and a testing of exact requirements before
+deploying Knot DNS to a production environment. These cases include deployment for a
+large number of zones (DNS hosting), large number of records in one
or more zones (TLD) or large number of requests.
CPU requirements
@@ -31,10 +31,10 @@ Memory requirements
-------------------
Knot DNS implementation focuses on performance and thus can be quite
-demanding for memory. The rough estimate for memory requirements is
-3 times of the size of the zone in text format. Again this is only
+memory demanding. The rough estimate for memory requirements is
+3 times the size of the zone in text format. Again this is only
an estimate and you are advised to do your own measurements before
-deploying Knot DNS into production.
+deploying Knot DNS to production.
Also note that to ensure uninterrupted serving of the zone, Knot DNS
employs a Read-Copy-Update mechanism instead of locking and thus
@@ -47,4 +47,4 @@ Operating system
Knot DNS itself is written in a portable way, but it depends on
several libraries. Namely userspace-rcu, which could be a constraint
when it comes to the operating system support. Knot DNS can be compiled
-and run on most of UNIX-like systems, such as Linux, \*BSD, and OS X.
+and run on most UNIX-like systems, such as Linux, \*BSD, and OS X.