From f3ea5f3e2ce623d38fb08c8d1e234a442afb354e Mon Sep 17 00:00:00 2001
From: Adrian Hope-Bailie <adrian@hopebailie.com>
Date: Thu, 21 Apr 2016 04:11:03 +0200
Subject: [PATCH] Fix section indents

---
 proposals/architecture/index.html | 36 +++++++++++++++----------------
 1 file changed, 18 insertions(+), 18 deletions(-)

diff --git a/proposals/architecture/index.html b/proposals/architecture/index.html
index 971d1ae..dc3d425 100644
--- a/proposals/architecture/index.html
+++ b/proposals/architecture/index.html
@@ -517,25 +517,25 @@ <h4>Filtering for capable Payment Apps</h4>
                     conclusion on the correct algorithm to use in mathcing payment method identifiers.
                 </div>
             </section>
+        </section>
+        <section>
+            <h3>Extension Points</h3>
+            <p>The following extension points are defined for implemntation specific processing.</p>
+            <section>
+                <h4>Selection of Payment App</h4>
+                <p>Once the mediator has determined the set of <a>payment apps</a> that are able to process the
+                    <a>payment request</a> it must select one and pass the request to it.</p>
+                <p>The <dfn>steps for selecting a payment app</dfn> are implementation specific and MAY involve user
+                    interaction with the payer or may involve an algorithm that uses defaults and configuration data to
+                    make the selection.</p>
+                <p>The input to this process is an ordered list of <a>payment apps</a> and the output is a single
+                    <a>payment app</a>.</p>
+            </section>
             <section>
-                <h3>Extension Points</h3>
-                <p>The following extension points are defined for implemntation specific processing.</p>
-                <section>
-                    <h4>Selection of Payment App</h4>
-                    <p>Once the mediator has determined the set of <a>payment apps</a> that are able to process the
-                        <a>payment request</a> it must select one and pass the request to it.</p>
-                    <p>The <dfn>steps for selecting a payment app</dfn> are implementation specific and MAY involve user
-                        interaction with the payer or may involve an algorithm that uses defaults and configuration data to
-                        make the selection.</p>
-                    <p>The input to this process is an ordered list of <a>payment apps</a> and the output is a single
-                        <a>payment app</a>.</p>
-                </section>
-                <section>
-                    <h4>Passing the Payment Request to the Payment App</h4>
-                    <p>The payment mediator must have some mechanism of passing the <a>payment request</a> to the
-                        <a>payment app</a> that was selected following the <a>steps for selecting a payment app</a>.</p>
-                    <p>The <a>payment request</a> MUST not be altered by the <a>payment mediator</a>.</p>
-                </section>
+                <h4>Passing the Payment Request to the Payment App</h4>
+                <p>The payment mediator must have some mechanism of passing the <a>payment request</a> to the
+                    <a>payment app</a> that was selected following the <a>steps for selecting a payment app</a>.</p>
+                <p>The <a>payment request</a> MUST not be altered by the <a>payment mediator</a>.</p>
             </section>
         </section>
     </section>