Fix examples and formatting in native_protocol_v5.spec

Closes #171

doc/native_protocol_v5.spec

@@ -93,8 +93,8 @@ Table of Contents
   it is moving. The rest of that byte is the protocol version (5 for the protocol
   defined in this document). In other words, for this version of the protocol,
   version will be one of:
-    0x04    Request frame for this protocol version
-    0x84    Response frame for this protocol version
+    0x05    Request frame for this protocol version
+    0x85    Response frame for this protocol version
 
   Please note that while every message ships with the version, only one version
   of messages is accepted on a given connection. In other words, the first message
@@ -409,13 +409,13 @@ Table of Contents
   Executes a prepared query. The body of the message must be:
   <id><result_metadata_id><query_parameters>
   where
-  - <id> is the prepared query ID. It's the [short bytes] returned as a
-      response to a PREPARE message. As for <query_parameters>, it has the exact
-      same definition as in QUERY (see Section 4.1.4).
+    - <id> is the prepared query ID. It's the [short bytes] returned as a
+      response to a PREPARE message.
     - <result_metadata_id> is the ID of the resultset metadata that was sent
       along with response to PREPARE message. If a RESULT/Rows message reports
       changed resultset metadata with the Metadata_changed flag, the reported new
       resultset metadata must be used in subsequent executions.
+    - <query_parameters> has the exact same definition as in QUERY (see Section 4.1.4).
 
 
 4.1.7. BATCH