Instead of talking about a majority of miners, it is better to talk
about a majority of available hashrate. There is no way to determine the
number of miners that exist, and it is confusing to talk about a
"majority of miners" as a consequence of this and other reasons.
As discussed on BitcoinTalk, there was confusion about whether a
non-upgraded node would switch to the strongest chain despite that chain
not following the consensus rules known to the non-upgraded node. Also
updated to mention Bitcoin Core 0.10.0 now that it's RC'd.
Ref: https://bitcointalk.org/index.php?topic=909732.msg9999032#msg9999032
Suggested by Saivann: RPC tables with Name/Type/Presence/Description
format are now in .ntpd CSS class so that we can format them specially.
We also change the style of all dev doc tables to replace bold table
headings (thead) with a double-line border-bottom. This makes the
theads look less like section headings and prevents us from over-using
bold.
Minor: a Makefile warning message has been made more explicit (also
suggested by Saivann) and another Makefile rule was updated to catch
more broken tables.
* All previously-documented RPCs have had their text completely
rewritten.
* All new RPCs and changed RPCs in Bitcoin Core 0.10.0 have been
documented, except for hidden RPCs.
* A new RPC "Quick Reference" section has been added to make finding the
right RPC easier.
* A "See Also" subsection has been added to the end of every RPC
pointing to other relevant information.
* All previous examples in the RPC section have been re-run and updated
as necessary.
* Syntax highlighting has been added wherever possible.
* Hash byte order has been specified as RPC byte order everywhere it's
used in RPCs.
Briefly describe the JSON-RPC 1.0 format as used by Bitcoin Core and how
bitcoin-cli abstracts away some of the details. Also link to the
Proper Money Handling wiki page. (This as a vanguard PR preparing the
way for a larger overhaul of our RPC docs, including updating them for
0.10.)
