diff --git a/handbook/troggle/trog2030.html b/handbook/troggle/trog2030.html
index 861318a78..d18be2cc3 100644
--- a/handbook/troggle/trog2030.html
+++ b/handbook/troggle/trog2030.html
@@ -163,7 +163,7 @@ A GIS db could make a lot of sense. Expo has GIS expertise and we have a lot of
 
 <h4>WebAssembly Front-Ends</h4>
 [January 2024]<br />
-<p>We have been waiting for more than a decade and a half for <a href="trogspeculate.html">the JavaScript Framework mess</a> to sort itself out. We want to see where we could sensibly move to a front-end+back-end architecture, instead of redrawing every screen of data on the server (see above "<a href="frontends">Things that could be a bit sticky 2 - front-end code</a>").
+<p>We have been waiting for more than a decade and a half for <a href="trogspeculate.html">the JavaScript Framework mess</a> to sort itself out. We want to see where we could sensibly move to a front-end+back-end architecture, instead of redrawing every screen of data on the server (see above "<a href="#frontends">Things that could be a bit sticky 2 - front-end code</a>").
   
   <p>In 2024 it now looks as if we may be able to stretch the current architecture into a <a href="trogspeculate.html#frontends">post-Javascript</a> era entirely because Webassembly <a href="https://thenewstack.io/webassembly-4-predictions-for-2024/">continues to develop rapidly</a>.