Fix additional cross-reference issues

This commit is contained in:
thephez 2017-12-20 16:37:30 -05:00
parent 3495dbbdf5
commit 295be42529
6 changed files with 46 additions and 46 deletions

View file

@ -898,7 +898,7 @@ Result (truncated):
###### GObject Vote-alias
The `gobject vote-alias` RPC votes on a governance object by masternode alias (using masternode.conf setup).
The `gobject vote-alias` RPC votes on a governance object by masternode alias (using masternode<!--noref-->.conf setup).
*Parameter #1---governance hash*
@ -1074,7 +1074,7 @@ dash-cli -testnet gobject vote-conf \
###### GObject Vote-many
The `gobject vote-many` RPC votes on a governance object by all masternodes (using masternode.conf setup).
The `gobject vote-many` RPC votes on a governance object by all masternodes (using masternode<!--noref-->.conf setup).
*Parameter #1---governance hash*

View file

@ -15,9 +15,9 @@ http://opensource.org/licenses/MIT.
The `masternode` RPC {{summary_masternode}}
###### Masternode Count
###### Masternode<!--noref--> Count
The `masternode count` RPC prints the number of all known masternodes.
The `masternode<!--noref--> count` RPC prints the number of all known masternodes.
*Parameter #1---mode*
@ -50,7 +50,7 @@ Result:
120
{% endhighlight %}
Get summarized count of all masternode nodes
Get summarized count of all masternodes
{% highlight bash %}
dash-cli -testnet masternode count all
@ -62,9 +62,9 @@ Total: 129 (PS Compatible: 97 / Enabled: 97 / Qualify: 90)
{% endhighlight %}
###### Masternode Current
###### Masternode<!--noref--> Current
The `masternode current` RPC prints info on current masternode winner to be paid the next block (calculated locally).
The `masternode<!--noref--> current` RPC prints info on current masternode winner to be paid the next block (calculated locally).
*Parameters: none*
@ -133,11 +133,11 @@ Result:
{% endhighlight %}
###### Masternode Debug
###### Masternode<!--noref--> Debug
The `masternode debug` RPC prints masternode status.
The `masternode<!--noref--> debug` RPC prints masternode status.
{{WARNING}} `masternode debug` will be removed in Dash Core 0.12.3.
{{WARNING}} `masternode<!--noref--> debug` was removed in Dash Core 0.12.2.2.
*Parameters: none*
@ -163,9 +163,9 @@ Masternode successfully started
{% endhighlight %}
###### Masternode Genkey
###### Masternode<!--noref--> Genkey
The `masternode genkey` RPC generates a new masternodeprivkey.
The `masternode<!--noref--> genkey` RPC generates a new masternodeprivkey.
*Parameters: none*
@ -191,9 +191,9 @@ Result:
{% endhighlight %}
###### Masternode Outputs<!--noref-->
###### Masternode<!--noref--> Outputs<!--noref-->
The `masternode outputs` RPC prints masternode compatible outputs.
The `masternode<!--noref--> outputs` RPC prints masternode compatible outputs.
*Parameters: none*
@ -226,12 +226,12 @@ Result:
{% endhighlight %}
###### Masternode Start
###### Masternode<!--noref--> Start
The `masternode start` RPC starts a local hot masternode configure in dash.conf.
The `masternode<!--noref--> start` RPC starts a local hot masternode configure in dash.conf.
{{WARNING}} `masternode start` will be removed in Dash Core 0.12.3. Local
masternode support is being removed for security reasons.
{{WARNING}} `masternode<!--noref--> start` was removed in Dash Core 0.12.2.2. Local
masternode support was removed for security reasons.
*Parameters: none*
@ -257,9 +257,9 @@ Masternode successfully started
{% endhighlight %}
###### Masternode Start-alias
###### Masternode<!--noref--> Start-alias
The `masternode start-alias` starts a single remote masternode by assigned alias configured in masternode.conf.
The `masternode<!--noref--> start-alias` starts a single remote masternode by assigned alias configured in masternode<!--noref-->.conf.
*Parameter #1---masternode alias*
@ -295,10 +295,10 @@ Result:
}
{% endhighlight %}
###### Masternode Start-mode
###### Masternode<!--noref--> Start-mode
The `masternode start-<mode>` RPC starts remote masternodes configured in
masternode.conf. Valid modes are: `all`, `missing`, or `disabled`.
The `masternode<!--noref--> start-<mode>` RPC starts remote masternodes configured in
masternode<!--noref-->.conf. Valid modes are: `all`, `missing`, or `disabled`.
*Parameters: none*
@ -340,7 +340,7 @@ masternode.conf. Valid modes are: `all`, `missing`, or `disabled`.
*Example from Dash Core 0.12.2*
Start all masternodes in masternodes.conf
Start all masternodes in masternodes<!--noref-->.conf
{% highlight bash %}
dash-cli -testnet masternode start-all
@ -360,7 +360,7 @@ Result:
{% endhighlight %}
Start missing masternodes in masternodes.conf
Start missing masternodes in masternodes<!--noref-->.conf
{% highlight bash %}
dash-cli -testnet masternode start-missing
@ -376,7 +376,7 @@ Result:
{% endhighlight %}
Start disabled masternodes in masternodes.conf
Start disabled masternodes in masternodes<!--noref-->.conf
{% highlight bash %}
dash-cli -testnet masternode start-disabled
@ -396,9 +396,9 @@ Result:
{% endhighlight %}
###### Masternode Status
###### Masternode<!--noref--> Status
The `masternode status` RPC prints masternode status information.
The `masternode<!--noref--> status` RPC prints masternode status information.
*Parameters: none*
@ -449,9 +449,9 @@ Result:
{% endhighlight %}
###### Masternode List
###### Masternode<!--noref--> List
The `masternode list` prints a list of all known masternodes.
The `masternode<!--noref--> list` prints a list of all known masternodes.
This RPC uses the same parameters and returns the same data as
[masternodelist][rpc masternodelist]. Please reference it for full details.
@ -471,9 +471,9 @@ Result:
{% endhighlight %}
###### Masternode List-conf
###### Masternode<!--noref--> List-conf
The `masternode list-conf` RPC prints masternode.conf in JSON format.
The `masternode<!--noref--> list-conf` RPC prints masternode<!--noref-->.conf in JSON format.
*Parameters: none*
@ -551,9 +551,9 @@ Result:
{% endhighlight %}
###### Masternode Winner
###### Masternode<!--noref--> Winner
The `masternode winner` RPC prints info on the next masternode winner to vote for.
The `masternode<!--noref--> winner` RPC prints info on the next masternode winner to vote for.
*Parameters: none*
@ -622,9 +622,9 @@ Result:
{% endhighlight %}
###### Masternode Winners
###### Masternode<!--noref--> Winners
The `masternode winners` RPC prints the list of masternode winners.
The `masternode<!--noref--> winners` RPC prints the list of masternode winners.
By default, the 10 previous block winners, the current block winner, and the
next 20 block winners are displayed. More past block winners can be requested

