doc: replace Internet-zone query with Internet-class query

doc/configuration.rst

@@ -580,7 +580,7 @@ several stages.
 * Answer, Authority, Additional records packet sections processing
 * After-query processing
 
-For example, processing an Internet-zone query needs to find an
+For example, processing an Internet-class query needs to find an
 answer. Then based on the previous state, it may also append an
 authority SOA or provide additional records. Each of these actions
 represents a 'processing step'. Now, if a query module is loaded for a
@@ -593,7 +593,7 @@ through :ref:`zone_module` option (in the form of ``module_name/module_id``)
 in the zone section or in the ``default`` template if it used for all queries.
 
 ``dnstap`` -- dnstap-enabled query logging
------------------------------------------
+------------------------------------------
 
 A module for query and response logging based on dnstap_ library.
 You can capture either all or zone-specific queries and responses; usually
@@ -612,7 +612,7 @@ a UNIX socket::
 .. _dnstap: http://dnstap.info/
 
 ``synth-record`` -- Automatic forward/reverse records
-----------------------------------------------------
+-----------------------------------------------------
 
 This module is able to synthesize either forward or reverse records for
 a given prefix and subnet.
@@ -704,7 +704,7 @@ Limitations
   possible to do online signing in the future.
 
 ``dnsproxy`` -- Tiny DNS proxy
------------------------------
+------------------------------
 
 The module catches all unsatisfied queries and forwards them to the
 indicated server for resolution, i.e. a tiny DNS proxy. There are several 
@@ -736,7 +736,7 @@ responded to locally. The rest of the requests will be forwarded to the
 specified server (``10.0.1.1`` in this case).
 
 ``rosedb`` -- Static resource records
-------------------------------------
+-------------------------------------
 
 The module provides a mean to override responses for certain queries before
 the record is searched in the available zones. The module comes with the 

doc/man_keymgr.rst

@@ -205,8 +205,7 @@ Examples
 3. Add a testing policy *lab* with rapid key rollovers. Apply the policy to an
    existing zone::
 
-   $ keymgr policy add lab rrsig-lifetime 300 rrsig-refresh 150 zsk-lifetime 600 \
-       delay 10
+   $ keymgr policy add lab rrsig-lifetime 300 rrsig-refresh 150 zsk-lifetime 600 delay 10
    $ keymgr zone set example.com policy lab
 
 4. Add an existing and already secured zone. Let the keys be managed by the

doc/man_knotc.rst

@@ -93,7 +93,7 @@ Examples
 --------
 
 Setup a key file for remote control
-..................................
+...................................
 
 1. Generate a key::
 

doc/running.rst

 .. highlight:: console
 .. _Running:
 
-*******
+*********
 Operation
-*******
+*********
 
 The Knot DNS server part ``knotd`` can run either in the foreground, or in the background
 using the ``-d`` option. When run in the foreground, it doesn't create a PID file.
@@ -51,7 +51,7 @@ It is recommended to perform these actions without server running.
 .. _Running a slave server:
 
 Slave mode
-======================
+==========
 
 Running the server as a slave is very straightforward as you usually
 bootstrap zones over AXFR and thus avoid any manual zone operations.
@@ -62,7 +62,7 @@ immediately but after the :ref:`zone_zonefile-sync` period elapses.
 .. _Running a master server:
 
 Master mode
-=======================
+===========
 
 If you just want to check the zone files before starting, you
 can use the ``knotc checkzone`` action::
@@ -83,7 +83,7 @@ or higher during transfers::
 .. _Controlling running daemon:
 
 Daemon controls
-==========================
+===============
 
 Knot DNS was designed to allow server reconfiguration on-the-fly
 without interrupting its operation. Thus it is possible to change

doc/troubleshooting.rst

@@ -11,7 +11,7 @@ the ``warning`` message severity may help you to identify some problems.
 ..  _Submitting a bugreport:
 
 Reporting bugs
-======================
+==============
 
 If you are unable to solve the problem by yourself, you can submit a
 bugreport to the Knot DNS team. *Do NOT use the public mailing list