diff --git a/index.html b/index.html
index 6141276..f4d9a07 100644
--- a/index.html
+++ b/index.html
@@ -511,7 +511,7 @@ In contrast, <b>(bottom-up) XR hypermedia</b> offers a more cost-efficient path.
       <b>A:</b> Basically that XR experiences should be cheap to archive and reproduce: the 'XR at rest' criteria dictates that immersive experiences should ideally exist as persistent, static files rather than being dependent on active, power-hungry server processes.<br>By decoupling the XR space from continuous compute requirements, these experiences remain accessible even when the original hosting infrastructure or company servers are powered down. <br>This approach leverages a 'cacheable' hypermedia architecture, allowing virtual environments to be served and cached much like standard web pages.<br> Ultimately, this ensures the long-term preservation and interoperability of the spatial web, preventing "digital decay" common in traditional live-service gaming models.
       <br>
 
-      <b>Q: What is the 'credible exit' criteria?<b><br>
+      <b>Q: What is the 'credible exit' criteria?</b><br>
       <B>A:</b> A credible exit ensures that users are never trapped within a single ecosystem, allowing their digital identity, assets, and progress to remain functional even if they switch platforms.<br> By prioritizing data portability and interoperable file standards, developers protect the user's long-term investment and prevent the loss of personal data if a service is discontinued.<br> Ultimately, providing a clear path to move data elsewhere fosters trust and is a fundamental requirement for building a truly open and decentralized XR landscape.<br>