fix docs links & stuff (#1273)

* fix links in docs/spec etc, closes #1261

* spec: remove ref to non-existant repo

* codecov you weirdo

docs/specification/new-spec/README.md

@@ -4,11 +4,6 @@ This is a markdown specification of the Tendermint blockchain.
 It defines the base data structures, how they are validated,
 and how they are communicated over the network.
 
-XXX: this spec is a work in progress and not yet complete - see github
-[issues](https://github.com/tendermint/tendermint/issues) and
-[pull requests](https://github.com/tendermint/tendermint/pulls)
-for more details.
-
 If you find discrepancies between the spec and the code that
 do not have an associated issue or pull request on github,
 please submit them to our [bug bounty](https://tendermint.com/security)!
@@ -24,18 +19,16 @@ please submit them to our [bug bounty](https://tendermint.com/security)!
 
 ### P2P and Network Protocols
 
-TODO: update links
-
-- [The Base P2P Layer](p2p/README.md): multiplex the protocols ("reactors") on authenticated and encrypted TCP connections
-- [Peer Exchange (PEX)](pex/README.md): gossip known peer addresses so peers can find each other
-- [Block Sync](block_sync/README.md): gossip blocks so peers can catch up quickly
-- [Consensus](consensus/README.md): gossip votes and block parts so new blocks can be committed
-- [Mempool](mempool/README.md): gossip transactions so they get included in blocks
-- [Evidence](evidence/README.md): TODO
+- [The Base P2P Layer](p2p): multiplex the protocols ("reactors") on authenticated and encrypted TCP connections
+- [Peer Exchange (PEX)](reactors/pex): gossip known peer addresses so peers can find each other
+- [Block Sync](reactors/block_sync): gossip blocks so peers can catch up quickly
+- [Consensus](reactors/consensus): gossip votes and block parts so new blocks can be committed
+- [Mempool](reactors/mempool): gossip transactions so they get included in blocks
+- Evidence: TODO
 
 ### More
-- [Light Client](light_client/README.md): TODO
-- [Persistence](persistence/README.md): TODO
+- Light Client: TODO
+- Persistence: TODO
 
 ## Overview
 

docs/specification/new-spec/reactors/consensus/consensus-reactor.md

@@ -31,7 +31,7 @@ Updates (state transitions) happen on timeouts, complete proposals, and 2/3 majo
 It receives messages from peers, internal validators and from Timeout Ticker 
 and invokes the corresponding handlers, potentially updating the RoundState. 
 The details of the protocol (together with formal proofs of correctness) implemented by the Receive Routine are 
-discussed in separate document (see [spec](https://github.com/tendermint/spec)). For understanding of this document
+discussed in separate document. For understanding of this document
 it is sufficient to understand that the Receive Routine manages and updates RoundState data structure that is 
 then extensively used by the gossip routines to determine what information should be sent to peer processes.
 

docs/specification/new-spec/reactors/consensus/consensus.md

@@ -11,7 +11,7 @@ next block should be; a validator might vote with a `VoteMessage` for a differen
 round, enough number of processes vote for the same block, then this block is committed and later
 added to the blockchain. `ProposalMessage` and `VoteMessage` are signed by the private key of the
 validator. The internals of the protocol and how it ensures safety and liveness properties are
-explained [here](https://github.com/tendermint/spec).
+explained in a forthcoming document.
 
 For efficiency reasons, validators in Tendermint consensus protocol do not agree directly on the
 block as the block size is big, i.e., they don't embed the block inside `Proposal` and