From 4253bc02787d4f126d7ea04a0e49c07d04f93f8c Mon Sep 17 00:00:00 2001
From: Nobuaki Sukegawa <nsukeg@gmail.com>
Date: Mon, 21 Sep 2015 12:25:10 +0900
Subject: [PATCH] THRIFT-3334 Markdown notation of protocol spec is malformed

---
 doc/specs/thrift-protocol-spec.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/specs/thrift-protocol-spec.md b/doc/specs/thrift-protocol-spec.md
index 48ee8273dee..950e1633572 100644
--- a/doc/specs/thrift-protocol-spec.md
+++ b/doc/specs/thrift-protocol-spec.md
@@ -1,4 +1,5 @@
 Thrift Protocol Structure
+====================================================================
 
 Last Modified: 2007-Jun-29
 
@@ -31,12 +32,13 @@ structure. There are some "dumb" terminals like STRING and INT
 that take the place of an actual encoding specification.
 
 They key point to notice is that ALL messages are just one wrapped
-<struct>. Depending upon the message type, the <struct> can be
+`<struct>`. Depending upon the message type, the `<struct>` can be
 interpreted as the argument list to a function, the return value
 of a function, or an exception.
 
 --------------------------------------------------------------------
 
+```
        <message> ::= <message-begin> <struct> <message-end>
 
  <message-begin> ::= <method-name> <message-type> <message-seqid>
@@ -94,3 +96,4 @@ of a function, or an exception.
  <set-elem-type> ::= <field-type>
 
       <set-size> ::= I32
+```