Merge pull request #47 from dagurval/spelling

fix spelling

_layouts/index-page.html

@@ -53,7 +53,7 @@ <h2 id="sec-manifesto"><i class="fa fa-compass fa-2x"></i>What we stand for</h2>
           <li class="sublist"><ul>
             <li>We believe <b>unconfirmed transactions are important</b>. Many merchants want or need to accept
                 payments within seconds rather than minutes or hours. XT accepts this fact and does what it can to
-                minimise the risk, then help sellers judge what remains. It is committed to <a href="http://satoshi.nakamotoinstitute.org/emails/cryptography/8/" title="Satoshi Nakamoto Institute - Re: Bitcoin P2P e-cash paper">
+                minimize the risk, then help sellers judge what remains. It is committed to <a href="http://satoshi.nakamotoinstitute.org/emails/cryptography/8/" title="Satoshi Nakamoto Institute - Re: Bitcoin P2P e-cash paper">
                 the first seen rule</a>. We will not adopt changes that make unconfirmed transactions riskier.
             </li>
             <li><b>Lightweight wallets are important</b>. Most users cannot or will not run a fully verifying node.
@@ -65,7 +65,7 @@ <h2 id="sec-manifesto"><i class="fa fa-compass fa-2x"></i>What we stand for</h2>
 
           <li><b>Decision making is quick and clear.</b> Decisions are made according to a leadership hierarchy. The XT
               software encodes decisions that follow the above principles: people who disagree are welcome to use
-              different software, or patch ours. We do not consider writing principled software to be centralising
+              different software, or patch ours. We do not consider writing principled software to be centralizing
               and do not refuse to select reasonable defaults.
           </li>
 
@@ -89,7 +89,7 @@ <h2 id="sec-hardfork"><i class="fa fa-gg fa-2x"></i>Block size hard fork</h2>
             lightweight wallets were developed, however, this was never done. As predicted Bitcoin has run out of capacity and users are
             experiencing reliability problems as a result</a>.
 The Bitcoin Core developers are unwilling to increase the block chain's capacity, finally this caused the network split into Bitcoin Cash (BCH) and Bitcoin (BTC).
-Miners and users who disagree with them have switched to Bitcoin XT or switch to other clients following the Bitcoin Cash consensus.
+Miners and users who disagree with them have switched to Bitcoin XT or switched to other clients following the Bitcoin Cash consensus.
         </p>
 
         <p>

patches.html

@@ -17,13 +17,13 @@ <h1>Some selected features of XT</h1>
 
 	  <li><b>Thin block relay</b>. Bitcoin XT is the only client that supports <em>both</em> the <a href="https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/bu-xthin-protocol.md">XThin</a> and <a href="https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki">Compact Block</a> protocols. When running XT you will efficiently keep up with the blockchain. You will also help the network by effectively acting as a bridge between nodes that support either protocol, but not both.</li>
 
-	  <li><b>Double spend relaying</b>. Detect and help other clients detect double spending transactions. This allows sellers to learn about attempts to defraud them faster and with a lower cost to the peer to peer network. The Bitcoin-Qt wallet will show broadcast double spend attempts in red. There is a new <em>-respendnotify</em> command line flag, and conflicts are reported via the RPC interface. Even if this feature is not needed by you, by running XT you will help those that benifit from it. </li>
+	  <li><b>Double spend relaying</b>. Detect and help other clients detect double spending transactions. This allows sellers to learn about attempts to defraud them faster and with a lower cost to the peer to peer network. The Bitcoin-Qt wallet will show broadcast double spend attempts in red. There is a new <em>-respendnotify</em> command line flag, and conflicts are reported via the RPC interface. Even if this feature is not needed by you, by running XT you will help those that benefit from it. </li>
 
-          <li><b>Support BIP 64 ("getutxos")</b>. This allows peers to request the contents of a ledger entry over the network. It is useful for <a href="https://vinumeris.com/lighthouse" title="Lighthouse - Raise money with Bitcoin">the Lighthouse decentralised crowdfunding wallet</a> to present a better user interface, and for miscellaneous other tasks.</li>
+          <li><b>Support BIP 64 ("getutxos")</b>. This allows peers to request the contents of a ledger entry over the network. It is useful for <a href="https://vinumeris.com/lighthouse" title="Lighthouse - Raise money with Bitcoin">the Lighthouse decentralized crowdfunding wallet</a> to present a better user interface, and for miscellaneous other tasks.</li>
 
 	  <li><b>Enhances SPV security</b>. XT passes onto SPV wallets knowledge about unconfirmed ancestors of transactions, enabling them to better asses the risk of their unconfirmed transactions.</li>
 
-	  <li><b>Prioritize incoming connections</b>. It's possible to group IP-addresses of incoming connections and assign them priority. If connection slots become full, then a peer with a lower priority than the incoming connection will be disconnected. As a an anti-DoS masure, Tor exit nodes have optionally lower priority than regular IP addresses as to not reject mobile and home users.</li>
+	  <li><b>Prioritize incoming connections</b>. It's possible to group IP-addresses of incoming connections and assign them priority. If connection slots become full, then a peer with a lower priority than the incoming connection will be disconnected. As a an anti-DoS measure, Tor exit nodes have optionally lower priority than regular IP addresses as to not reject mobile and home users.</li>
           </ul>
         </div>
         </section>