init-doc: fix typo

assets/init-doc/about

@@ -4,7 +4,7 @@
 IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas
 from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bit-
 torrent swarm, exchanging git objects. IPFS provides an interface as simple
-as the HTTP web, but with permanence built in. You can also mount the world
+as the HTTP web, but with permanence built-in. You can also mount the world
 at /ipfs.
 
 IPFS is a protocol:
@@ -20,14 +20,14 @@ IPFS is a web:
 - can be used to view documents like the web
 - files accessible via HTTP at `http://ipfs.io/<path>`
 - browsers or extensions can learn to use `ipfs://` directly
-- hash-addressed content guarantees authenticity
+- hash-addressed content guarantees the authenticity
 
 IPFS is modular:
 - connection layer over any network protocol
 - routing layer
 - uses a routing layer DHT (kademlia/coral)
 - uses a path-based naming service
-- uses bittorrent-inspired block exchange
+- uses BitTorrent-inspired block exchange
 
 IPFS uses crypto:
 - cryptographic-hash content addressing
@@ -40,10 +40,10 @@ IPFS is p2p:
 - completely decentralized architecture
 - **no** central point of failure
 
-IPFS is a cdn:
+IPFS is a CDN:
 - add a file to the filesystem locally, and it's now available to the world
 - caching-friendly (content-hash naming)
-- bittorrent-based bandwidth distribution
+- BitTorrent-based bandwidth distribution
 
 IPFS has a name service:
 - IPNS, an SFS inspired name system