Build updates, cont.

- Fix cross-reference issues
 - Properly comment out unused sections (coinjoin, payment processing)
 - Link correction
 - Subheading corrections

_includes/devdoc/dash-core/rpcs/intro.md

@@ -88,7 +88,7 @@ format:
 | → <br>`result`       | *any*           | Required<br>(exactly 1)     | The RPC output<!--noref--> whose type varies by call.  Has value `null` if an error occurred.
 | → <br>`error`        | null/object     | Required<br>(exactly 1)     | An object describing the error if one occurred, otherwise `null`.
 | → → <br>`code`        | number (int)    | Required<br>(exactly 1)     | The error code returned by the RPC function call. See [rpcprotocol.h][] for a full list of error codes and their meanings.
-| → → <br>`message`     | string          | Required<br>(exactly 1)     | A text description of the error.  May be an empty string ("").
+| → → <br>`message<!--noref-->`     | string          | Required<br>(exactly 1)     | A text description of the error.  May be an empty string ("").
 | → <br>`id`           | string          | Required<br>(exactly 1)     | The value of `id` provided with the request. Has value `null` if the `id` field was omitted in the request.
 {:.ntpd}
 

_includes/devdoc/example_p2p_networking.md

@@ -240,6 +240,7 @@ MATCH FAILURE: Index 0x6 not set in 1010110111110000
 {% endautocrossref %}
 
 ### Bloom Filter Script
+<!-- no subhead-links here -->
 
 <!-- Shell script to run previous examples -->
 Complete Python script demonstrating the

_includes/devdoc/example_transactions.md

@@ -129,6 +129,7 @@ second) and clear the shell variable.
 {% endautocrossref %}
 
 ##### Simple Spending Script
+{% include helpers/subhead-links.md %}
 
 <!-- Shell script to run previous example -->
 Shell script to run the previous example:

_includes/devdoc/guide_contracts.md

@@ -207,8 +207,9 @@ all under an Apache license.
 -->
 {% endautocrossref %}
 
-<!-- Obsolesced by PrivateSend
+{% comment %}<!-- Obsolesced by PrivateSend
 ### CoinJoin
+
 {% include helpers/subhead-links.md %}
 
 {% autocrossref %}
@@ -290,4 +291,7 @@ saving each one of them a tiny amount of duffs.
 CoinJoin is [CoinMux](http://coinmux.com/), available under the Apache
 license.
 -->
+
 {% endautocrossref %}
+
+{% endcomment %}

_includes/devdoc/guide_dash_features.md

@@ -28,7 +28,6 @@ economy.
 
 
 ### InstantSend
-
 {% include helpers/subhead-links.md %}
 
 {% autocrossref %}
@@ -62,7 +61,6 @@ There are a number of limitations on InstantSend transactions:
 
 
 ### PrivateSend
-
 {% include helpers/subhead-links.md %}
 
 {% autocrossref %}
@@ -90,7 +88,6 @@ reference this [Official Documentation PrivateSend page](https://dashpay.atlassi
 
 
 ### Masternode Payment
-
 {% include helpers/subhead-links.md %}
 
 {% autocrossref %}
@@ -115,7 +112,6 @@ treated as misbehaving and have its ban score increased.
 {% endautocrossref %}
 
 ### Masternode Sync
-
 {% include helpers/subhead-links.md %}
 
 {% autocrossref %}
@@ -129,6 +125,7 @@ several conditions that initiate a start/restart the sync process:
 * Issuing a `mnsync reset` RPC command
 
 #### Initial Masternode<!--noref--> Sync
+{% include helpers/subhead-links.md %}
 
 This diagram shows the order in which P2P messages are sent to perform
 masternode synchronization initially after startup.
@@ -176,6 +173,7 @@ are used in both `ssc` messages and the `mnsync` RPC.
 
 
 #### Ongoing Masternode<!--noref--> Sync
+{% include helpers/subhead-links.md %}
 
 Once a masternode completes an initial full sync, continuing synchronization is
 maintained by the exchange of P2P messages with other nodes. This diagram shows
@@ -219,6 +217,7 @@ network. Unsynchronized peers may send `govsync` messages to request governance
 sync.
 
 #### Masternode<!--noref--> Sync Schedule
+{% include helpers/subhead-links.md %}
 
 The following tables detail the timing of various functions used to keep the
 masternodes in sync with each other. This information is derived from
@@ -242,12 +241,12 @@ The following actions only run when the masternode sync is past `MASTERNODE_SYNC
 {% endautocrossref %}
 
 ### Governance
-
 {% include helpers/subhead-links.md %}
 
 {% autocrossref %}
 
 #### Synchronization
+{% include helpers/subhead-links.md %}
 
 Dash Core synchronizes the governance system via the Masternode network as the
 last stage of the Masternode sync process (following the sync of sporks, the
@@ -309,6 +308,7 @@ Once the syncing node receives the counts and inventories, it may request any
 |                          | ←              | `govobjvote` message      | (If requested) Governance object vote
 
 #### Sentinel<!--noref-->
+{% include helpers/subhead-links.md %}
 
 [Sentinel](https://github.com/dashpay/sentinel<!--noref-->/) is a Python application that connects to a masternode's local dashd
 instance to run as an autonomous agent for persisting, processing, and automating
@@ -323,11 +323,15 @@ governance sync, ping, governance object pruning, and superblock management.
 The governance object data is stored in a SQLite database.
 
 ##### Sentinel<!--noref--> Sync
+{% include helpers/subhead-links.md %}
+
 Sentinel issues a `gobject list` RPC command and updates its database with the
 results returned from dashd. When objects are removed from the network, they are
 purged from the Sentinel database.
 
 ##### Sentinel<!--noref--> Ping
+{% include helpers/subhead-links.md %}
+
 In Dash Core 12.2, use of the `watchdog` governance object type was replaced
 by integrating sentinel information into the masternode ping (`mnp` message)
 via [Pull Request #1491](https://github.com/dashpay/dash/pull/1491).
@@ -335,13 +339,17 @@ Sentinel calls the `sentinelping` RPC which updates the masternode info to
 prevent it from entering a `MASTERNODE_WATCHDOG_EXPIRED` state.
 
 ##### Sentinel<!--noref--> Prune
+{% include helpers/subhead-links.md %}
+
 Sentinel 1.1.0 introduced proposal pruning which automatically votes to delete
 expired proposals following approximately half of a superblock cycle. This delay
 period ensures that proposals are not deleted prematurely. Prior to this,
 proposals remained in memory unless a sufficient number of masternodes manually
 voted to delete them.
 
-##### Sentinel<!--noref--> Superblock
+##### Sentinel<!--noref--> Superblock<!--noref-->
+{% include helpers/subhead-links.md %}
+
 Sentinel manages superblock creation, voting, and submission to dashd for
 network propagation.
 
@@ -349,7 +357,6 @@ network propagation.
 
 
 ### Quorum Selection
-
 {% include helpers/subhead-links.md %}
 
 {% autocrossref %}

_includes/devdoc/guide_intro.md

@@ -14,8 +14,8 @@ Core, either from [source][core git] or from a [pre-compiled executable][core ex
 Questions about Dash development are best asked in one of the
 [Dash development communities][dev communities].
 Errors or suggestions related to
-documentation on {Dash.org} can be [submitted as an issue][docs issue]
-or posted to the [bitcoin-documentation mailing list][].
+documentation on [dash-docs.github.io](https://dash-docs.github.io) can be
+[submitted as an issue][docs issue].
 
 In the following documentation, some strings have been shortened or wrapped: "[...]"
 indicates extra data was removed, and lines ending in a single backslash "\\"

_includes/devdoc/guide_p2p_network.md

@@ -118,7 +118,7 @@ connection to a specific node by IP address.  See the `-help` text for
 details.
 
 **Resources:** [Dash Seeder][], the program run by several of the
-seeds used by Dash Core. The Dash Core [DNS SeedPolicy][]. The hardcoded list
+seeds used by Dash Core. The Dash Core [DNS Seed Policy][]. The hardcoded list
  of IP addresses used by Dash Core is generated using the [makeseeds script][].
 
 {% endautocrossref %}

_includes/devdoc/guide_transactions.md

@@ -661,8 +661,7 @@ added in sequence until all of the available space is filled.
 As of Dash Core 0.12.2.x, a [minimum fee][/en/glossary/minimum-relay-fee]{:#term-minimum-fee}{:.term}(1,000 duffs following [DIP1][] activation) is required to
 broadcast a non-priority transaction across the network. Any transaction paying
 only the minimum fee should be prepared to wait a long time before there's
-enough spare space in a block to include it. Please see the [verifying payment section][section verifying payment]
-for why this could be important.
+enough spare space in a block to include it.
 
 Since each transaction spends Unspent Transaction Outputs (UTXOs) and
 because a UTXO can only be spent once, the full value of the included
@@ -727,8 +726,8 @@ described below, with more general attacks hypothesized).
 So, for both privacy and security, we encourage you to build your
 applications to avoid public key reuse and, when possible, to discourage
 users from reusing addresses. If your application needs to provide a
-fixed URI to which payments should be sent, please see the
-[`dash:` URI section][bitcoin URI subsection] below.
+fixed URI to which payments should be sent, please use `dash:` URIs as defined
+by [BIP21](https://github.com/QuantumExplorer/bips/blob/master/bip-0021.mediawiki#general-format).
 
 {% endautocrossref %}
 

_includes/devdoc/guide_wallets.md

@@ -244,8 +244,7 @@ design these minimalist wallets:
 
 Neither method adds a significant amount of overhead, especially if a
 database is used anyway to associate each incoming payment with a
-separate public key for payment tracking. See the [Payment
-Processing][devguide payment processing] section for details.
+separate public key for payment tracking.
 
 {% endautocrossref %}
 

_includes/devdoc/ref_intro.md

@@ -16,7 +16,8 @@ Core, either from [source][core git] or from a [pre-compiled executable][core ex
 Questions about Dash development are best asked in one of the
 [Dash development communities][dev communities].
 Errors or suggestions related to
-documentation on dash-docs.github.io can be [submitted as an issue][docs issue].
+documentation on [dash-docs.github.io](https://dash-docs.github.io) can be
+[submitted as an issue][docs issue].
 
 In the following documentation, some strings have been shortened or wrapped: "[...]"
 indicates extra data was removed, and lines ending in a single backslash "\\"

_includes/devdoc/ref_p2p_networking.md

@@ -167,7 +167,7 @@ The currently-available type identifiers are:
 | 15               | [`MSG_MASTERNODE_PING`][msg_masternode_ping]{:#term-msg_masternode_ping}{:.term}                                     | The hash is a Masternode Ping.
 | 16               | [`MSG_DSTX`][msg_dstx]{:#term-msg_dstx}{:.term}                              | The hash is Private Send (Dark Send) Broadcast TX.
 | 17               | [`MSG_GOVERNANCE_OBJECT`][msg_governance_object]{:#term-msg_governance_object}{:.term}                                     | The hash is a Governance Object.
-| 18               | [`MSG_GOVERNANCE_OBJECT_VOTE`][msg_governance_object_vote]{:#term-msg_governance_object}{:.term}                                     | The hash is a Governance Object Vote.
+| 18               | [`MSG_GOVERNANCE_OBJECT_VOTE`][msg_governance_object_vote]{:#term-msg_governance_object_vote}{:.term}                                     | The hash is a Governance Object Vote.
 | 19               | [`MSG_MASTERNODE_VERIFY`][msg_masternode_verify]{:#term-msg_masternode_verify}{:.term}                                     | The hash is a Masternode Verify.
 
 Type identifier zero and type identifiers greater than nineteen are reserved