Fix typo

We don't write test for the readme. :)

Cargo.toml

@@ -1,7 +1,10 @@
 [package]
 name = "silk"
 description = "A silky smooth implementation of the Loom architecture"
-version = "0.1.1"
+version = "0.1.3"
+documentation = "https://docs.rs/silk"
+homepage = "http://loomprotocol.com/"
+repository = "https://github.com/loomprotocol/silk"
 authors = [
     "Anatoly Yakovenko <aeyakovenko@gmail.com>",
     "Greg Fitzgerald <garious@gmail.com>",

README.md

@@ -3,18 +3,17 @@
 [![Build Status](https://travis-ci.org/loomprotocol/silk.svg?branch=master)](https://travis-ci.org/loomprotocol/silk)
 [![codecov](https://codecov.io/gh/loomprotocol/silk/branch/master/graph/badge.svg)](https://codecov.io/gh/loomprotocol/silk)
 
-# Silk, A Silky Smooth Implementation of the Loom Architecture
+# Silk, a silky smooth implementation of the Loom specification
 
 Loom is a new achitecture for a high performance blockchain. Its whitepaper boasts a theoretical
-throughput of 710k transactions per second on a 1 gbps network. The first implementation of the
-whitepaper is happening in the 'loomprotocol/loom' repository. That repo is aggressively moving
-forward, looking to de-risk technical claims as quickly as possible. This repo is quite a bit
-different philosophically. Here we assume the Loom architecture is sound and worthy of building
-a community around. We care a great deal about quality, clarity and short learning curve. We
-avoid the use of `unsafe` Rust and an write tests for *everything*.  Optimizations are only
-added when corresponding benchmarks are also added that demonstrate real performance boots. We
-expect the feature set here will always be a long ways behind the loom repo, but that this is
-an implementation you can take to the bank, literally.
+throughput of 710k transactions per second on a 1 gbps network. The specification is implemented
+in two git repositories. Reserach is performed in the loom repository. That work drives the
+Loom specification forward. This repository, on the other hand, aims to implement the specification
+as-is.  We care a great deal about quality, clarity and short learning curve. We avoid the use
+of `unsafe` Rust and write tests for *everything*.  Optimizations are only added when
+corresponding benchmarks are also added that demonstrate real performance boots. We expect the
+feature set here will always be a ways behind the loom repo, but that this is an implementation
+you can take to the bank, literally.
 
 # Developing