diff --git a/static/releases.html b/static/releases.html
index 6fd6c257..aaecd207 100644
--- a/static/releases.html
+++ b/static/releases.html
@@ -729,7 +729,7 @@
Settings: fix issue preventing users from re-enabling system apps they previously disabled which can no longer be disabled
fix upstream Android bug causing out-of-band updates to system components using original-package to be rolled back after reboot if they're still using the old package name, which will allow us to ship Vanadium updates out-of-band without the browser package updates being rolled back for users with an older install where it's still org.chromium.chrome
instead of app.vanadium.browser
SELinux policy: drop base OS apk_data_file restrictions to avoid blocking out-of-band updates to APK-based system components (this was a minor security feature that's being replaced with our recent and ongoing improvements to package manager and verified boot security to close major weaknesses in the standard Android verified boot security model)
- disable package parser cache since it provides a verified boot bypass for system component updates for regular boots while not saving more than around a second of boot time
+ disable package parser cache since it provides a verified boot bypass for system component updates for regular boots while saving less than a second of boot time
perform additional boot-time checks on system package updates in order to extend verified boot to out-of-band system package updates including enforcing having valid signed fs-verity metadata for continuous verification (Android does not even provide working boot-time verification for out-of-band APK updates for non-APEX components)
reimplement requiring fs-verity when installing system package updates in a better way
remove unnecessary warning for failed virtual A/B sideloaded updates since it's atomic just like A/B updates