Updated the README file.

README

@@ -23,7 +23,7 @@ Clang supports atomics since version 2.9.
 
 By default Knot DNS is distributed with a slower zone file parser because of
 smaller source file and quick compile time. In most cases it is sufficient.
-If you plan to process large zone files, it is recomended to build Knot DNS
+If you plan to process large zone files, we recommend to build Knot DNS
 using ./configure --enable-fastparser. In this case Ragel compiler is required
 and it is normal if the C compiler takes much more time (minutes).
 
@@ -41,7 +41,7 @@ Installation on Debian based distributions
 ==========================================
 
 The following steps should work (verified in VirtualBox only)
-on the distribution/architecture/release combinations as listed bellow.
+for the distribution/architecture/release combinations as listed bellow.
 
 ----------------------------------------------
 Debian         (AMD64, I386) 6.0.2.1 (squeeze)
@@ -65,9 +65,9 @@ $ wget http://bd.archive.ubuntu.com/ubuntu/pool/universe/libu/liburcu/liburcu-de
 $ sudo dpkg -i liburcu0_0.5.4-1_amd64.deb
 $ sudo dpkg -i liburcu-dev_0.5.4-1_amd64.deb
 
-# Go for the real thing
+# Get the source code
 $ git clone git://git.nic.cz/knot-dns.git
-$ cd knot
+$ cd knot-dns
 $ autoreconf -if
 $ ./configure
 $ make
@@ -189,21 +189,9 @@ Prepare working directory.
 
 $ mkdir -p /tmp/knot-minimal/samples; cp samples/example.com.zone /tmp/knot-minimal/samples/
 
-Third, lets load server. You can do this by running 'knotd' directly, or with
-'knotc' as well. Server is able to run in daemonized or interactive mode.
-Lets start our server in interactive mode (parameter '-i') to see if it runs.
-
-$ knotc -c myserver.conf -i start # start server in interactive mode
-
-Running as daemon
-=================
+Third, let's start the server. This can be done by running the 'knotd' command. Your distribution
+should have a 
+Lets start our server in foreground to see if it runs.
 
-Controller runs server in daemonized mode as default. Disadvantage is, that
-it closes stdout/stderr so you need to set up either syslog or logging to
-own files in the configuration. Controller parameter '-w' waits for the
-operation to finish. Let's test server functionality.
+$ knotd myserver.conf # start server
 
-$ knotc -c myserver.conf -w start # start server
-$ dig @$ADDR -p $PORT example.com # issue a query and see result
-$ ...
-$ knotc -c myserver.conf -w stop  # stop server