Merge branch 'main' into patch-2

0xSilkweave · web-flow · commit 4c2ac98430cf · 2024-12-19T14:01:09.000+01:00
diff --git a/pages/chain/get-started.mdx b/pages/chain/get-started.mdx
@@ -12,9 +12,9 @@ Momentarily, Beam operates as an Avalanche subnet. In this role, Beam is not jus
 
 In the developer preview mode, Beam employs a reputation-based consensus method termed Proof of Authority (PoA), enhanced with the Snowman protocol. This set-up entrusts a selected group of reputable authorities to authenticate transactions, thereby safeguarding the blockchain's integrity. The PoA model emphasizes the value of the validators' reputations, with these validators being handpicked based on their trustworthiness. This allows for a highly scalable system where blocks and transactions are verified by pre-approved participants acting as system moderators.
 
-## The Role of the Beam token ($BEAM)
+## The Role of the Beam token (BEAM)
 
-To interact with the Beam Network, $BEAM token is required. The $BEAM token is the native currency used within the Beam Network to pay for transactions. This not only includes transfers of value but also involves all interactions with smart contracts on the Beam Network, facilitating a seamless, immersive gaming experience.
+To interact with the Beam Network, BEAM token is required. The BEAM token is the native currency used within the Beam Network to pay for transactions. This not only includes transfers of value but also involves all interactions with smart contracts on the Beam Network, facilitating a seamless, immersive gaming experience.
 
 ## Building on Beam: Empowering Innovation
 
diff --git a/pages/chain/get-started/gas.mdx b/pages/chain/get-started/gas.mdx
@@ -1,5 +1,5 @@
 ---
-description: "Discover the role of $BEAM token as the gas token for the Beam Network, covering its utilization, distribution, and fee configuration."
+description: "Discover the role of BEAM token as the gas token for the Beam Network, covering its utilization, distribution, and fee configuration."
 ---
 
 import { Callout } from "nextra/components";
diff --git a/pages/chain/nodes/delegation.mdx b/pages/chain/nodes/delegation.mdx
@@ -13,7 +13,7 @@ As a delegator, you can participate in staking on Beam without operating your ow
   more](/chain/nodes/validator#developer-preview-mode)
 </Callout>
 
-- To delegate, you only require BEAM.
-- The minimum delegation amount is TBD (to be determined) BEAM.
+- To delegate, you only require $BEAM.
+- The minimum delegation amount of $BEAM will be announced soon.
 - Select a validator to whom you wish to delegate your stake.
 - Rewards are distributed to you by the chosen validator.
diff --git a/pages/chain/nodes/requirements.mdx b/pages/chain/nodes/requirements.mdx
@@ -19,15 +19,15 @@ Avalanche is an incredibly lightweight protocol, so nodes can run on commodity h
 The node should be configured to accept incoming TCP/IP connections on port `9651`.
 
 <Callout type="info">
-  Hardware requirements may scale based on the amount of $BEAM staked on the node
-  and network activity. Nodes with significant stakes (500k+ $BEAM) may need
+  Hardware requirements may scale based on the amount of BEAM staked on the node
+  and network activity. Nodes with significant stakes (500k+ BEAM) may need
   hardware that exceeds the listed specifications and may also use more
   bandwidth.
 </Callout>
 
 ## Stake Requirements
 
-In addition to the hardware, running a validator on Beam requires staking a minimum amount of $BEAM tokens. Specifically, you'll need at least 20000 $BEAM.
+In addition to the hardware, running a validator on Beam requires staking a minimum amount of BEAM tokens. Specifically, you'll need at least 20000 BEAM.
 
 ## Next Steps
 
diff --git a/pages/chain/nodes/validate-delegate.mdx b/pages/chain/nodes/validate-delegate.mdx
@@ -9,5 +9,5 @@ The core distinctions between validators and delegators are outlined below:
 |                      | Validator                                                                                                     | Delegator                                                                                                                      |
 | :------------------- | :------------------------------------------------------------------------------------------------------------ | :----------------------------------------------------------------------------------------------------------------------------- |
 | Responsibilities     | Validators actively **run a node**, validate transactions, and actively participate in securing the network.  | Delegators **do not run a node** themselves but entrust their tokens to a validator to participate on their behalf.            |
-| Stake Requirement    | Validators have a **higher minimum stake** requirement and, additionally, they have to **stake AVAX tokens**. | The minimum stake **requirement** for delegators is **lower** and only requires BEAM tokens.                                   |
+| Stake Requirement    | Validators have a **higher minimum stake** requirement and, additionally, they have to **stake $AVAX tokens**. | The minimum stake **requirement** for delegators is **lower** and only requires $BEAM tokens.                                   |
 | Rewards Distribution | Validators **receive rewards directly** for their validation efforts.                                         | Delegators **receive rewards indirectly** through the validator they delegate to, sharing a portion of the validator's reward. |
diff --git a/pages/chain/nodes/validator.mdx b/pages/chain/nodes/validator.mdx
@@ -11,7 +11,7 @@ import { Callout } from "nextra/components";
 
 <Callout type="warning" emoji="⚠️">
   In the developer preview mode, Beam operates under a reputation-based
-  consensus method termed Proof of Authority (PoA). Later this year, we plan to
+  consensus method termed Proof of Authority (PoA). Early next year (Q1), we plan to
   switch the consensus method from Proof of Authority (PoA) to Proof of Stake
   (PoS). This step is irreversible and hasn't been done on AVAX before, hence
   our deliberate approach. You can read more about some of the considerations in
diff --git a/pages/chain/resources.mdx b/pages/chain/resources.mdx
@@ -8,7 +8,7 @@ import { Cards } from 'nextra/components'
  
 </Cards>
 
-- [Beam Testnet Faucet](https://core.app/tools/testnet-faucet/?subnet=beam&token=beam) ([Alternative Faucet](https://faucet.onbeam.com/)): A testnet faucet for obtaining $BEAM for testing purposes on the Beam Testnet.
+- [Beam Testnet Faucet](https://core.app/tools/testnet-faucet/?subnet=beam&token=beam) ([Alternative Faucet](https://faucet.onbeam.com/)): A testnet faucet for obtaining BEAM for testing purposes on the Beam Testnet.
 - [Verify Contract](https://subnets.avax.network/tools/verify-contract): A tool for verifying smart contracts on the official block explorer.
 - [Avatools](https://avatools.io): Offers helpful tools for interacting with the Beam Subnet, such as converting hex to cb58.
 - [buildonbeam community @ Reddit](https://www.reddit.com/r/buildonbeam/): A place where devs can share ideas, programming knowledge, learn & help others while building on Beam.
