Dev tools init, config edits, misc edits

site/source/support/user-manual/configuration/lan-setup/index.rst

@@ -1,7 +1,7 @@
 .. _lan-setup:
 
 ============
-Local Access - **UPDATES REQUIRED**
+Local Access
 ============
 
 When you are on the same network as your Embassy (typically a home or small office), :ref:`Local Access<lan>` is much faster and will allow access to your data, even with no Internet connection.  Begin by setting up :ref:`Devices<lan-os>` before setting up a :ref:`Browser<lan-browser>`.

site/source/support/user-manual/configuration/lan-setup/lan-os/lan-android.rst

@@ -4,3 +4,6 @@
 Android
 =======
 
+If you are running Android 12, you can setup :ref:`Local Access<lan>`, please see :ref:`Android Limitations <lim-android>` for more details on devices that have this capability.
+
+

site/source/support/user-manual/configuration/lan-setup/lan-os/lan-linux.rst

@@ -1,7 +1,7 @@
 .. _lan-linux:
 
 =====
-Linux - ***UPDATE SCREENS***
+Linux
 =====
 
 Nothing specific needs to be configured for this environment, so you just need the certificate from your Embassy.

site/source/support/user-manual/configuration/limitations/lim-android.rst

@@ -6,8 +6,8 @@ Android Known Limitations
 
 Local Access
 ------------
-Android does not have native support for :ref:`mDNS<mdns>` and therefore cannot resolve ``.local`` addresses.  This issue has been long known by Google, and can be tracked `here <https://issuetracker.google.com/issues/140786115>`_ (Google account required to view).
+Older versions of Android (previous to version 12, and some custom ROMs, such as Graphene/Calyx) do not have native support for :ref:`mDNS<mdns>` and therefore cannot resolve ``.local`` addresses.  This issue has been long known by Google, and can be tracked `here <https://issuetracker.google.com/issues/140786115>`_ (Google account required to view).
 
 Workarounds
-...........
+===========
 An app developer can add mDNS support, and some projects, such as Chromium, have long `considered it <https://bugs.chromium.org/p/chromium/issues/detail?id=405925>`_, but the real solution is for support to occur at the OS level.

site/source/support/user-manual/configuration/limitations/lim-ios.rst

@@ -9,7 +9,7 @@ Tor
 It is not currently possible to run Tor natively (in the background) on iOS.  The best chance for this functionality coming to iOS is via the `iCepa Project <https://github.com/iCepa>`_.
 
 Workarounds
-...........
+===========
 The only way to use Tor on iOS is with apps that come with Tor built-in, such as :ref:`Zap Wallet <zap>`.
 
 Matrix
@@ -17,5 +17,5 @@ Matrix
 The lack of Tor support on iOS means that Element/Matrix cannot be run on an iPhone in conjunction with your Embassy Matrix server, as that currently requires a Tor connection.  This will be fixed when `Element <https://github.com/vector-im/element-ios>`_ builds Tor into their app.  An issue specifically in regard to this can be found `here <https://github.com/vector-im/element-ios/issues/1085>`_.
 
 Workarounds
-...........
+===========
 None currently known.

site/source/support/user-manual/configuration/sessions.rst

@@ -1,6 +1,12 @@
-.. _sessions:
+.. _active-sessions:
 
 ===============
 Active Sessions
 ===============
 
+Every time a login is made with Embassy, such as from a web browser on your laptop or mobile device, a :ref:`Session <sessions>` is created.  You can see these listed in the ``Embassy`` tab, under ``Active Sessions``.
+
+To end a session, simply click ``Kill`` to the right of your selection.
+
+    .. figure:: /_static/images/walkthrough/sessions0.svg
+        :width: 60%