docs: polish content

Author: ines-toupeira

archive/index.md

@@ -6,35 +6,40 @@ links:
     title: Pre-registration
     description: How to be prepared to join the first epoch as a validator and earn rewards from the very beginning
     href: validator-registration
-    span: 6
+    span: half
   - title: Be part of the migration
     label: Node Operators
     href: node-operators
+    span: half
   - label: Learn more
     title: Deep dive into the technical details
     href: migration-technical-details
   - label: FAQ
     title: Check our FAQs for more information
     href: faqs
+  - label: PoS
+    title: Curious about the new PoS? Check the protocol
+    href: ../protocol/index
 ---
 
-# Nimiq Migration to Proof-of-Stake
+# Legacy PoW → PoS Migration
 
-We are transitioning from a Proof-of-Work blockchain to a Proof-of-Stake blockchain. Learn more about the migration process and how you can get involved.
+> [!NOTE]
+> This archive preserves the resources created for the Proof-of-Work to Proof-of-Stake transition.
 
 <NqGrid f-my-xl :cards="$frontmatter.links" />
 
 ## Understanding the Migration
 
-Nimiq is transitioning from a Proof-of-Work to a Proof-of-Stake blockchain through a special hard fork. The transition process includes several key phases:
+Nimiq completed the transition from a Proof-of-Work to a Proof-of-Stake blockchain through a special hard fork. The transition process included several key phases:
 
 - **Pre-registration Phase**: Establishes the first list of validators for the PoS blockchain within the PoW chain
 - **Pre-Staking Phase**: Users pre-stake their NIM
 - **Activation Phase**: Selects candidate transition blocks from the PoW chain and executes the transition to the PoS chain if at least 80% of the stake is ready
 
-During the migration, we will capture the entire blockchain state, including all accounts, balances, and transaction history. This means that users' balances will remain intact and will be transferred to the new PoS chain.
+During the migration, the entire blockchain state—including accounts, balances, and transaction history—was captured so that users' balances moved intact to the PoS chain.
 
