Small fixes to FullNode basics. (aptos-labs#199)

developer-docs-site/docs/basics/basics-fullnodes.md

@@ -2,14 +2,14 @@
 title: "FullNodes"
 slug: "basics-fullnodes"
 ---
-An Aptos node is a peer entity of the Aptos ecosystem that tracks the [state](/reference/glossary#state) of the Aptos Blockchain. Clients interact with the blockchain via Aptos nodes. There are two types of nodes:
+An Aptos node is an entity of the Aptos ecosystem that tracks the [state](/reference/glossary#state) of the Aptos Blockchain. Clients interact with the blockchain via Aptos nodes. There are two types of nodes:
 * [Validator nodes](basics-validator-nodes.md)
 * FullNodes
 
 Each Aptos node comprises several logical components:
 * [REST service](/reference/glossary#rest-service)
 * [Mempool](basics-validator-nodes.md#mempool)
-* [Consensus](basics-validator-nodes.md#consensus)
+* [Consensus (disabled in FullNodes)](basics-validator-nodes.md#consensus)
 * [Execution](basics-validator-nodes.md#execution)
 * [Virtual Machine](basics-validator-nodes.md#virtual-machine)
 * [Storage](basics-validator-nodes.md#storage)
@@ -19,7 +19,7 @@ The [Aptos-core](/reference/glossary#aptos-core) software can be configured to r
 
 ## Overview
 
-FullNodes can be run by anyone. FullNodes re-execute all transactions in the history of the Aptos blockchain. FullNodes replicate the full state of the blockchain by synchronizing with an upstream participant either other FullNodes or validators, receiving the set of transactions and the [accumulator hash root](/reference/glossary#accumulator-root-hash) of the ledger after their execution signed by the validtors. In addition, FullNodes accept transactions submitted by Aptos clients and forward them upstream, eventually to validator nodes. While FullNodes and validators share the same code, FullNodes do not participate in consensus and only verify it.
+FullNodes can be run by anyone. FullNodes re-execute all transactions in the history of the Aptos Blockchain. FullNodes replicate the entire state of the blockchain by synchronizing with upstream participants, e.g., other FullNodes or validator nodes. To verify blockchain state, FullNodes receive the set of transactions and the [accumulator hash root](/reference/glossary#accumulator-root-hash) of the ledger signed by the validators. In addition, FullNodes accept transactions submitted by Aptos clients and forward them directly (or indirecly) to validator nodes. While FullNodes and validators share the same code, FullNodes do not participate in consensus.
 
 Third-party blockchain explorers, wallets, exchanges, and DApps may run a local FullNode to:
 * Leverage the REST interface for blockchain interactions.