doc: updated doc and readme

diff --git a/README.md b/README.md
index f465e0600e63b85c7c7e35d2eec6300c9470dabb..b2c3b4c61f07641cb806db88c7cb47b9d9305145 100644 (file)
--- a/README.md
+++ b/README.md
@@ -6,14 +6,22 @@
 [![Documentation Status](https://readthedocs.org/projects/knot-resolver/badge/?version=latest)](https://readthedocs.org/projects/knot-resolver/?badge=latest)
 
 
-The Knot DNS Resolver is a minimalistic caching resolver implementation. The project provides both a resolver
-library and a small daemon. Modular architecture of the library keeps the core tiny and efficient, and provides
-a state-machine like API for extensions. There are two built-in modules: *iterator* and *cache*,
-and each module can be flipped on and off.
+The Knot DNS Resolver is a caching full resolver implementation written in C and [LuaJIT][luajit], including both a resolver
+library and a daemon. Modular architecture of the library keeps the core tiny and efficient, and provides
+a state-machine like API for extensions. There are three built-in modules - *iterator*, *cache*, *validator*, and many external.
+
+The Lua modules, switchable and shareable cache, and fast FFI bindings makes it great to tap into resolution process, or be used for your recursive DNS service. It's the [OpenResty][openresty] of DNS.
+
+The server adopts a [different scaling strategy][scaling] than the rest of the DNS recursors - no threading, shared-nothing architecture (except MVCC cache that may be shared). You can start and stop additional nodes depending on the contention without downtime.
 
 ### Try it out?
 
-The Knot DNS Resolver is currently in an early development phase, you shouldn't put it in the production right away.
+Keep in mind that the Knot DNS Resolver is in beta. While it's being tested by the [DNS test harness][https://gitlab.labs.nic.cz/knot/deckard], we'll be super glad to hear out your feedback!
+
+### Building from sources
+
+The Knot DNS Resolver [depends][depends] on the 2.0.1 version of the Knot DNS library, [LuaJIT][luajit] and [libuv][libuv].
+See the [Building project][depends] documentation page for more information.
 
 ### Docker image
 
@@ -25,24 +33,22 @@ $ docker run cznic/knot-resolver
 
 See the build page [registry.hub.docker.com/u/cznic/knot-resolver](https://registry.hub.docker.com/u/cznic/knot-resolver) for more information and options.
 
-### Building from sources 
-
-The Knot DNS Resolver [depends][depends] on the pre-release version of the Knot DNS library and other projects.
-See the [Building project][depends] documentation page for more information.
-
 ### Running
 
 The project builds a resolver library in the `lib` directory, and a daemon in the `daemon` directory.
 
 ```
-$ ./daemon/kresd -h
-$ ./daemon/kresd [working_directory]
+$ kresd -h
 ```
 
 See the documentation at [knot-resolver.readthedocs.org][doc].
 
 [depends]: http://knot-resolver.readthedocs.org/en/latest/build.html
 [doc]: http://knot-resolver.readthedocs.org/en/latest/index.html
+[scaling]: http://knot-resolver.readthedocs.org/en/latest/daemon.html#scaling-out
+[luajit]: http://luajit.org/
+[libuv]: https://github.com/libuv/libuv
+[openresty]: https://openresty.org/
 
 ### Contacting us
 

diff --git a/daemon/README.rst b/daemon/README.rst
index 24c0c8b8881c1faf0ad92a22e34ff5828292958e..0512e5ba6b4f84d71b0641cbb0255762e1739290 100644 (file)
--- a/daemon/README.rst
+++ b/daemon/README.rst
@@ -65,7 +65,7 @@ You can add start and stop processes on runtime based on the load.
 
 .. code-block:: bash
 
-       $ kresd -f 4 rundir > kresd.log &
+   $ kresd -f 4 rundir > kresd.log &
    $ kresd -f 2 rundir > kresd_2.log & # Extra instances
    $ pstree $$ -g
    bash(3533)─┬─kresd(19212)─┬─kresd(19212)