Merge pull request #829 from maticnetwork/new-to-polygon

Update new to polygon

Author: Nazeim

docs/home/new-to-matic.md

@@ -5,17 +5,17 @@ description: Build your next blockchain app on Polygon.
 keywords:
   - docs
   - matic
-image: https://matic.network/banners/matic-network-16x9.png 
+image: https://matic.network/banners/matic-network-16x9.png
 ---
 Polygon is a scaling solution for public blockchains. Polygon PoS supports all the existing Ethereum tooling along with faster and cheaper transactions.
 
-### Types of Interaction on Polygon
+## Types of Interaction on Polygon
 
 * [Polygon PoS chain](/docs/develop/getting-started)
 * [Ethereum + Polygon with PoS bridge](https://docs.polygon.technology/docs/develop/ethereum-polygon/pos/getting-started)
 * [Ethereum + Polygon with Plasma bridge](https://docs.polygon.technology/docs/develop/ethereum-polygon/plasma/getting-started)
 
-### Deploy Smart Contracts
+## Deploy Smart Contracts
 
 <!-- ### Are you an Experience Blockchain Developer? -->
 
@@ -28,17 +28,53 @@ Polygon is a scaling solution for public blockchains. Polygon PoS supports all t
     - [Using Hardhat](/docs/develop/hardhat)
 * Configure the Web3 RPC-URL to https://rpc-mumbai.matic.today, *Everything else remains the same*
 
-### What is a Blockchain?
+## What is a Blockchain?
 Simply put, Blockchain is a shared, immutable ledger for recording transactions, tracking assets and building trust. Head over to [Blockchain Basics](blockchain-basics/blockchain) to read more.
 
 :movie_camera: [Your first DApp](https://www.youtube.com/watch?v=rzvk2kdjr2I)
 
-### What is a Sidechain?
+## What is a Sidechain?
 Think of a Sidechain as a clone of a 'parent' blockchain, supporting transfer of assets to and from the main chain. It is simply an alternate to parent chain that creates a new blockchain with its own mechanism of creating blocks (consensus mechanism). Connecting a sidechain to a parent chain involves setting up a method of moving assets between the chains.
 
 :page_facing_up: [Sidechains and Childchains](https://hackernoon.com/what-are-sidechains-and-childchains-7202cc9e5994)
-### What is Plasma?
-Plasma is a framework of secondary chains that will communicate and interact as sparingly as possible with the main chain. Child chain is a scaling solution for Ethereum (or any blockchain for that matter).
-It is a layer 2 solution for Ethereum that provides a framework for building ‘off-chain’ decentralised applications that are secure, scalable and swift.
 
-:page_facing_up: [Read more about Plasma](blockchain-basics/sidechain)
+## Validator and delegator roles
+
+On the Polygon Network, you can be a validator or a delegator. See:
+
+* [Who Is a Validator](/docs/validate/polygon-basics/who-is-validator)
+* [Who Is a Delegator](/docs/validate/polygon-basics/who-is-delegator)
+
+## Architecture
+
+If your goal is to become a validator, it is essential that you understand the Polygon architecture.
+
+See [Polygon Architecture](/docs/validate/validator/architecture).
+
+### Components
+
+To have a granular understanding of the Polygon architecture, see core components:
+
+* [Heimdall](/docs/contribute/heimdall/overview)
+* [Bor](/docs/contribute/bor/overview)
+* [Contracts](/docs/contribute/contracts/stakingmanager)
+
+#### Codebases
+
+To have a granular understanding of the core components, see the codebases:
+
+* [Heimdall](https://github.com/maticnetwork/heimdall)
+* [Bor](https://github.com/maticnetwork/bor)
+* [Contracts](https://github.com/maticnetwork/contracts)
+
+## How-tos
+
+### Node setup
+
+* [Run a Validator Node with Ansible](/docs/validate/validate/run-validator-ansible)
+* [Run a Validator Node from Binaries](/docs/validate/validate/run-validator-binaries)
+
+### Staking operations
+
+* [Validator Staking Operations](/docs/validate/validate/validator-staking-operations)
+* [Delegate](/docs/validate/delegate)

docs/validate/validator/architecture.md

@@ -7,7 +7,7 @@ keywords:
   - matic
   - polygon
   - architecture
-image: https://matic.network/banners/matic-network-16x9.png 
+image: https://matic.network/banners/matic-network-16x9.png
 ---
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
@@ -30,26 +30,24 @@ The staking contracts implement the following features:
 * Enable penalties/slashing for activities such as double signing, validator downtime, etc.
 * Save [checkpoints](/docs/validate/glossary#checkpoint-transaction) on the Ethereum mainnet.
 
-The PoS mechanism also acts as a mitigation to the data unavailability problem for the Polygon sidechains in terms of Plasma.
-
-The Plasma contracts implement the [MoreVP Plasma framework](https://ethresear.ch/t/more-viable-plasma/2160). See also [an overview of the Polygon MoreVP implementation](https://ethresear.ch/t/account-based-plasma-morevp/5480). 
+The PoS mechanism also acts as a mitigation to the data unavailability problem for the Polygon sidechains.
 
 ## Heimdall (validation layer)
 
-Heimdall layer handles the aggregation of blocks produced by [Bor](/docs/validate/glossary#bor) into a Merkle tree and publishing the Merkle root periodically to the root chain. The periodic publishing of snapshots of the Bor sidechain are called [checkpoints](/docs/validate/glossary#checkpoint-transaction). 
+Heimdall layer handles the aggregation of blocks produced by [Bor](/docs/validate/glossary#bor) into a Merkle tree and publishing the Merkle root periodically to the root chain. The periodic publishing of snapshots of the Bor sidechain are called [checkpoints](/docs/validate/glossary#checkpoint-transaction).
 
 For every few blocks on Bor, a validator on the Heimdall layer:
 
 1. Validates all the blocks since the last checkpoint.
 2. Creates a Merkle tree of the block hashes.
 3. Publishes the Merkle root hash to the Ethereum mainnet.
 
-Checkpoints are important for two reasons: 
+Checkpoints are important for two reasons:
 
 1. Providing finality on the root chain.
 2. Providing proof of burn in withdrawal of assets.
 
-An overview of the process: 
+An overview of the process:
 
 * A subset of active validators from the pool is selected to act as [block producers](/docs/validate/glossary#block-producer) for a [span](/docs/validate/glossary#span). These block producers are responsible for creating blocks and broadcasting the created blocks on the network.
 * A checkpoint includes the Merkle root hash of all blocks created during any given interval. All nodes validate the Merkle root hash and attach their signature to it.
@@ -60,8 +58,8 @@ See also [Heimdall architecture](/docs/contribute/heimdall/overview).
 
 ### Bor (block producer layer)
 
-Bor is Polygon's sidechain block producer — the entity responsible for aggregating transactions into blocks. 
+Bor is Polygon's sidechain block producer — the entity responsible for aggregating transactions into blocks.
 
 Bor block producers are a subset of the validators and are shuffled periodically by the [Heimdall](/docs/validate/glossary#heimdall) validators.
 
-See also [Bor architecture](/docs/contribute/bor/overview).
+See also [Bor architecture](/docs/contribute/bor/overview).