Fixed formatting of references.

No \code{}.

refs #1877 @5m

doc/configuration.texi

@@ -55,14 +55,14 @@ Now let's go step by step through this minimal configuration file:
 @item
 In @code{system} statement we have configured @code{storage}
 directory where Knot DNS will store compiled zone files, 
-PID file and for slave zone also their journal files. (See @code{@ref{system}} and @code{@ref{storage}})
+PID file and for slave zone also their journal files. (See @ref{system} and @ref{storage})
 
 @item
 The @code{interfaces} statement defines interfaces where Knot
 DNS will listen for incoming connections. We have defined two
 interfaces: one IPv4 called @kbd{my_interface} explicitly listening
 on port 53 and second IPv6 called @kbd{second_int} also listening on
-port 53, which is the default port for the DNS. See @code{@ref{interfaces}}.
+port 53, which is the default port for the DNS. See @ref{interfaces}.
 
 @item
 The @code{log} statement defines the log facilities for Knot DNS.
@@ -71,18 +71,18 @@ In this example we told Knot DNS to send its log messages with the severities
 If you omit this sections, all severities will printed to
 either @code{stdout} or @code{stderr}, and the severities
 from the @code{warning} and more serious to syslog. You can find all
-possible combinations in the @code{@ref{log}}.
+possible combinations in the @ref{log}.
 
 @item
 The @code{zones} statement is probably the most important one,
 because it defines the zones that Knot DNS will serve.  In its most simple
 form you can define a zone by its name and zone file.
 You can turn on more detailed semantic
-checks of zone file in this statement. Refer to @code{@ref{zones List of zone semantic checks}} to see
+checks of zone file in this statement. Refer to @ref{zones List of zone semantic checks} to see
 which checks are enabled by default and which are optional. If Knot is
 being run as a master server, experimental feature @code{ixfr-from-differences}
 can be enabled to create IXFR changesets from changes made to the master zone file.
-See @ref{Controlling running daemon} for more information. For more information about @code{zones} statement see @code{@ref{zones}}.
+See @ref{Controlling running daemon} for more information. For more information about @code{zones} statement see @ref{zones}.
 @end enumerate
 
 @page
@@ -95,7 +95,7 @@ thus allowing both incoming XFR from that remote and using it as the
 zone master. Note that you need to explicitly allow incoming NOTIFY, otherwise
 the daemon would reject them.
 Also, you can specify paths, relative to the storage directory.
-See @code{@ref{zones}} and @code{@ref{storage}}.
+See @ref{zones} and @ref{storage}.
 If the zone file doesn't exist and @code{xfr-in} is set, it will be bootstrapped over AXFR.
 
 @example
@@ -116,7 +116,7 @@ and assign it to a remote.
 Supported algorithms for TSIG key are:@*
 @code{hmac-md5, hmac-sha1, hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512}
 @*
-Key secret is written in a base64 encoded format. See @code{@ref{keys}}.
+Key secret is written in a base64 encoded format. See @ref{keys}.
 
 @example
 keys @{

doc/running.texi

@@ -20,7 +20,7 @@ $ knotc -a -c knot.conf start|reload|restart
 
 The tool @code{knotc} is designed as a front-end for user, making it easier
 to do everything from zone compilation to controlling the server daemon.
-To communicate with the binary, it reads the PID from the @emph{PID file} specified in the configuration @code{pidfile} and sends POSIX signals to it (@code{@pxref{pidfile}}).
+To communicate with the binary, it reads the PID from the @emph{PID file} specified in the configuration @code{pidfile} and sends POSIX signals to it (@pxref{pidfile}).
 If you want to control the daemon directly, use @code{SIGINT} to quit the process or @code{SIGHUP} to reload configuration. Signal @code{SIGUSR2} is currently used to refresh slave zones.
 
 @example
@@ -72,8 +72,8 @@ Parameters:
 @end example
 
 Also, the server needs to create several files in order to run properly.
-All files are placed in the directory described by @code{storage} (@code{@pxref{storage}}).
-PID file can be placed elsewhere using the @code{pidfile} statement (@code{@pxref{pidfile}}).
+All files are placed in the directory described by @code{storage} (@pxref{storage}).
+PID file can be placed elsewhere using the @code{pidfile} statement (@pxref{pidfile}).
 Slave zones with relative path specified will be placed in the @code{storage} as well.
 @itemize @bullet
 @item
@@ -103,7 +103,7 @@ However when IXFR transfer finishes, it stores the differences in a journal file
 and doesn't update the zone file nor compiled zone immediately,
 but there is a timer that checks periodically for new differences and
 updates both zone file and the compiled zone. You can configure this timer
-with the @code{zonefile-sync} statement in @ref{zones}.
+with the @code{zonefile-sync} statement in @code{zones} (@pxref{zones}).
 
 There are two ways to start the server - directly or with the @code{knotc} controller tool.
 First, let us start it directly. If you do not pass any configuration, it will try to