Mark up tsig tables/algorithms/lengths

diff --git a/docs/tsig.rst b/docs/tsig.rst
index 6335e96c2c099877dafe1527468a77e2b7694a44..415bd8144b070dcb673880c6181c9be4ebc586a6 100644 (file)
--- a/docs/tsig.rst
+++ b/docs/tsig.rst
@@ -8,15 +8,15 @@ transfer of a domain if the request is signed with an authorized name.
 
 In PowerDNS, TSIG shared secrets are stored by the various backends. In
 case of the :doc:`backends/generic-sql`, they
-can be found in the 'tsigkeys' table. The name can be chosen freely, but
-the algorithm name will typically be 'hmac-md5'. Other supported
-algorithms are 'hmac-sha1', 'hmac-shaX' where X is 224, 256, 384 or 512.
+can be found in the ``tsigkeys`` table. The name can be chosen freely, but
+the algorithm name will typically be ``hmac-md5``. Other supported
+algorithms are ``hmac-sha1``, ``hmac-shaX`` where ``X`` is ``224``, ``256``, ``384`` or ``512``.
 The content is a Base64-encoded secret.
 
 .. note::
   Most backends require DNSSEC support to be enabled to support TSIG.
   For the Generic SQL Backend, make sure to use the DNSSEC-enabled schema
-  and to turn on the relevant '-dnssec' flag (for example,
+  and to turn on the relevant ``-dnssec`` flag (for example,
   ``gmysql-dnssec``)!
 
 Provisioning outbound AXFR access