Run markdownlint --fix on spec.

1 files changed, 6 insertions, 0 deletions

diff --git a/spec/pt-spec/pluggable-transport-to-parent-process-communication.md b/spec/pt-spec/pluggable-transport-to-parent-process-communication.md
index b7f8175..985bcb5 100644
--- a/spec/pt-spec/pluggable-transport-to-parent-process-communication.md
+++ b/spec/pt-spec/pluggable-transport-to-parent-process-communication.md
@@ -1,4 +1,5 @@
 <a id="pt-spec.txt-3.3"></a>
+
 ## Pluggable Transport To Parent Process Communication
 
 All Pluggable Transport Proxies communicate to the parent process
@@ -19,6 +20,7 @@ The parent process MUST ignore lines received from PT proxies with
 unknown keywords.
 
 <a id="pt-spec.txt-3.3.1"></a>
+
 ### Common Messages
 
 When a PT proxy first starts up, it must determine which version
@@ -93,6 +95,7 @@ Example:
 ENV-ERROR No TOR_PT_AUTH_COOKIE_FILE when TOR_PT_EXTENDED_SERVER_PORT set
 
 <a id="pt-spec.txt-3.3.2"></a>
+
 ### Pluggable Transport Client Messages
 
 After negotiating the Pluggable Transport Specification version,
@@ -174,6 +177,7 @@ Notes:
 ```
 
 <a id="pt-spec.txt-3.3.3"></a>
+
 ### Pluggable Transport Server Messages
 
 PT server reverse proxies iterate over the requested transports
@@ -240,6 +244,7 @@ Upon sending the "SMETHODS DONE" message, the PT proxy
 initialization is complete.
 
 <a id="pt-spec.txt-3.3.4"></a>
+
 ### Pluggable Transport Log Message
 
 This message is for a client or server PT to be able to signal back to the
@@ -270,6 +275,7 @@ Example:
 `LOG SEVERITY=debug MESSAGE="Connected to bridge A"`
 
 <a id="pt-spec.txt-3.3.5"></a>
+
 ### Pluggable Transport Status Message
 
 This message is for a client or server PT to be able to signal back to the