Merge branch 'km/incorporate_docs' of https://github.com/0xPolygon/po…

…lygon-edge into km/incorporate_docs

wiki-docs/Dockerfile

@@ -1,12 +1,15 @@
 FROM python:3.9-alpine
 
-RUN apk update
-RUN apk add rsync
-RUN apk add git
-RUN apk add nodejs npm
+# Install system dependencies
+RUN apk update && \
+    apk add --no-cache rsync git nodejs npm && \
+    rm -rf /var/cache/apk/*
+
+# Copy and install Python dependencies
 COPY requirements.txt requirements.txt
 RUN pip install -r requirements.txt --no-cache-dir
 
+# Switch to a non-root user (if 'nonroot' is already created)
 USER nonroot
 
 # Build doc by default

wiki-docs/docs/contracts/reward-pool.md

@@ -1,6 +1,6 @@
 ## Overview
 
-`RewardPool` is library for the management and distributiion validator rewards.
+`RewardPool` is library for the management and distribution of validator rewards.
 Each validator has a reward pool for delegators delegating funds to them.
 
 ## Functions

wiki-docs/docs/design/consensus/polybft/ibft.md

@@ -22,7 +22,7 @@ A validator's voting power is proportional to the amount of stake they have lock
 
 PolyBFT limits network participation to around 100 validators, and a variable amount of stake is used as a fixed stake criterion to limit the system's security and can make the system economically vulnerable. The validator set in the PolyBFT does not update on each block but is fixed during n block periods known as an epoch.
 
-The `n` block period to define one epoch is determined by governance, and until then, validators will remain the same. At the end of the epoch, a special state transaction to validatorSetManagementContract is emitted, notifying the system about the validators' uptime during the epoch. It is up to the smart contract to reward validators by their uptime and update the validator set for the next epoch. There is a function getValidatorSet which returns the current validator set at any time.
+The `n` block period to define one epoch is determined by `genesis` configuration, and until then, validators will remain the same. At the end of the epoch, a special state transaction to validatorSetManagementContract is emitted, notifying the system about the validators' uptime during the epoch. It is up to the smart contract to reward validators by their uptime and update the validator set for the next epoch. There is a function getValidatorSet which returns the current validator set at any time.
 
 !!! note
     Proposer selection algorithm - Section is being updated

wiki-docs/docs/operate/deploy/staking/stake.md

@@ -2,7 +2,7 @@ In this section, we'll walkthrough how to stake WMATIC on the associated rootcha
 
 ## i. Initial Staking on the Rootchain
 
-Each validator needs to perform initial staking on the rootchain `StakeManager` contract. This is done using the `polygon-edge polybft stake` command. **Note that this command is for testing purposes only.**
+Each validator needs to perform initial staking on the rootchain `StakeManager` contract. This is done using the `polygon-edge root stake` command. **Note that this command is for testing purposes only.**
 
 <details>
 <summary>Flags ↓</summary>