diff --git a/draft/conflicts.html b/draft/conflicts.html
index b7491ba..e3b7031 100644
--- a/draft/conflicts.html
+++ b/draft/conflicts.html
@@ -144,8 +144,8 @@ <h3 id="working">Working with Conflicts</h3>
 &gt; curl -X PUT $HOST/db/foo -d '{"count":1}'
 {"ok":true,"id":"foo","rev":"1-74620ecf527d29daaab9c2b465fbce66"}
 
-&gt; curl -X POST $HOST/_replicate -d '{"source":"db","target":"http://127.0.0.1:5984/db-replica"}'
-{"ok":true,...,"docs_written":1,"doc_write_failures":0}]} -H "Content-Type: application/json"
+&gt; curl -X POST $HOST/_replicate -d '{"source":"db","target":"http://127.0.0.1:5984/db-replica"}' -H "Content-Type: application/json"
+{"ok":true,...,"docs_written":1,"doc_write_failures":0}]}
 </pre>
 
 <p>We skip a bit of the output of the replication session (see <a href="replication.html">Chapter 16, Replication</a> for details). If you see <code>"docs_written":1</code> and <code>"doc_write_failures":0</code>, our document made it over to <code>db-replica</code>. We now update the document to <code>{"count":2}</code> in <code>db-replica</code>. Note that we now need to include the correct <code>_rev</code> property.
@@ -161,8 +161,8 @@ <h3 id="working">Working with Conflicts</h3>
 &gt; curl -X PUT $HOST/db/foo -d '{"count":3,"_rev":"1-74620ecf527d29daaab9c2b465fbce66"}'
 {"ok":true,"id":"foo","rev":"2-7c971bb974251ae8541b8fe045964219"}
 
-&gt; curl -X POST $HOST/_replicate -d '{"source":"db","target":"http://127.0.0.1:5984/db-replica"}'
-{"ok":true,..."docs_written":1,"doc_write_failures":0}]} -H "Content-Type: application/json"
+&gt; curl -X POST $HOST/_replicate -d '{"source":"db","target":"http://127.0.0.1:5984/db-replica"}' -H "Content-Type: application/json"
+{"ok":true,..."docs_written":1,"doc_write_failures":0}]}
 </pre>
 
 <p>To see that we have a conflict, we create a simple view in <code>db-replica</code>. The map function looks like this: