typo (#212)

inormation should be in"f"ormation

01_introduction.asciidoc

@@ -21,7 +21,7 @@ Because blockchains are gossip protocols, each node is required to know and vali
 The side effects of increasing the block size or the decreasing the block time with respect to centralization of the network are severe as a few calculations with the numbers show. 
 Let us assume the usage of Bitcoin grows so that the network has to process 40.000 transactions per second.
 Assuming 250 Bytes on average per transaction this would result in a data stream of 10 Megabyte per second or 80 Mbit/s just to be able to receive all the transactions.
-This is does not include the traffic overhead of forwarding the transaction inormation to other peers.
+This is does not include the traffic overhead of forwarding the transaction information to other peers.
 While single hosts on the internet could handle such a load of traffic our current internet would not be able to support this traffic for a large fraction of hosts.
 Also storing this information locally would result in 864000 Megabyte per day. This is roughly 1 Terabyte of data or the size of a hard drive.
 While verifying 40.000 ECDSA signatures per second seems barely feasable (c.f.: https://bitcoin.stackexchange.com/questions/95339/how-many-bitcoin-transactions-can-be-verified-per-second) nodes could hardly catch up initial sync of the blockchain.