From c78e327625b0901019c30ed7575ef6a1c9d2bd7d Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Wed, 24 Jul 2019 13:25:05 +0200
Subject: fix floatings

---
 principles.html.j2 | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/principles.html.j2 b/principles.html.j2
index 52164b7e..854ebce4 100644
--- a/principles.html.j2
+++ b/principles.html.j2
@@ -89,7 +89,7 @@ h2 {
   <div class="row">
     <div class="col-lg-12">
       <h2>5. Only disclose the minimal amount of information necessary</h2>
-      <img style="width:20vw;float:left;padding:15px" src="../images/gdpr.medium.jpg" alt="Privacy by design, privacy by default, General Data Protection Regulation (GDPR) compliant"></a>
+      <img style="width:20vw;float:right;padding:15px" src="../images/gdpr.medium.jpg" alt="Privacy by design, privacy by default, General Data Protection Regulation (GDPR) compliant"></a>
       <p>
         The reason behind this goal is similar to (2). The privacy of buyers is given
         priority, but other parties such as merchants still benefit from it, for example,
@@ -100,7 +100,7 @@ h2 {
   <div class="row">
     <div class="col-lg-12">
       <h2>6. Be usable</h2>
-      <img style="width:20vw;float:right;padding:15px" src="../images/buy.medium.jpg" alt="Buy with one click"></a>
+      <img style="width:20vw;float:left;padding:15px" src="../images/buy.medium.jpg" alt="Buy with one click"></a>
       <p>
 Specifically it must be usable for non-expert customers. Usability also
 applies to the integration with merchants, and informs choices about the
@@ -112,7 +112,7 @@ operations into an isolated component with a simple API.
   <div class="row">
     <div class="col-lg-12">
       <h2>7. Be efficient</h2>
-      <img style="width:20vw;float:left;padding:15px" src="../images/efficient.png" alt="Energy efficiency"></a>
+      <img style="width:20vw;float:right;padding:15px" src="../images/efficient.png" alt="Energy efficiency"></a>
       <p>
          Approaches such as proof-of-work are ruled out by this requirement. Efficiency is necessary for GNU Taler to be used for micropayments.
       </p>
@@ -121,7 +121,7 @@ operations into an isolated component with a simple API.
   <div class="row">
     <div class="col-lg-12">
       <h2>8. Fault-tolerant design</a></h2>
-      <img style="width:20vw;float:right;padding:15px" src="../images/life-safer.medium.jpg" alt="Life Safers"></a>
+      <img style="width:20vw;float:left;padding:15px" src="../images/life-safer.medium.jpg" alt="Life Safers"></a>
       <p>
         Taler should tolerate failure of individual components and systems,
         including malicious operators compromising core secrets.
@@ -133,7 +133,7 @@ operations into an isolated component with a simple API.
   <div class="row">
     <div class="col-lg-12">
       <h2>9. Foster competition</h2>
-      <img style="width:20vw;float:left;padding:15px" src="../images/market.medium.jpg" alt="A competitive market"></a>
+      <img style="width:20vw;float:right;padding:15px" src="../images/market.medium.jpg" alt="A competitive market"></a>
       <p>
 It must be relatively easy for competitors to join the systems. While the
 barriers for this in traditional financial systems are rather high, the technical
-- 
cgit v1.2.3