diff --git a/doc/installation.texi b/doc/installation.texi
index 9dc0ba9e561fcf9d57be133980f7e33afe1d8c9c..0d88f060b1aa7d6628db742208f50ffc3dd5cf97 100644
--- a/doc/installation.texi
+++ b/doc/installation.texi
@@ -11,7 +11,7 @@
 @node Required build environment
 @section Required build environment
 
-GCC at least 4.1 is strictly required for atomic built ins, but 4.2 or newer is recommended.
+GCC at least 4.1 is strictly required for atomic built-ins, but 4.2 or newer is recommended.
 Another requirement is @code{_GNU_SOURCE} support, otherwise it adapts to the compiler available features.
 Clang should work, but it is not officially supported.
 
@@ -77,7 +77,7 @@ Minimum supported version of Userspace RCU library is 0.5.4,
 but we recommend using latest available version.
 It is crucial especially on non-Linux systems, as we got some compatibility
 patches accepted to later releases of Userspace RCU.
-OpenBSD,NetBSD and OS X platforms are supported from version 0.7.0.
+OpenBSD, NetBSD and OS X platforms are supported from version 0.7.0.
 
 @node Installation from the sources
 @section Installation from the sources
@@ -131,6 +131,8 @@ $ ./configure --enable-debug=server,packet --enable-debuglevel=brief
 $ ./configure --enable-debug=server,packet --enable-debuglevel=verbose
 @end example
 
+For more detailed information, see @ref{Debug messages}.
+
 In most simple case you can just run configure without any options.
 
 @example
@@ -255,9 +257,9 @@ $ sudo apt-get install knot
 @end example
 
 @noindent
-Running this sequence of command will ensure that you will
-install the Knot DNS on your system and keep it up-to-date
-in the future, when new version are released.
+Running this sequence of commands will ensure that you will
+install Knot DNS on your system and keep it up-to-date
+in the future, when new versions are released.
 
 @page
 @node Installing Knot DNS RPMs on Fedora
diff --git a/doc/introduction.texi b/doc/introduction.texi
index 10337f83a10a4ddb61b7aef951f5e00d1f5b8c77..42170015c2a9c137c7f563da61b917886cf28587 100644
--- a/doc/introduction.texi
+++ b/doc/introduction.texi
@@ -16,7 +16,7 @@ Domain Name System.
 Knot DNS is a high-performance open source DNS server. It 
 implements only authoritative domain name service. Knot DNS 
 is best suited for use on TLD domains but can reliably serve
-any other zone as well.
+any other zones as well.
 
 Knot DNS benefits from its multi-threaded and mostly lock-free
 implementation which allows it to scale well on SMP systems and
diff --git a/doc/knot.texi b/doc/knot.texi
index 95482134c94c1b267eb61db55cc48fa4c7468793..3c652dd2d17602dfe617e07bc255da8f4788af6f 100644
--- a/doc/knot.texi
+++ b/doc/knot.texi
@@ -39,10 +39,10 @@ along with this program.  If not, see <http://www.gnu.org/licenses/>.
 @titlepage
 @title Knot DNS Reference Manual
 @subtitle for version @value{VERSION}, @value{UPDATED}
+@author Jan Kadlec (@email{jan.kadlec@@nic.cz})
+@author Lubos Slovak (@email{lubos.slovak@@nic.cz})
 @author Ondrej Sury (@email{ondrej@@sury.org})
 @author Marek Vavrusa (@email{marek.vavrusa@@nic.cz})
-@author Lubos Slovak (@email{lubos.slovak@@nic.cz})
-@author Jan Kadlec (@email{jan.kadlec@@nic.cz})
 @page
 @vskip 0pt plus 1filll
 @insertcopying
diff --git a/doc/reference.texi b/doc/reference.texi
index 33966c2d1018bad3202cca2060d4a83632c4ab89..50e1a3898d7f8fa1520d98d36f22df6e1ee888d7 100644
--- a/doc/reference.texi
+++ b/doc/reference.texi
@@ -546,7 +546,7 @@ See @ref{Controlling running daemon} for more information. Possible values are @
 @subsubsection disable-any
 @vindex disable-any
 
-If you enable @code{disable-any}, all ANY queries sent over UDP will be answered with an empty response and with the TC bit set.
+If you enable @code{disable-any}, all authoritative ANY queries sent over UDP will be answered with an empty response and with the TC bit set.
 Use to minimize the risk of DNS replay attack. Disabled by default.
 
 @node notify-timeout
diff --git a/doc/troubleshooting.texi b/doc/troubleshooting.texi
index bba2e24a069fde6580d08e2ca66b0459d281af87..18fee7a625ac28ed5865a017683f53de662173b1 100644
--- a/doc/troubleshooting.texi
+++ b/doc/troubleshooting.texi
@@ -28,7 +28,7 @@ The bugreport should contain at least:
 @item basic hardware information,
 @item description of the bug,
 @item log output of all messages (category @code{any}) with severity Info 
-and higher (severity @code{info}),
+and higher (severities @code{info, notice, warning, error}, or @code{any} if debug messages are not turned on (see below)),
 @item steps to reproduce the bug (if known),
 @item backtrace (if the bug caused a crash; see next section).
 @end itemize
@@ -80,7 +80,7 @@ Two steps are required in order to log debug messages. First you need to
 allow the debug messages in the server. Then the logging must be configured
 to log debug messages (@pxref{log}). It is recommended to log these 
 messages to a file. Firstly, the debug output may be rather large and 
-secondly it is easier to use the data for debugging.
+secondly, it is easier to use the data for debugging.
 
 @node Enabling debug messages in server
 @subsection Enabling debug messages in server