first attempt at fixing all links

spec/README.md

@@ -31,7 +31,7 @@ please submit them to our [bug bounty](https://tendermint.com/security)!
 - [Consensus Algorithm](./consensus/consensus.md)
 - [Creating a proposal](./consensus/creating-proposal.md)
 - [Time](./consensus/bft-time.md)
-- [Light-Client](./consensus/light-client.md)
+- [Light-Client](./consensus/light-client/README.md)
 
 ### P2P and Network Protocols
 

spec/consensus/fork-accountability.md

@@ -1,3 +0,0 @@
-# Fork Accountability - MOVED!
-
-Fork Accountability has moved to [light-client](./light-client/accountability).

spec/consensus/light-client.md

@@ -1,3 +0,0 @@
-# Light Client - MOVED!
-
-Light Client has moved to [light-client](./light-client).

spec/consensus/readme.md

@@ -23,7 +23,7 @@ Specification of the Tendermint consensus protocol.
   consensus state machine to recover from crashes.
 
 The protocol used to gossip consensus messages between peers, which is critical
-for liveness, is described in the [reactors section](/spec/reactors/consensus).
+for liveness, is described in the [reactors section](/spec/reactors/consensus/consensus.md).
 
 There is also a [stale markdown description](consensus.md) of the consensus state machine
 (TODO update this).

spec/p2p/node.md

@@ -12,7 +12,8 @@ Seeds should operate full nodes with the PEX reactor in a "crawler" mode
 that continuously explores to validate the availability of peers.
 
 Seeds should only respond with some top percentile of the best peers it knows about.
-See [the peer-exchange docs](https://github.com/tendermint/tendermint/blob/master/docs/spec/reactors/pex/pex.md)for details on peer quality.
+See [the peer-exchange docs](https://github.com/tendermint/spec/blob/master/spec/reactors/pex/pex.md) for
+ details on peer quality.
 
 ## New Full Node
 

spec/reactors/consensus/consensus.md

@@ -16,7 +16,8 @@ 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
 `VoteMessage`. Instead, they reach agreement on the `BlockID` (see `BlockID` definition in
-[Blockchain](https://github.com/tendermint/tendermint/blob/master/docs/spec/blockchain/blockchain.md#blockid) section) that uniquely identifies each block. The block itself is
+[Blockchain](https://github.com/tendermint/spec/blob/master/spec/blockchain/blockchain.md#blockid) section) 
+that uniquely identifies each block. The block itself is
 disseminated to validator processes using peer-to-peer gossiping protocol. It starts by having a
 proposer first splitting a block into a number of block parts, that are then gossiped between
 processes using `BlockPartMessage`.
@@ -65,7 +66,9 @@ type Proposal struct {
 ## VoteMessage
 
 VoteMessage is sent to vote for some block (or to inform others that a process does not vote in the
-current round). Vote is defined in the [Blockchain](https://github.com/tendermint/tendermint/blob/master/docs/spec/blockchain/blockchain.md#blockid) section and contains validator's
+current round). Vote is defined in the 
+[Blockchain](https://github.com/tendermint/spec/blob/master/spec/blockchain/blockchain.md#blockidd) 
+section and contains validator's
 information (validator address and index), height and round for which the vote is sent, vote type,
 blockID if process vote for some block (`nil` otherwise) and a timestamp when the vote is sent. The
 message is signed by the validator private key.

spec/reactors/mempool/reactor.md

@@ -7,7 +7,7 @@ See [this issue](https://github.com/tendermint/tendermint/issues/1503)
 Mempool maintains a cache of the last 10000 transactions to prevent
 replaying old transactions (plus transactions coming from other
 validators, who are continually exchanging transactions). Read [Replay
-Protection](../../../app-dev/app-development.md#replay-protection)
+Protection](https://github.com/tendermint/tendermint/blob/master/docs/app-dev/app-development.md#replay-protection)
 for details.
 
 Sending incorrectly encoded data or data exceeding `maxMsgSize` will result