suggested readme changes

Author: michaelsutton

README.md

@@ -9,9 +9,13 @@ Your feedback, contributions, and issue reports will be integral to evolving thi
 
 The default branch of this repository is `master` and new contributions are constantly merged into it. For a stable branch corresponding to the latest stable release please pull and compile the `stable` branch. 
 
-## The Crescendo Hardfork
+## The Crescendo Hardfork  
+
+The Crescendo Hardfork, which will transition the network to 10 BPS, is scheduled to activate on mainnet at DAA Score **110,165,000**, projected to occur on **May 5, 2025, at approximately 15:00 UTC**. Note that 24 hours before activation, nodes will connect only to upgraded peers which are using the new P2P protocol version 7.  
+
+You are encouraged to verify your client software against this mainnet version ahead of or after the hardfork. For a more controlled environment, consider using **Testnet 10**, where the Crescendo changes are already active. Refer to the [Crescendo guide](docs/crescendo-guide.md) for detailed instructions.
+
 
-The Crescendo Hardfork which will transition the network to 10BPS is scheduled to occur in mainnet on `2025-05-05 1500 UTC` at DAA Score `110,165,000`. You can participate in testing the hardfork on mainnet (prior to activation) or on the already activated testnet by following [this node specification and testing guide](docs/crescendo-guide.md).
 
 ## Installation
   <details>

docs/crescendo-guide.md

@@ -16,7 +16,7 @@ Kaspa is about to take a significant leap with the **Crescendo Hardfork**, as de
   - 512 GB SSD  
   - Higher network bandwidth for robust peer support
 
-While the minimum specs suffice to sync and maintain a TN10 node with the accelerated 10 bps, increasing CPU cores, RAM, storage, and bandwidth allows your node to serve as a stronger focal point on the network. This leads to faster initial block download (IBD) for peers syncing from your node and provides more leeway for future storage growth and optimization.
+While the minimum specs suffice to sync and maintain a 10 bps node, increasing CPU cores, RAM, storage, and bandwidth allows your node to serve as a stronger focal point on the network. This leads to faster initial block download (IBD) for peers syncing from your node and provides more leeway for future storage growth and optimization.
 
 If you are a pool operator, it is _strongly recommended_ that you pick specs that are closer to the preferred specifications above.
 
@@ -58,7 +58,7 @@ Crescendo introduces a new field in transactions, `mass`, which needs to be pres
 
 Ensure your pool/stratum is updated to preserve this field in the transactions by updating your GRPC proto files. Then, ensure that your pool software properly sends back the `mass` for each transaction in the block.
 
-### Updating your Pool/Stratum to work in Cresendo
+### Updating your Pool/Stratum to work in Crescendo
 
 #### Updating GRPC proto