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.

_includes/ref_core_rpc_intro.md

@@ -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).

_includes/ref_transactions.md

@@ -210,13 +210,13 @@ A raw transaction has the following top-level format:
 |----------|--------------|---------------------|-------------
 | 4        | version      | uint32_t            | Transaction version number; currently version 1.  Programs creating transactions using newer consensus rules may use higher version numbers.
 | *Varies* | tx_in count  | compactSize uint    | Number of inputs in this transaction.
-| *Varies* | tx_in        | *See TxIn Below*    | Transaction inputs.
+| *Varies* | tx_in        | txIn                | Transaction inputs.  See description of txIn below.
-| *Varies* | tx_out count | compactSize uint    | Number outputs in this transaction
+| *Varies* | tx_out count | compactSize uint    | Number of outputs in this transaction.
-| *Varies* | tx_out       | *See TxOut Below*   | Transaction outputs.
+| *Varies* | tx_out       | txOut               | Transaction outputs.  See description of txOut below.
 | 4        | lock_time    | uint32_t            | A time (Unix epoch time) or block number.  See the [locktime parsing rules][]. 
 
-A transaction may have multiple inputs and outputs, so the TxIn and
+A transaction may have multiple inputs and outputs, so the txIn and
-TxOut structures may recur within a transaction. CompactSize unsigned
+txOut structures may recur within a transaction. CompactSize unsigned
 integers are a form of variable-length integers; they are described in
 the [CompactSize section][CompactSize unsigned integer].
 
@@ -231,9 +231,9 @@ Each non-coinbase input spends an outpoint from a previous transaction.
 
 | Bytes    | Name             | Data Type            | Description
 |----------|------------------|----------------------|--------------
-| 36       | previous_output  | *See Outpoint Below* | The previous outpoint being spent.
+| 36       | previous_output  | outpoint             | The previous outpoint being spent.  See description of outpoint below.
 | *Varies* | script bytes     | compactSize uint     | The number of bytes in the signature script.  Maximum is 10,000 bytes.
-| *Varies* | signature script | char[]              | A script-language script which satisfies the conditions placed in the outpoint's pubkey script.  Should only contain data pushes; see the [signature script modification warning][].
+| *Varies* | signature script | char[]               | A script-language script which satisfies the conditions placed in the outpoint's pubkey script.  Should only contain data pushes; see the [signature script modification warning][].
 | 4        | sequence         | uint32_t             | Sequence number; see [sequence number][].  Default for Bitcoin Core and almost all other programs is 0xffffffff.
 
 {% endautocrossref %}
@@ -276,7 +276,7 @@ to a new pay-to-pubkey-hash (P2PKH) output.
 {% highlight text %}
 01000000 ................................... Version
 
-01 ......................................... Number of TxIns
+01 ......................................... Number of inputs
 |
 | 7b1eabe0209b1fe794124575ef807057
 | c77ada2138ae4fa8d6c4de0398a14f3f ......... Outpoint TXID

_less/screen.less

@@ -753,6 +753,7 @@ table td,table th{
 	width:600px;
 	margin:auto 0 auto auto;
 	position:relative;
+	text-align: left;
 }
 .toccontent h2{
 	font-size:150%;