diff --git a/handbook/computing/myphone.html b/handbook/computing/myphone.html
index 0c1f2a084..05fbacb8a 100644
--- a/handbook/computing/myphone.html
+++ b/handbook/computing/myphone.html
@@ -28,14 +28,15 @@ For the latest updates on why "battery saver" kills accurate location for the mo
   
 
 <h3>The reason why</h3>
-<p>Phones assume that you are walking along streets, or running along tracks or cycling. They are <b>very, very bad</b> at making the right guesses on the Totes Gebirge plateau.
-  
-<h3>Location, location, location</h3>
-
 <figure  class=onright width=500>
   <a href='/handbook/computing/gps-location.png'><img class="onright" alt="GPS position controls" width=40% src='/handbook/computing/gps-location.png' /></a>
  <br> <figcaption style="text-align: center"> Android GPS setting </figcaption>
 </figure>
+<p>Phones assume that you are walking along streets, or running along tracks or cycling. They are <b>very, very bad</b> at making the right guesses on the Totes Gebirge plateau.
+  
+<h3>Location, location, location</h3>
+
+
 
 <p>Do <em>not</em> select the "high accuracy" location setting on your phone. Mostly this will snap your position to the nearest cafe or bierstube: by default it will use the nearest WiFi it can find and assume that you are there, and will ignore the perfectly reasonable GPS position it has recorded directly.
   <p>This is all explained by Google <a href="https://support.google.com/maps/answer/2839911?hl=en&co=GENIE.Platform=Android">here</a>.