fix(devx) implement feedback on docs

docs/content/about-iota/iota-architecture/staking-rewards.mdx

@@ -32,8 +32,9 @@ epoch. Similarly, when a user withdraws their stake, it stops counting from the
 
 ## Rewards Distribution
 
-At the end of each [epoch](epochs.mdx), gas fees and stake subsidies are distributed among validators and stakers as
-rewards. The amount of rewards a validator gets depends on:
+At the end of each [epoch](epochs.mdx), newly minted IOTA tokens are distributed as rewards among validators and stakers. Within each validator staking pool, stakers receive rewards proportionally through the appreciation of the pool's exchange rate. Validators also earn additional rewards, represented as StakedIOTA objects, which they receive at the end of each epoch in proportion to the commissions generated by their staking pool.
+
+Each epoch's rewards are funded by newly minted IOTA tokens, totaling 767k IOTA per epoch. This amount is distributed across staking pools based on their voting power and the specified tallying rule. The amount of rewards a validator gets depends on:
 
 ### Performance
 

docs/content/developer/advanced/asset-tokenization.mdx

@@ -734,7 +734,7 @@ Afterward, it's necessary to modify the `Move.toml` file. Under the `[addresses]
 
 ##### Automatically
 
-The fields that are automatically filled are: `SUI_NETWORK`, `ASSET_TOKENIZATION_PACKAGE_ID` and `REGISTRY`.
+The fields that are automatically filled are: `IOTA_NETWORK`, `ASSET_TOKENIZATION_PACKAGE_ID` and `REGISTRY`.
 
 To publish with the bash script run:
 

docs/content/operator/validator-config.mdx

@@ -13,7 +13,7 @@ Validators on the IOTA network run special nodes and have additional tasks and r
 
 To run an IOTA validator, you must set up and configure an IOTA Validator node. After you have a running node, you must have a minimum of 2 million IOTA in your staking pool to join the validator set on the IOTA network.
 
-To learn how to set up and configure an IOTA Validator node, see [IOTA for Node Operators](https://github.com/iotaledger/iota/blob/main/nre/iota_for_node_operators.md) on GitHub. The guide includes all of the information you need to configure your Validator node. It also provides guidance on the tasks you must perform after you join the validator set.
+To learn how to set up and configure an IOTA Validator node, see [IOTA for Node Operators](../operator/validator-operation/validator-tasks.mdx) on GitHub. The guide includes all of the information you need to configure your Validator node. It also provides guidance on the tasks you must perform after you join the validator set.
 
 Specific steps you must take include:
 
@@ -28,15 +28,24 @@ Specific steps you must take include:
 
 <StakingPoolReqs />
 
-## Hardware requirements to run a Validator node
+## Hardware requirements to run a Validator node on Mainnet
 
-Suggested minimum hardware specifications to run an IOTA Validator node:
+Suggested minimum hardware specifications to run an IOTA Validator node on Mainnet:
 
 - CPU: 24 physical cores (or 48 virtual cores)
 - Memory: 128 GB
 - Storage: 4 TB NVME
 - Network: 1 Gbps
 
+## Hardware requirements to run a Validator node on Testnet
+
+Suggested minimum hardware specifications to run an IOTA Validator node on Testnet:
+
+- CPU: 8 cores
+- Memory: 64 GB
+- Storage: 2 TB NVME
+- Network: 1 Gbps
+
 ## Validator consensus and voting power 
 
 The total voting power on IOTA is always 10,000, regardless of the amount staked. Therefore, the quorum threshold is 6,667. There is no limit to the amount of IOTA users can stake with a validator. Each validator has consensus voting power proportional to IOTA in its staking pool, with one exception: the voting power of an individual validator is capped at 1,000 (10% of the total). If a validator accumulates more than 10% of total stake, the validator's voting power remains fixed at 10%, and the remaining voting power is spread across the rest of the validator set.