docs: fix syntax highlighting of code blocks

And various other cleanups

Change-Id: I240badc5358c09f006c2a22d4706ce373f2dd188
diff --git a/docs/local-prefix-discovery.rst b/docs/local-prefix-discovery.rst
index 868d2bb..083134b 100644
--- a/docs/local-prefix-discovery.rst
+++ b/docs/local-prefix-discovery.rst
@@ -3,30 +3,25 @@
 Local hub prefix discovery
 ==========================
 
-Some applications need to discover the prefix(es) under which they can publish data
-/ which Interests the local hub will be able to forward down to the application.
-In order to discover that, applications need to send an Interest for
-``/localhop/nfd/rib/routable-prefixes`` prefix. Response data to the
-Interest contains a list of prefixes and should be encoded as follows:
+Some applications need to discover the prefix(es) under which they can publish
+data / which Interests the local hub will be able to forward down to the
+application. In order to discover that, an application can send an Interest for
+``/localhop/nfd/rib/routable-prefixes``. The data in response to this Interest
+will contain a list of prefixes and should be encoded as follows:
 
-::
+.. code-block:: abnf
 
-    Response ::= DATA-TYPE TLV-LENGTH
-                   Name (= /localhop/nfd/rib/routable-prefixes/[version]/[segment])
-                   MetaInfo (= ResponseMetaInfo)
-                   Content (= ResponseContent)
-                   Signature
+    Response = DATA-TYPE TLV-LENGTH
+                 Name     ; /localhop/nfd/rib/routable-prefixes/[version]/[segment]
+                 MetaInfo ; ContentType == BLOB, FreshnessPeriod == 5000
+                 ResponseContent
+                 DataSignature
 
-    ResponseMetaInfo ::= META-INFO-TYPE TLV-LENGTH
-                           ContentType (= BLOB)
-                           FreshnessPeriod (= 5000)
+    ResponseContent = 1*Name
 
-    ResponseContent ::= Name+
-
-.. note::
-    ResponseContent should contain at least one ``Name``, which should be routable
-    towards the face from which the request has been received.  The requester may
-    process the list of returned names and pick whichever it wants to use.
+``ResponseContent`` should contain at least one ``Name``, which should be routable
+towards the face from which the request was received.  The requester may process
+the list of returned names and pick whichever it wants to use.
 
 For now, the ``/localhop/nfd/rib/routable-prefixes`` data is served by
 :ref:`ndn-autoconfig-server`.