-**There is no requirement to participate in the migration.** However, if you want, you can [become one of the first validators](validator-registration) or [migrate as an observer](node-operators). Nimiq ensures that no NIM will be lost during the process. We have [guides](#nimiq-migration-to-proof-of-stake) available for those who want to actively engage in the transition.
+**Participation was optional.** Those who wanted to contribute could [become one of the first validators](validator-registration) or [migrate as observers](node-operators). The captured state ensured no NIM was lost during the process, and the guides below document the steps that were available at the time.
 
 ## Most Asked Questions
 

index.md

@@ -76,10 +76,9 @@ hoverableGrid:
       description: Interactive, in‑browser walkthrough
       href: https://nimiq.guide
       icon: i-local:nimiq-tutorial
-    - title: RPC Playground
-      description: Test JSON‑RPC calls live
-      href: ./rpc-client/playground
-      icon: i-local:nimiq-rpc
+    - title: RPC Quick Start
+      description: Explore docs and run JSON-RPC from your environment
+      href: ./rpc-client/
     - title: Nimiq MCP
       description: Build with AI
       href: https://github.com/onmax/nimiq-mcp
@@ -156,7 +155,10 @@ popularResources:
           href: ./validators/staking-faq
         - text: Validators API
           href: https://github.com/nimiq/validators-api
-          # TODO: TS library. ARPL
+        - text: Validator RPC Docs
+          href: ./validators/rpc-docs/
+        - text: ARPL CLI Tool
+          href: https://github.com/sisou/arpl
     - title: Core & Protocol
       links:
         - text: Protocol Docs

migration/index.md

@@ -1,14 +1,11 @@
-# Migration Guide
+# Legacy Migration Guide (PoW → PoS)
 
-This section contains migration guides and resources for upgrading from Nimiq 1.0 to 2.0 (Albatross).
+> [!IMPORTANT]
+> This content documents the completed transition from PoW to PoS and is retained for historical reference.
 
 ## Migration Resources
 
 - [Migration for Integrators](migration-integrators) - Guide for integrators migrating to Nimiq 2.0
 - [JSON-RPC Migration](migration-json-rpc) - JSON-RPC API changes and migration guide
 - [Web Developers Migration](migration-web-developers) - Guide for web developers
 - [Technical Details](migration-technical-details) - Technical migration details and breaking changes
-
-::: warning
-This section is primarily for reference during the migration period. Most developers should start with the current documentation in the Protocol, Web Client, and RPC Client sections.
-:::

protocol/storage/merkle-trees.md

@@ -11,7 +11,7 @@ The Merkle Radix Tree is a data structure used in our blockchain system to store
 
 Merkle Radix Trees are significantly different from standard Merkle Trees. Leaf nodes with similar prefixes are paired up, while leaf nodes with unique prefixes are called “only child” nodes. Parent nodes in the tree can have multiple children or just one child. When a parent node has only one child, it merges with that child node, optimizing space within the tree. Likewise, as parent nodes can have an only child node, parent nodes can also have up to 16 children. Below is a simplified illustration of a Merkle Radix Tree.
 
-![Alt Text](/assets/images/protocol/merkle.png)
+![Diagram of a Merkle Radix Tree showing merged branches](/assets/images/protocol/merkle.png)
 
 When constructing the tree, nodes with similar prefixes are paired to form parent nodes, optimizing space by reducing the number of intermediate nodes. If a node does not have a sibling with a similar prefix, it becomes an "only child" node and is merged with its parent node, further optimizing space within the tree.
 
@@ -24,7 +24,7 @@ Transactions are hashed and stored as leaf nodes. As transactions are appended t
 
 MMRs are designed to efficiently append new transactions without restructuring the entire tree. When a new transaction occurs, its hash is appended to the MMR as a new leaf node, always added to the tree's rightmost part. As MMRs include a set of trees within, each tree hash root is called a “peak”. To calculate the final root of the tree, the peaks are hashed from the right, combining their hash values to construct the root hash. These peaks, representing the root hash values of individual trees within the MMR, also serve as reference points for subsets of transaction data. Note that due to the nature of the MMR, it is possible to have a sub-tree consisting of just one node. Below is a simplified illustration of an MMR with 3 sub-trees.
 
-![Alt Text](/assets/images/protocol/mmr.png)
+![Diagram of a Merkle Mountain Range with three peaks](/assets/images/protocol/mmr.png)
 
 Unlike Merkle Radix Trees where accounts and balances undergo constant updates, MMRs do not require direct data updates. In case a block is reverted, transactions are deleted from the transaction history, and new transactions are appended as new blocks come in.
 

rpc-client/playground.md

@@ -24,7 +24,7 @@ Staking enhances the security and decentralization of the Nimiq network. Validat
 
 You can choose not to stake and not earn any rewards. By not staking, you miss the opportunity to help maintain the network secure and decentralized.
 
-How long does it take to have my funds available after I un-stake?
+### How long does it take to have my funds available after I un-stake?
 
 Once you un-stake your funds, it usually takes between 12 hours to 4 days for them to become available. The exact time frame depends on your validator's status. In rare cases, validators can be "jailed" for up to 4 days, which may delay access to your funds.
 
@@ -70,7 +70,7 @@ Yes, you can change the Staking Pool or Validator to which you've staked your NI
 
 You can only stake with one validator per wallet address. To stake with multiple validators, you’ll need to create additional wallet addresses. Simply create a new wallet, transfer funds to it, and stake with your chosen validator under that new wallet address.
 
-What happens if the validator I’m staking with goes offline?
+### What happens if the validator I’m staking with goes offline?
 
 If the validator you're staking with goes offline, it will be deactivated and will not receive rewards during its inactivity. As a staker, this means you won't earn rewards from that validator while it's offline. However, you retain full control over your NIM and can choose to unstake and delegate to a different validator at any time. Keep in mind that unstaking involves a lock-up period before your funds become available for redelegation.
 
@@ -100,7 +100,7 @@ Currently, exchanges that support NIM do not offer direct staking functionality.
 
 ### How does the Nimiq Proof of Stake protocol ensure that all validators follow the rules?
 
-There is a system of rewards and punishments for validators. Validators are rewarded for validating transactions and producing blocks according to the consensus protocol, incentivizing good behavior. If a validator fails to follow the rules, they may face a punishment such as losing rewards or being temporarily “jailed” for up to 4 days, during which they cannot participate or earn rewards. This combination of rewards and punishments motivates validators to follow the rules. If you would like to learn more about validators, rewards, and punishments, you can refer to the [protocol documentation](https://www.nimiq.com/developers/learn/).
+There is a system of rewards and punishments for validators. Validators are rewarded for validating transactions and producing blocks according to the consensus protocol, incentivizing good behavior. If a validator fails to follow the rules, they may face a punishment such as losing rewards or being temporarily “jailed” for up to 4 days, during which they cannot participate or earn rewards. This combination of rewards and punishments motivates validators to follow the rules. If you would like to learn more about validators, rewards, and punishments, you can refer to the [protocol documentation](/protocol/).
 
 ### Can I lose my funds when staking?
 

validators/staking-faq.md

@@ -153,7 +153,7 @@ $$
 
 Where:
 - $c_j$: The number of blocks produced by the validator in batch $j$ of epoch $i$.
-- $N$: The total number of batches in the epoch (retrievable from the [policy](htts://github.com/nimiq/core-rs-albatross/blob/albatross/primitives/src/policy.rs)).
+- $N$: The total number of batches in the epoch (retrievable from the [policy](https://github.com/nimiq/core-rs-albatross/blob/albatross/primitives/src/policy.rs)).
 The number of blocks a validator produced can be retrieved from the blockchain via the rewarded inherent of each batch.
 
 ##### **Calculating $H_i$**

validators/validator-trustscore.md

@@ -17,7 +17,7 @@ integrations:
   - title: Nuxt
     icon: i-logos:nuxt-icon
     href: ./integrations/nuxt
-  - title: NextJS
+  - title: Next.js
     icon: i-logos:nextjs-icon
     href: ./integrations/NextJS
   - title: CommonJS

web-client/installation.md

@@ -1,3 +1,3 @@
 ## Contribute
 
-You can help us improve this guide by contributing to the Nimiq Web Client documentation on GitHub. Simply click the **Edit this page** button at the bottom of the page to suggest changes.
+You can help us improve this guide by contributing directly on GitHub. Simply click the **Edit this page** button at the bottom of the page to suggest changes.