Update (Multiple) Docs (#802)

* Update 01-development.md

Add the RoboSats Twitter as a communication channel

* Update 00-quicks-start-guide.md

Fix the typo in the /docs/access URL (2 instances)

* Update 06-outreach.md

Add the RoboSats Twitter to the social media outreach page

* Update 03-premium.md

Remove '**' which is used for bold opening. Instead, a note in parenthesis to refer to the footnote is used in lieu of the double asterisk

* Update 07-wallets.md

Update Bluewallet and Muun descriptions per the previous PR comments.

---------

Co-authored-by: Reckless_Satoshi <90936742+Reckless-Satoshi@users.noreply.github.com>

docs/_pages/contribute/01-development.md

@@ -24,6 +24,8 @@ This contributing guide is based on the [Bisq contributing guide](https://github
 
 - **Matrix:** [RoboSats Development Group](https://matrix.to/#/#robosats:matrix.org). Main developer communication group chat where open and technical discussions about development takes place. Discussion about code changes happens in GitHub issues and pull requests (PRs).
 
+- **Twitter:** [RoboSats](https://twitter.com/RoboSats). Announces project updates, shares tips and tricks of using RoboSats, and discusses other privacy-related topics. Feel free to ask questions and to share your experience using RoboSats! The psuedonymous "Robotoshi" character, a privacy-loving and sometimes sassy robot, runs the RoboSats Twitter and tries his best to answer questions! Keep in mind that the aforementioned public Simplex group chat may be more effective in seeking technical help and users seeking dispute help will be directed to the SimpleX chat.
+
 ## Contributor Workflow
 
 All RoboSats contributors submit changes via pull requests. The workflow is as follows:

docs/_pages/contribute/06-outreach.md

@@ -19,7 +19,7 @@ The best we can do is reason with users of why they should value their privacy a
 
 Social media is a great opportunity for word-of-mouth advertising of RoboSats. If you had a great experience using RoboSats or have interesting insight to share about the project, please do say something! Shout it from the robo-heavens!
 
-For example, you could post on Nostr and tag the RoboSats Nostr account (npub1p2psats79rypr8lpnl9t5qdekfp700x660qsgw284xvq4s09lqrqqk3m82) so that it can be shared with others!
+For example, you could post on Nostr and tag the RoboSats Nostr account (npub1p2psats79rypr8lpnl9t5qdekfp700x660qsgw284xvq4s09lqrqqk3m82) so that it can be shared with others! Or, if you are on Twitter, create a tweet and tag the [RoboSats Twitter](https://twitter.com/RoboSats) account.
 
 Any help would be greatly appreciated in this sector! More order book liquidity attracts more users and thus more users get to take advantage of buying and selling bitcoin privately!
 

docs/_pages/docs/00-quick-start/00-quicks-start-guide.md

@@ -12,6 +12,6 @@ RoboSats is an easy way to privately exchange bitcoin for national currencies. I
 {: .notice--primary}
 
 1. Get a Lightning [Wallet](/docs/wallets/)
-2. Get [TOR browser](https://www.torproject.org/download/), or a supported [alternative](/docs/acces/)
+2. Get [TOR browser](https://www.torproject.org/download/), or a supported [alternative](/docs/access/)
 3. Access [RoboSats](/docs/access/)
 4. Check the [tutorials](/watch/en/) as needed!

docs/_pages/docs/03-understand/03-premium.md

@@ -22,7 +22,7 @@ Choose a competitive premium and incentivize fellow robots to provide liquidity
 
 Create an order, then input the "Premium over Market (%)" which can be a positive, negative, or zero percentage value. By default, the order premium is priced relative to the bitcoin-fiat market rate.
 
-Or, instead of the default setting, makers can select the explicit pricing method** by choosing an exact amount of Sats to exchange for the fiat amount given.
+Or, instead of the default setting, makers can select the explicit pricing method (*see footnote*) by choosing an exact amount of Sats to exchange for the fiat amount given.
 
 When selecting a premium, consider the payment method(s) and amount you have chosen; these, along with your desired premium, will compete with other live orders to incentivize and entice robot takers. Experiment with different premiums to find what works best for your specific orders.
 
@@ -48,7 +48,7 @@ For example, you (buyer) find that the highest premium across existing orders as
 
 But your competing order makers might notice their existing order no longer has the highest premium on the order book and thus cancel their order to create a new one for some premium higher than yours... Watch out for a premium war!
 
-***The explicit pricing method has been removed as an option for technical reasons, but could potentially come back in future updates. Currently, order pricing is only relative to the market rate.*
+*Footnote: the explicit pricing method has been removed as an option for technical reasons, but could potentially come back in future updates. Currently, order pricing is only relative to the market rate.*
 
 ## **Why Have Premiums?**
 

docs/_pages/docs/03-understand/07-wallets.md

@@ -62,7 +62,7 @@ Works well with RoboSats. Hodl invoices (Bonds) show as "Pending" in the transac
 Most development testing for RoboSats has been done using Blixt. This is one of the most complete Lightning wallets around. However, it does lead to misunderstanding when hold invoices are locked, as it shows a spinner with payment in transit. The user needs to check on the website for confirmation. Blixt allows for multiple pending HTLCs; this is necessary as a seller since you need to lock a taker/maker bond and then a trade escrow (2 pending concurrent HTLCs). It might eventually also display as paid/charged invoices that are still pending, especially if the user force closes Blixt and reopens it. Occasionally, it can display fidelity bonds as charged that have in fact been returned.
 
 ### Bluewallet (Mobile)
-It works well. But they are having issues in the custodial mode. Escrows that RoboSats returns are charged to users (so Bluewallet is keeping that balance?). Bonds that are slashed... are charged twice by Blue! More info once they reply to us. EDIT: Blue has confirmed they are working to soon solve these accounting bugs!
+It works well. Bluewallet has discontinued their custodial service. Previously, the custodial service would cause issues where escrows that RoboSats returns are charged to users and where slashed bonds are charged twice by Bluewallet! This was a known bug for long time in Bluewallet, so they shut down their LN custodial service (which ended up making RoboSats a smoother experience for users).
 
 ### Cash App (Mobile)
 Works well with RoboSats. Hodl invoices (Bonds) show as "Pending" in the transaction history. Payouts to the Cash App wallet function as intended. Custodial wallet by Block, Inc., formerly known as Square, Inc., which is led by Jack Dorsey.
@@ -77,7 +77,7 @@ Experience using Electrum is limited. It does not seem to support more than one
 Raw; it shows exactly what is happening and what it knows "IN_FLIGHT". It is not user friendly and therefore not recommended to interact with RoboSats by beginners. However, everything works just fine. If you are using LNCLI regularly, then you will find no issue using it with RoboSats.
 
 ### Muun (Mobile)
-Similar to Blixt or LND, Muun plays nicely with hold invoices. You can be a seller in RoboSats using Muun and the user experience will be great. However, in order to be a buyer when using Muun, you need to submit an on-chain address for the payout as a Lightning invoice won't work. Muun is _fee siphoning attacking_ any sender to Muun wallet. There is a mandatory hop through a private channel with a fee of +1500ppm. RoboSats will strictly not route a buyer payout for a net loss. Given that RoboSats trading fees are {{site.robosats.total_fee}}% and it needs to cover the routing fees, **RoboSats will never find a suitable route to a Muun wallet user**. At the moment, RoboSats will scan your invoice for routing hints that can potentially encode a _fee siphoning attack_. If this trick is found, then the invoice will be rejected: submit an on-chain address instead for an on-the-fly swap. Refer to [Understand > On-Chain Payouts](/docs/on-chain-payouts/) for more information about on-the-fly swaps.
+Similar to Blixt or LND, Muun plays nicely with hold invoices. You can be a seller in RoboSats using Muun and the user experience will be great. However, in order to be a buyer when using Muun, you need to submit an on-chain address for the payout as a Lightning invoice won't work. Muun is _fee siphoning attacking_ any sender to Muun wallet. There is a mandatory hop through a private channel with a fee of +1500ppm. RoboSats will strictly not route a buyer payout for a net loss. Given that RoboSats trading fees are {{site.robosats.total_fee}}% and it needs to cover the routing fees, **RoboSats will never find a suitable route to a Muun wallet user**. At the moment, RoboSats will scan your invoice for routing hints that can potentially encode a _fee siphoning attack_. If this trick is found, then the invoice will be rejected: submit an on-chain address instead for an on-the-fly swap. Refer to [Understand > On-Chain Payouts](/docs/on-chain-payouts/) for more information about on-the-fly swaps. Important to note that Muun has issues during times of high on chain fee spikes. Regardless, the workaround to receive to Muun is: either submit an on chain address or choose a higher routing budget after enabling the "Advanced Options" switch.
 
 ### OBW (Mobile)
 One of the simplest and one of the best. The hodl invoice shows as "on fly", it is not custodial and can create your own channels. Buy one from a liquidity provider or use Hosted Channels. It is maintained by the great Fiatjaf and it is a fork of the abandoned SBW.