From 0e40343b1b0a41551af52a83207070dd78d86328 Mon Sep 17 00:00:00 2001
From: Lucy Cifferello <12953208+elvece@users.noreply.github.com>
Date: Mon, 3 May 2021 17:09:40 -0600
Subject: [PATCH] fxing typos and removing duplicate page
---
source/conf.py | 2 +-
source/misc-guides/tor-os/windows.rst | 4 +-
source/support/FAQ/bitcoin-faq.rst | 10 +-
source/support/FAQ/general-faq.rst | 2 +-
source/support/FAQ/usage-faq.rst | 2 +-
.../general/lan-setup/os-config.rst | 185 ------------------
6 files changed, 10 insertions(+), 195 deletions(-)
delete mode 100644 source/user-manual/general/lan-setup/os-config.rst
diff --git a/source/conf.py b/source/conf.py
index e70bf65..7886234 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -59,7 +59,7 @@ html_theme_options = {
"use_edit_page_button": True,
"use_issues_button": True,
"use_repository_button": True,
- "extra_navbar": "Powered by Start9", # Will be displayed underneath the left navbar",
+ "extra_navbar": "Powered by Start9", # Will be displayed underneath the left navbar"
"show_navbar_depth": 1,
"use_download_button": False,
"use_edit_page_button": True,
diff --git a/source/misc-guides/tor-os/windows.rst b/source/misc-guides/tor-os/windows.rst
index b1139e2..a6a6fc0 100644
--- a/source/misc-guides/tor-os/windows.rst
+++ b/source/misc-guides/tor-os/windows.rst
@@ -45,8 +45,8 @@ Running Tor on Windows
sc delete tor
- 2. Uninstall the Tor Browser, following the steps `here `_.
- 3. Begin this guide again from the beginning.
+ 1. Uninstall the Tor Browser, following `these steps `_.
+ 2. Begin this guide again from the beginning.
#. When you run this, it should look something like this:
diff --git a/source/support/FAQ/bitcoin-faq.rst b/source/support/FAQ/bitcoin-faq.rst
index cc5c654..85bd7f8 100644
--- a/source/support/FAQ/bitcoin-faq.rst
+++ b/source/support/FAQ/bitcoin-faq.rst
@@ -26,7 +26,7 @@ It is fully validating and verifying consensus all the way from Genesis. Really,
What actions, specifically, are only possible with an archival, or ‘unpruned’ node?
-----------------------------------------------------------------------------------
-The more sophisticated the blockchain analysis being done is, the more index data is required, which will increase the system resources required. For example, if you wanted to run a block explorer, you would require not only a full archival node, but also a full transaction index. So, specifically, at this time, a full archival node is required for running an Electrum server, a block explorer, and for doing advanced chainalysis in general.
+The more sophisticated the blockchain analysis being done is, the more index data is required, which will increase the system resources required. For example, if you wanted to run a block explorer, you would require not only a full archival node, but also a full transaction index. So, specifically, at this time, a full archival node is required for running an Electrum server, a block explorer, and for doing advanced chain analysis in general.
Is it insecure to run a pruned node?
------------------------------------
@@ -47,7 +47,7 @@ The commitment fees are automatically negotiated every few blocks with your peer
What would happen if I shut down an Embassy that is running a Lightning node with open channels?
------------------------------------------------------------------------------------------------
It is REALLY IMPORTANT to understand that if Lightning services are shut off for long periods of time (days on end) it is possible for your peers to cheat you out of money. If you are not prepared to LOSE ALL THE MONEY IN YOUR CHANNELS, KEEP YOUR NODE RUNNING.
-That said, malicious actors on the network right now are probably sparse. However, you are still open to that risk if you do not keep your node online.
+That said, malicious actors on the network right now are probably sparse. However, you are still open to that risk if you do not keep your node online.
Is there a solution to this?
----------------------------
@@ -76,7 +76,7 @@ You do not use hardware signers directly with your node. Hardware signers interf
Node (Embassy) <— Wallet (Specter, Sparrow, Electrum) <— Hardware signer (Coldcard, Trezor)
-You would use your hardware with your wallet, then instruct that wallet to use Embassy as its node.
+You would use your hardware signee with your wallet, then instruct that wallet to use Embassy as its node.
- Nodes are for interacting with the Bitcoin network: enforcing consensus rules, validating and relaying blocks/transactions, and broadcasting transactions.
@@ -90,7 +90,7 @@ Please note: of the wallets listed (Specter/Sparrow/Electrum), only Specter is c
Which wallets can I use that sync with my Embassy Bitcoin node?
---------------------------------------------------------------
-There are many wallets that support linking to your own full node. You will need one that supports tor. Here are a few options that are compatible: FullyNoded, Samourai, Specter, Wasabi, Zap, and Zeus.
+There are many wallets that support linking to your own full node. You will need one that supports Tor. Here are a few options that are compatible: FullyNoded, Samourai, Specter, Wasabi, Zap, and Zeus.
Is there a guide for connecting Specter Wallet to my Embassy?
-------------------------------------------------------------
@@ -138,7 +138,7 @@ You may need to restart the LND Service.
I get the following error from LND: "Error ECONNREFUSED Fetching Info Failed! Unknown Error." What's wrong?
-----------------------------------------------------------------------------------------------------------
-LND is waiting for Bitcoin to completely sync, and then needs to catch up on block scanning itself. This may take several minutes, and in some cases might require a restart of the LND service. Do this if the process takes more than 5-10min.
+LND is waiting for Bitcoin to completely sync, and then needs to catch up on block scanning itself. This may take several minutes, and in some cases might require a restart of the LND service. Do this if the process takes more than 5-10 minutes.
What's the best way to move a small lightning balance?
------------------------------------------------------
diff --git a/source/support/FAQ/general-faq.rst b/source/support/FAQ/general-faq.rst
index 4f1d968..3ecce31 100644
--- a/source/support/FAQ/general-faq.rst
+++ b/source/support/FAQ/general-faq.rst
@@ -80,7 +80,7 @@ Yes! EmbassyOS is open sourced under the `Start9 Personal Use License Embassy --> Connect Over LAN
-
- .. figure:: /_static/images/embassy_lan_setup.png
- :width: 90%
- :alt: LAN setup menu item
-
- Select the "Connect over LAN" menu item
-
-#. Select the "Root Certificate Authority" sub menu. This will prompt a download to save the certificate file to your machine.
-
- .. figure:: /_static/images/secure_lan_setup_page.png
- :width: 90%
- :alt: LAN setup page
-
- Select the "Root Certificate Authority" sub menu
-
-#. Select the option to open your key with Keychain Access. If you choose to save file, double click on it once downloaded.
-
- .. figure:: /_static/images/secure_lan_setup_prompt.png
- :width: 90%
- :alt: LAN setup prompt
-
- Open with "Keychain Access" and select "OK"
-
-#. Enter your computer password when prompted. It will be imported into your computer’s keychain.
-
- .. figure:: /_static/images/ssl/macos/certificate_untrusted.png
- :width: 90%
- :alt: Keychain access import menu
-
- Keychain access import menu
-
-#. If the keychain console did not open, press "Command + spacebar" and type “Keychain Access”, and hit enter to open it.
-
-#. Navigate to the "System" tab and find the certificate entitled “Embassy Local Root CA”.
-
-#. Double click on this certificate. A second window will pop up.
-
-#. Open the “Trust” dropdown and select “Always Trust” from the dropdown next to “when using this certificate”.
-
- .. figure:: /_static/images/ssl/macos/always_trust.png
- :width: 90%
- :alt: Keychain submenu
-
- Select "Always trust" under SSL dropdown for Embassy Local CA
-
-#. Close this window and enter your password to apply the settings.
-
-#. The “Embassy Local Root CA” cert will now read “This certificate is marked as trusted for all users” in Keychain Access.
-
- .. figure:: /_static/images/ssl/macos/certificate_trusted.png
- :width: 90%
- :alt: Keychain menu trusted certificate
-
- Trusted Embassy Local CA certificate
-
-#. Open to your favorite browser to import this certificate and follow the steps for :ref:`supported browsers `.
-
-Windows
--------
-
-#. Install `Bonjour Print Services `_ on your Windows machine. This is necessary in order to visit .local addresses on Windows.
-#. If you are having issues running Bonjour after installing, you might have had Bonjour previously installed. To fix:
-
- #. Check out this video: https://www.youtube.com/watch?v=9ECCB3bqNDQ
- #. UNinstall Bonjour completely via ``system settings -> remove programs``
- #. Reinstall Bonjour Printer Driver package (download at https://support.apple.com/kb/DL999?locale=en_US)
- #. Restart Windows
- #. Note: Uninstalling Bonjour via the setup package seems to be not enough to solve the issue. Bonjour must be uninstalled via windows system settings.
-
-#. Visit your Embassy at its Tor Address.
-
-#. Navigate to --> Embassy --> Connect Over LAN
-
- .. figure:: /_static/images/embassy_lan_setup.png
- :width: 90%
- :alt: LAN setup menu item
-
- Select the "Connect over LAN" menu item
-
-#. Select the "Root Certificate Authority" sub menu. This will prompt a download to save the certificate file to your machine.
-
- .. figure:: /_static/images/secure_lan_setup_page.png
- :width: 90%
- :alt: LAN setup page
-
- Select the "Root Certificate Authority" sub menu download icon
-
-#. Select the option to save the *Embassy Local CA.crt* file.
-
- .. figure:: /_static/images/ssl/windows/windows_download_cert.png
- :width: 90%
- :alt: LAN setup prompt
-
- "Save file" when Opening Embassy Local CA.crt
-
-#. On your computer, right-click the “Start” menu and select “Run”.
-
-#. Type in “mmc” and click “OK”. When prompted on the “User Account Control” window, select “Yes” to allow this program to run.
-
- .. figure:: /_static/images/ssl/windows/1_windows_mmc.png
- :width: 90%
- :alt: Windows MMC
-
- Access the Windows Management Console
-
-#. When the Management Console opens, navigate to *File > Add/Remove Snap-in*.
-
- .. figure:: /_static/images/ssl/windows/2_windows_console_root.png
- :width: 90%
- :alt: Windows Console Root
-
- Add Snap-in from Console Root
-
-#. Select “Certificates” in the left side menu, then “Add”. This will open another window.
-
- .. figure:: /_static/images/ssl/windows/3_windows_add_certificates.png
- :width: 90%
- :alt: Add Certificates
-
- Add Certificates to selected snap-ins
-
-#. Select “Computer account” and click “Next. Leave defaulted options on the next screen and click “Finish”.
-
-#. When you return to the “Add or Remove Snap-ins” page, ensure “Certificates (Local Computer)” exists under “Console Root” in the “Selected snap-ins” section, then click “OK”.
-
- .. figure:: /_static/images/ssl/windows/4_windows_selected_snapin.png
- :width: 90%
- :alt: Snap-in Selected
-
- Certificates (Local Computer) is selected as snap-in
-
-#. In the left hand menu of the Management Console, navigate to Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.
-
- .. figure:: /_static/images/ssl/windows/5_windows_trusted_certificate_menu.png
- :width: 90%
- :alt: Certificates in Management Console
-
- Access Certificates in Management Console
-
-#. Right click on “Certificates”, then navigate to *All Tasks > Import*.
-
- .. figure:: /_static/images/ssl/windows/6_windows_import_cert.png
- :width: 90%
- :alt: Import certificate
-
- Select "Import" from Certificates sub-menu
-
-#. Click “Next” on the first page of the Certificate Import Wizard, then browse to the location where you saved the downloaded certificate and click “Open”.
-
- .. figure:: /_static/images/ssl/windows/7_windows_import_cert_wizard.png
- :width: 90%
- :alt: Import cert wizard
-
- Add downloaded certificate int he Certificate Import Wizard
-
-#. On the “Certificate Store” window, ensure that it says “Trusted Root Certificate Authorities” and click “Next”.
-
-#. Select “OK” when the import is successful.
-
-#. Verify the Embassy Local Root CA certificate is in the “Certificates” folder.
-
- .. figure:: /_static/images/ssl/windows/8_windows_successful_cert_install.png
- :width: 90%
- :alt: Successful cert install
-
- Embassy Local Root CA imported into Certificate folder
-
-#. You can save the settings to the console if desired or cancel.
-
-#. Open to your favorite browser to import this certificate and follow the steps for :ref:`supported browsers `.
-
-
-Linux
------
-
-Nothing specific needs to be configured for this environment. Follow the guides below to import the certificate into your desired browser.