chore(docs): proofreading (solana-labs#35172)

* proofread

* proofread

docs/README.md

@@ -8,7 +8,7 @@ Static content delivery is handled using `vercel`.
 > documentation which is generalize to the Solana protocol as a whole, and apply
 > to all Solana validator implementations, are maintained within the
 > [`developer-content`](https://github.com/solana-foundation/developer-content/)
-> repo. Those "common docs" are manged by the Solana Foundation within their
+> repo. Those "common docs" are managed by the Solana Foundation within their
 > GitHub organization and are publicly accessible via
 > [solana.com/docs](https://solana.com/docs)
 

docs/src/proposals/comprehensive-compute-fees.md

@@ -35,7 +35,7 @@ A fee could be calculated based on:
    - Fixed rate per writable account
 3. Data byte cost
    - Fixed rate per byte of the sum of the length all a transactions instruction
-     datas
+     data
 4. Account sizes
    - Account sizes can't be known up-front but can account for a considerable
      amount of the load the transaction incurs on the network.  The payer will

docs/src/proposals/simple-payment-and-state-verification.md

@@ -117,7 +117,7 @@ https://github.com/solana-labs/solana/blob/b6bfed64cb159ee67bb6bdbaefc7f833bbed3
         let mut hash = hashv(&[
             // bank hash of the parent block
             self.parent_hash.as_ref(),
-            // hash of all the modifed accounts
+            // hash of all the modified accounts
             accounts_delta_hash.hash.as_ref(),
             // Number of signatures processed in this block
             &signature_count_buf,

metrics/README.md

@@ -41,8 +41,8 @@ The cluster telemetry dashboard shows the current state of the cluster:
 
 The fee market dashboard shows:
 
-1. Total Priorization Fees
-2. Block Min Priorization Fees
+1. Total Prioritization Fees
+2. Block Min Prioritization Fees
 3. Cost Tracker Stats
 
 ### Ping Results