reformat Vanadium default connections

static/faq.html

@@ -1016,23 +1016,27 @@ <h3><a href="#default-connections">What kind of connections do the OS and bundle
                             <p>DNS resolution for other connections involving connections to the
                             network / user provided DNS resolvers</p>
                         </li>
+                        <li>
+                            <p>Vanadium, our browser and WebView implementation, uses
+                            <code>update.vanadium.app</code> to check for updates to components
+                            providing revoked certificates and other data. It downloads the
+                            components from <code>dl.vanadium.app</code>.</p>
+                        </li>
                     </ul>
 
+                    <p>Other Vanadium browser connections are initiated by the user such as the
+                    search engine (defaults to DuckDuckGo), websites and retrieving favicons for
+                    your bookmarks and the frequent sites shown on the home page. We enable
+                    connection and cache partitioning to keep connections separate between
+                    different sites. There are a few parts of state partitioning still being
+                    implemented including cookie partitioning which is currently in the testing
+                    phase but causes too many compatibility issues to fully deploy it by default
+                    without any exceptions like Brave's heuristics to disable it for cross-site
+                    login flows, etc.</p>
+
                     <p>Unlike Chrome/Chromium, Vanadium WebView does not make connections beyond
                     those initiated by the app using it so there are no default connections from
                     apps using the WebView.</p>
-
-                    <p>Vanadium browser uses <code>update.vanadium.app</code> to check for updates
-                    to components providing revoked certificates and other data. It downloads the
-                    components from <code>dl.vanadium.app</code>. Other connections are initiated
-                    by the user such as the search engine (defaults to DuckDuckGo), websites and
-                    retrieving favicons for your bookmarks and the frequent sites shown on the
-                    home page. We enable connection and cache partitioning to keep connections
-                    separate between different sites. There are a few parts of state partitioning
-                    still being implemented including cookie partitioning which is currently in
-                    the testing phase but causes too many compatibility issues to fully deploy it
-                    by default without any exceptions like Brave's heuristics to disable it for
-                    cross-site login flows, etc.</p>
                 </article>
 
                 <article id="other-connections">