From cc507ff76580b785d41e29416a46d1620954846f Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@gmail.com>
Date: Tue, 5 May 2026 15:25:49 +0100
Subject: [PATCH] figure layout - online edit of
 handbook/computing/myphone.html

---
 handbook/computing/myphone.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/handbook/computing/myphone.html b/handbook/computing/myphone.html
index 05fbacb8a..54d58c8e0 100644
--- a/handbook/computing/myphone.html
+++ b/handbook/computing/myphone.html
@@ -29,7 +29,7 @@ For the latest updates on why "battery saver" kills accurate location for the mo
 
 <h3>The reason why</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>
+  <a href='/handbook/computing/gps-location.png'><img  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.