From 1f3b812a664333f1329548cdaa158faf98762ff8 Mon Sep 17 00:00:00 2001
From: Rob Winch <rwinch@vmware.com>
Date: Thu, 26 Sep 2013 08:58:39 -0500
Subject: [PATCH] SEC-2282: Polish CSRF Documentation

---
 docs/manual/src/docbook/csrf.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/manual/src/docbook/csrf.xml b/docs/manual/src/docbook/csrf.xml
index 0945b0312e..a2efae2fc4 100644
--- a/docs/manual/src/docbook/csrf.xml
+++ b/docs/manual/src/docbook/csrf.xml
@@ -75,7 +75,7 @@ amount=100.00&routingNumber=1234&account=9876&_csrf=<secure-random>
                 are CSRF exploits that can impact JSON requests. For example, a malicious user can create a
                 <link xlink:href="http://blog.opensecurityresearch.com/2012/02/json-csrf-with-parameter-padding.html" >CSRF with JSON using the following form</link>:</para>
             <programlisting language="xml"><![CDATA[<form action="https://bank.example.com/transfer" method="post" enctype="text/plain">
-            <input name='{"amount":100,"routingNumber":"evilsRoutingNumber","account":"evilsAccountNumber", "ignore_me":"' value='test"}' type='hidden'>
+  <input name='{"amount":100,"routingNumber":"evilsRoutingNumber","account":"evilsAccountNumber", "ignore_me":"' value='test"}' type='hidden'>
   <input type="submit"
       value="Win Money!"/>
 </form>]]></programlisting>