Whitespace

pep-email/draft-pep-email.mkd

@@ -334,9 +334,7 @@ by default ensures the delivery of the sender's public key as an attachment
 A simple plaintext email looks like the following:
 
 {::include ../shared/fence-line.mkd}
-
 {::include examples/pef-0.mkd}
-
 {::include ../shared/fence-line.mkd}
 
 ### pEp Email Format 1.0 {#pef-1-0}
@@ -383,17 +381,13 @@ PEF-1.0 is also considered pEp's compatibility format towards non-pEp clients.
 A PEF-1.0 example looks as follows:
 
 {::include ../shared/fence-line.mkd}
-
 {::include examples/pef-1-0.mkd}
-
 {::include ../shared/fence-line.mkd}
 
 Decrypting the enclosed "msg.msc" part yields the following:
 
 {::include ../shared/fence-line.mkd}
-
 {::include examples/msg-part-decrypted-compat.mkd}
-
 {::include ../shared/fence-line.mkd}
 
 Note that the user-intended subject value is encrypted in the first 
@@ -414,9 +408,7 @@ This variant MUST NOT be produced anymore.
 An example of this deprecated variant of PEF-1.0 looks as follows:
 
 {::include ../shared/fence-line.mkd}
-
 {::include examples/pef-1-0_old.mkd}
-
 {::include ../shared/fence-line.mkd}
 
 There, decrypting the PGP encrypted text/plain element yields a text
@@ -811,9 +803,7 @@ messages to/from this identity. Past messages, however, MUST NOT be
 altered.
 
 {::include ../shared/fence-line.mkd}
-
 {::include ../shared/ascii-arts/basic-msg-flow.mkd}
-
 {::include ../shared/fence-line.mkd}
 
 \[\[ TODO: Add more of what is specific to email \]\]