View file

@ -26,7 +26,7 @@ The `masternodebroadcast` RPC {{summary_masternodeBroadcast}}
###### MNB create-alias
The `masternodebroadcast create-alias` RPC creates single remote masternode broadcast message by assigned alias configured in `masternode.conf`.
The `masternodebroadcast create-alias` RPC creates single remote masternode broadcast message by assigned alias configured in `masternode<!--noref-->.conf`.
*Parameter #2---masternode alias*
@ -81,7 +81,7 @@ Result:
###### MNB create-all
The `masternodebroadcast create-all` RPC creates remote masternode broadcast messages for all masternodes configured in `masternode.conf`.
The `masternodebroadcast create-all` RPC creates remote masternode broadcast messages for all masternodes configured in `masternode<!--noref-->.conf`.
*Result---broadcast message(s)*

View file

@ -37,7 +37,7 @@ To display the status of sporks, use the `show` or `active` syntax.
p: "Required<br>(exactly 1)"
d: "Object containing status"
- n: "→<br>`Spork Value`"
- n: "→<br>`Spork<!--noref--> Value`"
t: "int64_t"
p: "Required<br>(1 or more)"
d: "Spork value (epoch datetime to enable/disable)"
@ -75,7 +75,7 @@ Result:
p: "Required<br>(exactly 1)"
d: "Object containing status"
- n: "→<br>`Spork Activation Status`"
- n: "→<br>`Spork<!--noref--> Activation Status`"
t: "bool"
p: "Required<br>(1 or more)"
d: "Spork activation status"

View file

@ -19,7 +19,7 @@ The `voteraw` RPC {{summary_voteRaw}}
*Parameter #1---masternode transaction hash*
{% itemplate ntpd1 %}
- n: "`masternode-tx-hash`"
- n: "`masternode<!--noref-->-tx-hash`"
t: "string (hex)"
p: "Required<br>(exactly 1)"
d: "Hash of the masternode collateral transaction"
@ -29,7 +29,7 @@ The `voteraw` RPC {{summary_voteRaw}}
*Parameter #2---vote signal*
{% itemplate ntpd1 %}
- n: "`masternode-tx-index`"
- n: "`masternode<!--noref-->-tx-index`"
t: "string"
p: "Required<br>(exactly 1)"
d: "Index of the masternode collateral transaction"

View file

@ -46,12 +46,12 @@ hardcoded into Dash Core. The response to the lookup should include one or more
incoming connections. For example, using the [Unix `dig`command][dig command]:
;; QUESTION SECTION:
;dnsseed.masternode.io. IN A
;dnsseed.masternode<!--noref-->.io. IN A
;; ANSWER SECTION:
dnsseed.masternode.io. 60 IN A 192.0.2.113
dnsseed.masternode.io. 60 IN A 198.51.100.231
dnsseed.masternode.io. 60 IN A 203.0.113.183
dnsseed.masternode<!--noref-->.io. 60 IN A 192.0.2.113
dnsseed.masternode<!--noref-->.io. 60 IN A 198.51.100.231
dnsseed.masternode<!--noref-->.io. 60 IN A 203.0.113.183
[...]