Change Text Alignment & Fix Some Typos

* Replaced text justification with left-align (raggedright) for all text
  in dev docs.

    * Removed previous manual left-align in RPC byte order table

* Changed placement of See Below text partly based on a suggestion by
  @saivann (thanks!)

* Normalized capitialization of special structures (e.g. s/TxIn/txIn/)
  to be consistent with some other parts of the docs. (I don't think
  we're fully consistent on this in all parts of the docs. I'll put a
  rule in the style guide today and then we can make changes on the next
  global proofread.)

* Fixed missing period found by @saivann (thanks!) and a related missing
  preposition.
This commit is contained in:
David A. Harding 2014-11-04 14:30:57 -05:00
parent 0af6ef09ff
commit 6ae33424e5
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7
3 changed files with 9 additions and 12 deletions

View file

@ -45,8 +45,6 @@ other Bitcoin software, this reversal of hashes has become the standard
way to refer to certain objects. The table below should make clear where
each byte order is used.
<div style="text-align: left;" markdown="1">
|---------------+---------------------|-----------------|
| Data | Internal Byte Order ("Big Endian") | RPC Byte Order ("Little Endian") |
|---------------|---------------------|-----------------|
@ -63,8 +61,6 @@ each byte order is used.
| P2SH Hashes: RIPEMD160(SHA256(redeem script)) | Used in both addresses and pubkey scripts | **N/A:** RPCs use addresses which use internal byte order |
|---------------|---------------------|-----------------|
</div>
Note: RPCs which return raw results, such as `getrawtransaction` or the
raw mode of `getblock`, always display hashes as they appear in blocks
(internal byte order).