fixed typo in architecture/staking

Author: LandauRaz

components/Starknet/modules/architecture-and-concepts/pages/staking.adoc

@@ -65,7 +65,7 @@ Starknet's staking protocol features two options for participation:
 
 * Staking directly as validators: Staking a minimum of 20,000 STRK and earning rewards by handling any responsibilities the protocol requires
 
-* Staking indirectly as delegators: Delegating STRKs to validators who alloe delegation and sharing in their rewards without handling any of their responsibilities
+* Staking indirectly as delegators: Delegating STRKs to validators who allow delegation and sharing in their rewards without handling any of their responsibilities
 +
 [NOTE]
 ====
@@ -74,8 +74,6 @@ Validators can choose whether to allow delegation or not.
 
 === Addresses
 
-// The operational address serves as the Validator's identifier within the network and is used for essential tasks such as block attestations and sequencing. Validators can utilize three distinct addresses, each dedicated to a specific utility: the staking address for controlling the stake, the rewards address for receiving rewards, and the operational address for performing ongoing operational work. This structure allows for a clear separation of responsibilities, enhancing security and efficiency. Disclaimer: In the first stage of staking on Starknet, the operational address will not yet be actively used, as Validators will primarily run full nodes.
-
 To reduce exposure to threats and enhance security, multiple addresses for defined for both validators and delegators:
 
 * Validator addresses: