Edit FAQ for 0.3 relevance

site/source/support/faq/faq-troubleshooting.rst

@@ -6,7 +6,7 @@ Setup and Troubleshooting FAQ
 
 What do I do first?
 -------------------
-Simply plug the device into power and internet, most easily by using an empty ethernet port on your home internet router.  That's it!  After this, get the :ref:`Setup App <initial-setup>`, and follow the instructions.
+Please check out the :ref:`Initial Setup <initial-setup>` page, and follow the instructions.
 
 How do I know if my Embassy is running?
 ---------------------------------------
@@ -14,7 +14,7 @@ After plugging into power and your router, you will hear 2 distinct sounds: firs
 
 My Embassy is really hot!  Is this normal?
 ------------------------------------------
-Yes, the Embassy's case is actually doing 'double duty' as a heat sync.  This means that the metal of the case is actually touching the chips on the circuit board and drawing their heat out and away.  This is known as "passive cooling," as no fan (and therefore no additional energy) is required to cool the system.
+Yes, the Embassy's case is actually doing 'double duty' as a heat sync.  This means that the metal of the case is actually touching the chips on the circuit board and drawing their heat out and away.  This is known as "passive cooling," as no fan (and therefore no noise) is required to cool the system.
 
 What if I can't connect to my Embassy?
 --------------------------------------
@@ -30,7 +30,7 @@ This is most likely a transient networking issue that will correct itself in a f
 
 1. On Android/Orbot, the most common solution is to restart your Android device.
 
-2. Access your Embassy over :ref:`LAN <ssl-setup>` and restart it from the "Embassy" menu.
+2. Access your Embassy over :ref:`LAN <lan-setup>`, and restart it from the "Embassy" menu.
 
 3. Restart your router.
 
@@ -40,26 +40,18 @@ Nothing special is required, however, it is best practice to use good passwords,
 
 What if I have an unique network issue, for example, with a firewall?
 ---------------------------------------------------------------------
-The Embassy is designed to work as simply as possible, for as many as possible, while providing the ability to self-host in a private manner.  If you have an agressive or custom firewall, or other custom network settings, there is a good chance that addtional configuration may be necessary.  We will continue to learn about custom networking issues, update our docs with resources, and help in the community :ref:`channels <contact>` to the best of our ability.
+The Embassy is designed to work as simply as possible, for as many as possible, while providing the ability to self-host in a private manner.  If you have an agressive or custom firewall, or other custom network settings, there is a good chance that addtional configuration may be necessary.  We will continue to learn about custom networking issues, update our docs with resources, and help in the :ref:`Community Channels <contact>` to the best of our ability.
 
-Can I use the Embassy from behind a VPN, for example, if my router has a built-in VPN?
---------------------------------------------------------------------------------------
+Can I use my Embassy from behind a VPN, for example, if my router has a built-in VPN?
+-------------------------------------------------------------------------------------
 While this is possible, it adds complexity, which may lead to problems.  You will need to understand the setup of your router/VPN and how it supports (or doesn't support) tor connections.
 
 If you are having trouble with this, you might consider letting the Embassy out "in the clear," since everything is broadcast exclusively across the Tor network, offering a high level of privacy.
 
 Why am I having trouble using my Embassy via the Brave browser?
 ---------------------------------------------------------------
-Unfortunately, Brave does not treat .onion addresses in a 'secure context.'  This is a known issue in Brave that is being tracked `here <https://github.com/brave/brave-browser/issues/13834>`_.
+Unfortunately, Brave does not treat .onion addresses in a 'secure context.'  This is a well-known issue in Brave that is being tracked `here <https://github.com/brave/brave-browser/issues/13834>`_.
 
-I'm getting this error: The shell command "apt-get update" returned a failure exit code: 100.  What do I do?
-------------------------------------------------------------------------------------------------------------
-This has been fixed in newer updates.  Please first make sure to update to the latest EOS version (2.16 or higher).  If this does not work, please :ref:`contact us <contact>`.
-
-Is it true that iOS has some limited functionality in regard to the Embassy?
-----------------------------------------------------------------------------
-The short answer is yes, but not much.  Unfortunately, Apple does not allow any ability for Tor to run in the background (everything on the Embassy runs over Tor).  Most of your Embassy services can be run with Tor-native apps, inside Consulate, or with another Tor browser, with the exception of RTL, Spark, and Matrix.  Zap and Zeus wallets can be used in place of RTL/Spark, and we hope a Tor-native Element client will be available soon to allow for the use of Matrix.
-
-I'm having trouble using Firefox for Tor addresses on Lineage, what can I do?
------------------------------------------------------------------------------
-Unfortunately, there seems to be a bug in Lineage that makes using Firefox over Tor currently unusable.  Currently, this feature works fine on Calyx and Graphene.
+Is it true that my device has some limited functionality in regard to Embassy?
+------------------------------------------------------------------------------
+The short answer is maybe, but there are workarounds for most limitations.  Please see the :ref:`Limitations<limitations>` page for details on your device.