@@ -97,7 +97,7 @@ A contract that every staker delegates to, bond or STX-only. It owns approval lo
 
 ## Signer set minimum
 
-`SIGNER_SET_MIN_USTX u50000000000` is 50,000 STX. It is an aggregate threshold on total uSTX delegated to a signer, counting both bond STX and STX-only STX, with no per-staker minimum. A signer crossing it is added to that cycle's signer set; falling below removes them.
+`SIGNER_SET_MIN_USTX u50000000000` is 50,000 STX. It is an aggregate threshold on total uSTX delegated to a signer, counting both bond STX and STX-only STX, with no per-staker minimum. A signer at or above it gets a yield distribution for that cycle; falling below stops it.
 
 ## Early exit
 
 
@@ -43,4 +43,4 @@ As you read through the Staking section, you may find stakers and signers mentio
 * Stakers are not signers\
   → signing is done by the key granted to the signer-manager contract they stake to, and running that signer is the manager operator's job
 * Every signer is backed by **staked STX**\
-  → to be in the signer set, a signer-manager must have at least 50,000 STX staked to it in aggregate, and its weight grows with the stake it represents
+  → a signer-manager with at least 50,000 STX staked to it in aggregate gets a yield distribution, and its weight grows with the stake it represents
@@ -18,7 +18,7 @@ description: >-
 #### The Big Picture
 
 * Signers validate and sign proposed Stacks blocks before they can join the chain.
-* The signer set is fixed each reward cycle: every signer-manager with at least 50,000 STX staked to it.
+* The signer set is fixed each reward cycle. Every signer-manager with at least 50,000 STX staked to it gets a yield distribution.
 * A signer's voting weight is proportional to the STX staked through it.
 * Accepting a block requires signatures carrying at least 70% of total signer weight.
 * Signing prevents forks and anchors Stacks history to Bitcoin.
@@ -44,7 +44,7 @@ This behavior prevents forks. If a miner builds a block atop a stale tip, signer
 
 Under PoX-5, a signer is a signer-manager contract bound to one signer key. The binding happens once: the signer-key holder signs a [SIP-018](https://github.com/stacksgov/sips/blob/main/sips/sip-018/sip-018-signed-structured-data.md) grant naming the manager, and the manager submits it through `grant-signer-key` and registers with `register-signer`. The key holder can revoke the grant at any time with `revoke-signer-grant`, which stops the manager accepting new stake while existing positions wind down.
 
-During each prepare phase, the last 100 Bitcoin blocks of a reward cycle, the signer set for the upcoming cycle is fixed: every registered signer-manager with at least 50,000 STX (`SIGNER_SET_MIN_USTX`) staked to it in aggregate. A signer's voting weight for that cycle is proportional to the total STX staked through it, counting the STX in STX-only stakes and the STX side of protocol bonds together. The BTC side of a bond carries no signing weight: signing weight, like governance weight, is a function of locked STX alone.
+During each prepare phase, the last 100 Bitcoin blocks of a reward cycle, the signer set for the upcoming cycle is fixed. Every registered signer-manager with at least 50,000 STX (`SIGNER_SET_MIN_USTX`) staked to it in aggregate gets a yield distribution. A signer's voting weight for that cycle is proportional to the total STX staked through it, counting the STX in STX-only stakes and the STX side of protocol bonds together. The BTC side of a bond carries no signing weight: signing weight, like governance weight, is a function of locked STX alone.
 
 The signer software detects from chain state whether its manager is in the upcoming cycle's signer set. Staking transactions are sent manually; everything the signer does with that information is automatic.
 
@@ -53,7 +53,7 @@ The signer software detects from chain state whether its manager is in the upcom
 <div data-with-frame="true"><figure><img src="https://2842511454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH74xqoobupBWwBsVMJhK%2Fuploads%2FS1L4pYrXDd1Ju74JhJkr%2Fstaking-and-signing.png?alt=media&#x26;token=3395cd31-c1fa-4f1a-97e0-f762285052c7" alt="Manual staking transactions feeding the reward phase, and the signer software acting automatically once its manager is in the signer set"><figcaption><p>Manual on the staker's side, automatic on the signer's</p></figcaption></figure></div>
 
 * Stakers are not signers. Signing is done by the key granted to the signer-manager they stake to, and running that signer is the manager operator's job.
-* Every signer is backed by staked STX. To be in the signer set, a manager must represent at least the 50,000 STX aggregate threshold, and its weight grows with the stake it represents.
+* Every signer is backed by staked STX. A manager with at least the 50,000 STX aggregate threshold gets a yield distribution, and its weight grows with the stake it represents.
 
 ***
 
 
@@ -20,7 +20,7 @@ description: >-
 * Staking locks STX to help secure the network and earn Bitcoin-denominated rewards.
 * It is part of Proof of Transfer (PoX): miners commit BTC, and that BTC pays stakers.
 * You stake by naming a signer-manager contract. The STX locks in your own account and never moves.
-* There is no per-staker minimum. A signer-manager needs 50,000 STX in aggregate to enter the signer set.
+* There is no per-staker minimum. A signer-manager with at least 50,000 STX staked to it in aggregate gets a yield distribution.
 * You can unstake an STX-only position at any time, and the STX unlocks at the start of the next cycle. Bond-paired STX is committed for the bond term.
 * Rewards arrive as sBTC by default. A native BTC payout can be elected through your signer-manager.
 
@@ -74,7 +74,7 @@ Who does what:
 * **The signer-manager contract** is bound to a signer key once, through a one-time [SIP-018](https://github.com/stacksgov/sips/blob/main/sips/sip-018/sip-018-signed-structured-data.md) grant, and receives your settled rewards for onward distribution. It may take a fee, which is contract-level logic rather than a protocol feature.
 * **The pox-5 contract** registers your position for every cycle you chose in the single staking transaction, and settles rewards per staker to the manager.
 
-A signer-manager enters the signer set once at least 50,000 STX (`SIGNER_SET_MIN_USTX`) is staked to it in aggregate. The threshold is fixed, and it applies to the manager rather than to you: your own stake can be any size.
+A signer-manager with at least 50,000 STX (`SIGNER_SET_MIN_USTX`) staked to it in aggregate gets a yield distribution. The threshold is fixed, and it applies to the manager rather than to you: your own stake can be any size.
 
 Running your own signer-manager and staking to someone else's are the same mechanism. A "solo" staker is someone running their own manager, which is operationally identical to offering a pool, because anyone can stake to that contract.
 
@@ -154,7 +154,7 @@ Staking happens in reward cycles of 2,100 Bitcoin blocks (roughly two weeks). Th
 
 <div data-with-frame="true"><figure><img src="https://2842511454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH74xqoobupBWwBsVMJhK%2Fuploads%2Ffz7B1xYNMnl5u5ICddZi%2Fstaking-cycles.png?alt=media&#x26;token=7aea0cf7-4dee-42af-a195-acf5c9aade65" alt="A reward cycle of 2,100 Bitcoin blocks ending in a 100-block prepare phase, with reward distributions every 1,050 blocks and unlocks at the cycle boundary"><figcaption><p>One reward cycle, block by block</p></figcaption></figure></div>
 
-* The prepare phase fixes the signer set for the upcoming cycle: every signer-manager with at least 50,000 STX staked to it in aggregate.
+* The prepare phase fixes the signer set for the upcoming cycle. Every signer-manager with at least 50,000 STX staked to it in aggregate gets a yield distribution.
 * During the reward phase, miners commit BTC to mine Stacks blocks, and that BTC funds staker rewards.
 * Rewards are credited once per distribution interval of 1,050 Bitcoin blocks (roughly one week), two intervals per reward cycle. The interval gates crediting only: your signer-manager can claim credited rewards at any time.
 * Unlocks happen at a cycle boundary: at the start of the cycle after your chosen duration ends, or after you unstake.