Basic formatting checked
diff --git a/ndns-packet-format.md b/ndns-packet-format.md
index 6a6cfa4..2292b0f 100644
--- a/ndns-packet-format.md
+++ b/ndns-packet-format.md
@@ -3,7 +3,11 @@
Query
-----
- Requests to the server are made in the format of a standard NDN interest packet. The question is replaced with a standard request for content. See :ref `Interest section <Interest>` for details.
+Requests to the server are made in the format of a standard NDN interest packet.
+The question is replaced with a standard request for content.
+
+See :ref `Interest section <Interest>` for details.
+
Answer
------
@@ -25,10 +29,13 @@
.. _MetaInfo
+
MetaInfo
~~~~~~~~
-MetaInfo specified here represents portions that are defaultly specified in any NDN packet, which NDNS specific additions.
+MetaInfo specified here represents portions that are defaultly specified in any
+NDN packet, which NDNS specific additions.
+
See `NDN Packet Specification - Meta-Info <http://named-data.net/doc/ndn-tlv/data.html#metainfo>`_
MetaInfo ::= META-INFO-TYPE TLV-LENGTH
@@ -37,6 +44,7 @@
NDNS-Type
AnswerCount
+
ContentType
+++++++++++
@@ -45,10 +53,12 @@
ContentType ::= CONTENT-TYPE-TYPE TLV-LENGTH
nonNegativeInteger
-For an NDNS packet the ContentType should always be BLOB (=0), specificity is accomplished by NDNS-Type.
+For an NDNS packet the ContentType should always be BLOB (=0), specificity is
+accomplished by NDNS-Type.
See :ref: `NDNS-Type` for details
+
FreshnessPeriod
+++++++++++++++
@@ -57,10 +67,12 @@
FreshnessPeriod ::= FRESHNESS-PERIOD-TLV TLV-LENGTH
nonNegativeInteger
-The optional freshness period specifies how long after the arrive of the data the recieving node should wait before marking it stale.
+The optional freshness period specifies how long after the arrive of the data
+the recieving node should wait before marking it stale.
See `NDN Packet Specification - Freshness Period <http://named-data.net/doc/ndn-tlv/data.html#freshnessperiod>`_
+
.. _NDNS-Type:
NDNS-Type
@@ -71,12 +83,25 @@
NDNS-Type ::= NDNS-TYPE-TLV TLV-LENGTH
nonNegativeIntegear
-There are 4 distinct types of NDNS Responses:
-
- *NDNS Data*- a traditional response which answers which contains the data corresponding to the NDNS Query.
- *NDNS NACK* - indicates that the responding zone has no content matching the query
- *NDNS AUTH* - indicates that the zone has content, but a more specific question is need to determine the correct content to server.
-
+There are 3 distinct types of NDNS Responses:
++-----------+------------------------------------------------------------------+
+| Type | Description |
++===========+==================================================================+
+| NDNS Data | indicates an answer was found, and that contains the requested |
+| | content |
++-----------+----------------------------------------------------------------+
+| NDNS NACK | indicates that the responding zone has no content matching the |
+| | query. |
++-----------+------------------------------------------------------------------+
+| NDNS AUTH | indicates that the zone has content, but a more specific |
+| | question is need to determine the correct content to server. |
++-----------+------------------------------------------------------------------+
+
+.. note:
+
+Both ``NDNS NACK`` and ``NDNS AUTH`` are types of negative respones which
+indicate an issue with the request.
+
.. _AnswerCount:
AnswerCount
@@ -107,3 +132,4 @@
See `NDN Signature Specification - Signature <http://named-data.net/doc/ndn-tlv/signature.html>`_
+