minor fixes to staking

Author: LandauRaz

components/Starknet/modules/architecture/pages/staking.adoc

@@ -9,7 +9,7 @@ Jump into the discussion and help shape the future of Starknet's decentralizatio
 
 == Overview
 
-While Starknet is currently still centralized, it is xref:roadmap[gradually] moving towards employing a xref:protocol[staking protocol], handing over the responsibilities of producing, attesting, and proving blocks to validators. To facilitate this gradual implementation, the protocol's xref:architecture[architecture] is modular, ensuring maximum flexibility and ease of upgrades. However, anyone holding STRK in their wallets can already stake their tokens and earn rewards based on their level of participation by following xref:procedures[a few simple steps]. 
+While Starknet is currently still centralized, it is xref:roadmap[gradually] moving towards employing a xref:protocol[staking protocol], handing over the responsibilities of producing, attesting, and proving blocks to validators. To facilitate this gradual implementation, the protocol's architecture is divided into several xref:components[components], ensuring maximum flexibility and ease of upgrades. However, anyone holding STRK in their wallets can already stake their tokens and earn rewards based on their level of participation by following xref:procedures[a few simple steps]. 
 
 [TIP]
 ====
@@ -48,24 +48,28 @@ The following sections describe the details of Starknet's staking protocol. The
 | 1 STRK
 
 | Minting curve yearly inflation cap (stem:[C])
-| 1.6
-| 1.6
+| 1.6%
+| 1.6%
 
 | Withdrawal security lockup
 | 21 days
 | 5 minutes
 
 | Epoch length (stem:[E])
-| 120
-| 40
+| 120 blocks
+| 40 blocks
+
+| Epoch duration
+| 3600 seconds
+| 1200 seconds
 
 | Attestation window (stem:[W])	
-| 16
-| 16
+| 16 blocks
+| 16 blocks
 
 | Number of epochs used for latency (stem:[k])
-| 3600
-| 1200
+| 1 block
+| 1 block
 |===
 
 === Roles
@@ -216,13 +220,13 @@ The following latencies are set in place:
 
 Starting from its second phase, the staking protocol allows validators to increase their commission. To avoid an unexpected increase in commissions, validators must commit to a certain maximum commission stem:[M] and the last date (in epochs) that this commitment is relevant for. Until this date arrives, validators cannot increase their commission beyond stem:[M], but can freely change their commission in the range stem:[[0,M\]].
 
-== Architecture
+== Components
 
 The implementation of Starknet's staking protocol is divided into several contracts, summarized in the following figure:
 
 image::staking-architecture.png[]
 
-This modular architecture allows for targeted upgrades and improvements without affecting the entire system. Access control mechanisms are also in place to ensure that only authorized parties can make critical changes, further enhancing the security of the staking process. The following table details the key components of the architecture:
+This modular architecture allows for targeted upgrades and improvements without affecting the entire system. Access control mechanisms are also in place to ensure that only authorized parties can make critical changes, further enhancing the security of the staking process. The following table details the key components of the protocol:
 
 [cols="1,8"]
 |===