spec links / glossary audit (#258)

documents/build.md

@@ -10,7 +10,7 @@ description: Learn how to build your own app via LBRY in this comprehensive guid
 Want to build something on top of LBRY? This is the place to get started.
 
 At least, it's the place to get started so long as you have some idea of what LBRY _is_. If you don't, you should read the
-[Overview](/overview) first.
+[Overview](/overview) and the [spec](/spec) for more technical details. 
 
 Want to build with us rather than on your own? Check out our [Contributing Guide](/contribute).
 
@@ -18,7 +18,7 @@ Want to build with us rather than on your own? Check out our [Contributing Guide
 
 - You want to build an application that contributes to the world's knowledge, or benefits from global, shared discovery.
 - You want to replace an existing centralized service related to digital content distribution with a decentralized or community-controlled one.
-- You want to build an application that is [[permissionless]] to interact with.
+- You want to build an application that is permissionless to interact with.
 - You want to further openness, freedom of information, and/or personal choice on the internet.
 
 ### When Not to Use LBRY

documents/partials/overview/lbrycrd.md

@@ -4,7 +4,7 @@ LBRY uses a public, proof-of-work blockchain that is very similar to Bitcoin. Th
 
 The most salient feature of the LBRY blockchain is the association of a normalized string of characters (a "name") with a structured set of metadata. This coupling is called a [[claim]]. The content referenced by a claim can be accessed as a LBRY URL, e.g. [lbry://hellolbry](/playground?url=hellolbry).
 
-The LBRY blockchain stores names and metadata in a parallel [[Merkle tree]], separate from the tree used to store transaction data. This allows LBRY URLs to be trustfully resolved even without a full copy of the blockchain.
+The LBRY blockchain stores names and metadata in a parallel [Merkle tree](/resources/claimtrie), separate from the tree used to store transaction data. This allows LBRY URLs to be trustfully resolved even without a full copy of the blockchain.
 
 The metadata contains information about the content, such as the title, creator, price (if any), and a unique signature allowing the actual content to be fetched from the data network, the next level in the LBRY stack.
 

documents/partials/overview/lbrysdk.md

@@ -1,10 +1,10 @@
-While the blockchain is the innovation that makes LBRY _possible_, the Data Network is the layer that actually makes the blockchain _useful_.
+While the blockchain is the innovation that makes LBRY _possible_, the [Data Network](/spec#data) is the layer that actually makes the blockchain _useful_.
 
 At this level:
 
-- Metadata stored in the blockchain is interpreted and validated.
+- [Metadata](/spec#metadata] stored in the blockchain is interpreted and validated.
-- Data referenced by metadata is accessed and distributed via a peer-to-peer network.
+- [Data referenced by metadata](/spec#data) is accessed and distributed via a peer-to-peer network.
-- [[Identities]] are created, signed, and validated.
+- [Identities](/spec#channels) are created, signed, and validated.
 
 Data network operations are provided by the [lbrysdk](https://github.com/lbryio/lbry). This SDK also provides local wallet functionality and a set of APIs to facilitate building applications.
 

documents/partials/overview/lighthouse.md

@@ -1 +1 @@
-Lighthouse is a fast, advanced search engine for searching metadata stored in the LBRY blockchain.
+Lighthouse is a fast, advanced search engine for searching [metadata](/spec#metadata) stored in the LBRY blockchain.

documents/partials/overview/reflector.md

@@ -1 +1 @@
-Reflectors are a special class of hosting servers that facilitate end-user publishing. A reflector server (or server cluster) can accept LBRY content for hosting en masse as well as earn blockchain tokens for data fees.
+[Reflectors](/spec#reflectors-and-data-markets) are a special class of hosting servers that facilitate end-user publishing. A reflector server (or server cluster) can accept LBRY content for hosting en masse as well as earn blockchain tokens for data fees.

documents/resources/claimtrie.md

@@ -3,9 +3,9 @@ title: Merkle Claim Trie
 description: Publishes to the LBRY network get placed into a Merkle Claim Trie. Learn what that is and why trie is not a typo in this resource article. 
 ---
 
-How the data structure that organizes claims by names works, how proofs are generated/verified and how consensus on the state of the trie is represented.
+This article will discuss how the data structures that organize claims by names work, how proofs are generated/verified, and how consensus on the state of the trie is represented.
 
-For looking into how claims end up in the trie, [read this instead](https://lbry.io/faq/claimtrie-implementation).
+For looking into how claims end up in the trie, [read this instead](/spec#claimtrie).
 
 ## The Trie
 

documents/resources/consensus.md

@@ -3,7 +3,7 @@ title: Consensus Algorithm
 description: How does the LBRY blockchain achieve consensus? This resource page will explain. 
 ---
 
-LBRY uses [proof of work](https://en.bitcoin.it/wiki/Proof_of_work) as a consensus mechanism, the same way that Bitcoin does.
+LBRY uses [proof of work](https://en.bitcoin.it/wiki/Proof_of_work) as a [consensus mechanism](/spec#consensus), the same way that Bitcoin does.
 
 LBRY has differences in hash function, block targeting, and difficult adjustment.
 

documents/resources/download-overview.md

@@ -7,7 +7,7 @@ This resource outlines the step-by-step process of using the LBRY protocol to do
 
 ## Getting Started
 
-Downloading spans the three core components of LBRY (blockchain, DHT, blob exchange) and explains the structure of the claim metadata and the blobs that make up a LBRY stream.
+Downloading spans the three core components of LBRY (blockchain, DHT, blob exchange) and explains the structure of the [claim metadata](/spec#metadata) and the blobs that make up a [LBRY stream](/spec#data).
 
 You will need: