Merge pull request bisq-network#114 from m52go/fix-stale-links

Fix stale links in dao spec and index page

Author: Steve Jain

dao/specification.adoc

@@ -26,11 +26,11 @@ We use that possibility to invalidate BSQ intentionally for "burning" tokens to
 
 ==== Validation process
 
-The validation of the BSQ tokens requires the full blockchain data from the block containing the genesis transaction up to the latest block. To avoid users from needing to download too much data we use a lite-node mode where all BSQ transactions are delivered by the dedicated block provider nodes at startup (we use the seed nodes for that but that can/should change later). The verification is done on the lite node itself (each Bisq application). Every time a new block is created by the miners, the block provider nodes (they operate as full nodes) broadcast the BSQ transactions contained in that block to the P2P network. The data is broadcasted by multiple block provider nodes, and if the data is not consistent the lite node would re-validate from the last snapshot (see below). Such inconsistency is expected in the case of https://en.bitcoin.it/wiki/Chain_Reorganization[chain reorganisations] (reorgs), but also delivers more resilience in case a block provider node is not providing reliable data.
+The validation of the BSQ tokens requires the full blockchain data from the block containing the genesis transaction up to the latest block. To avoid users from needing to download too much data we use a lite-node mode where all BSQ transactions are delivered by the dedicated block provider nodes at startup (we use the seed nodes for that but that can/should change later). The verification is done on the lite node itself (each Bisq application). Every time a new block is created by the miners, the block provider nodes (they operate as full nodes) broadcast the BSQ transactions contained in that block to the P2P network. The data is broadcasted by multiple block provider nodes, and if the data is not consistent the lite node would re-validate from the last snapshot (see below). Such inconsistency is expected in the case of https://en.bitcoin.it/wiki/Chain_Reorganization[chain reorganisations^] (reorgs), but also delivers more resilience in case a block provider node is not providing reliable data.
 
 Furthermore we use snapshots of past blocks which will get distributed with the software release to reduce bandwidth requirements. Thus we do not require to load all BSQ transactions since the genesis transaction but only since the latest snapshot. At certain block-heights (every 100 blocks) the nodes are locally persisting snapshots. Those persisted snapshots will be used after a restart to only request the missing BSQ transactions from the blocks since the latest snapshot up to the actual chain head.
 
-Users can also run themselves a full node either directly from the Bisq application or as a self hosted headless full node. To run a full node requires a Bitcoin Core (bitcoind) full node with RPC enabled. More details on https://github.com/bisq-network/exchange/blob/master/doc/rpc.md[how to run a full node] can be found in the documentation folder of the source code repository.
+Users can also run themselves a full node either directly from the Bisq application or as a self hosted headless full node. To run a full node requires a Bitcoin Core (bitcoind) full node with RPC enabled. Here are more details on <<../btcnode#, running a full node>>.
 
 The block provider nodes are operated by the developers and the management for the privilege to run a default block provider node will be a part of the DAO (see phase 3). As said before the seed nodes will carry that functionality because those are the first nodes the user connects to so it improves user experience when the data gets delivered fast at start up.
 

index.adoc

@@ -55,8 +55,8 @@ image::quick-link-4.png[alt=Make a Compensation Request,width=200,role=quick-lin
 
 === Features
 
- * Payment Methods — _Explore https://bisq.network/faq/#paymentmethods[20+] supported fiat currency payment methods, from Alipay to Zelle_
- * Altcoins — _Explore https://bisq.network/faq/#altcoins[100+] supported cryptocurrencies, tokens and assets_
+ * Payment Methods — _Explore https://bisq.network/faq/#Which_payment_methods_are_supported[20+] supported fiat currency payment methods, from Alipay to Zelle_
+ * Altcoins — _Explore https://bisq.network/markets/[100+] supported cryptocurrencies, tokens and assets_
 
 === Ecosystem
 
@@ -69,7 +69,7 @@ image::quick-link-4.png[alt=Make a Compensation Request,width=200,role=quick-lin
 === Incubating Efforts
 
  * Bisq HTTP API — _Automate trading and interact programmatically with your Bisq node_
- * <<bisq-mobile#, Bisq Mobile Notifications>> — _Get alerts for new offers, trades in process, and more right on your phone._
+ * <<bisq-mobile#, Bisq Mobile Notifications>> — _Get alerts for new offers, trades in process, and more right on your phone_
 
 == Contributor Docs