From 3c809ce07559cc6d904c54ef4cb52e71cd3dc99e Mon Sep 17 00:00:00 2001
From: Daniel Micay <danielmicay@gmail.com>
Date: Mon, 17 Oct 2022 03:14:50 -0400
Subject: [PATCH] be more specific about 32-bit WebView compat issue

---
 static/releases.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/static/releases.html b/static/releases.html
index 84b552d2..fb8be619 100644
--- a/static/releases.html
+++ b/static/releases.html
@@ -650,7 +650,7 @@
                     <p>Changes since the 2022101500 release:</p>
 
                     <ul>
-                        <li>Vanadium: add back 32-bit WebView support since there are non-Play-Store app repositories distributing 32-bit-only APKs to save storage space since they lack of split APK support and are incorrectly assuming 64-bit devices support 32-bit apps (Pixel 7 and Pixel 7 Pro have finally dropped 32-bit app support so we'll be able to build and ship 64-bit-only Vanadium on those devices, but we don't want to break existing setups on previous generation devices)</li>
+                        <li>Vanadium: add back 32-bit WebView support primarily due to a certain F-Droid repository distributing 32-bit-only APKs to save storage space since they lack of split APK support and are incorrectly assuming 64-bit devices support 32-bit apps (Pixel 7 and Pixel 7 Pro have finally dropped 32-bit app support so we'll be able to build and ship 64-bit-only Vanadium on those devices, but we don't want to break existing setups on previous generation devices)</li>
                         <li>don't auto-revoke Sensors/Network permissions when 'freezing' apps with device managers</li>
                         <li>GmsCompatConfig: disable WearableDataListenerService</li>
                         <li>raise minimum supported fastboot version for the factory images flashing scripts to 33.0.3</li>