Moar paragiraffes

draft-ietf-ohai-chunked-ohttp.md

@@ -327,6 +327,7 @@ in HTTP, which has the client withhold the body of a request until it receives a
 highlights the risks involved in the use of this chunked encoding to adapt an
 existing HTTP-based interaction to use Oblivious HTTP as such an adaptation
 might not achieve expected privacy outcomes.
+
 In order to prevent the Oblivious Gateway Resource from observing the round trip time
 to the client, client implementations can choose to not base the sending of request chunks based
 on received response chunks. These interactions can still benefit from chunked processing,