Fix some typos

README.md

@@ -20,7 +20,6 @@ solana tpu ([details](quic-forward-proxy/README.md)).
 ### Confirmation strategies
 
 1) Subscribe to new blocks using websockets (deprecated)
-(depricated) 
 2) Polling blocks over RPC.(Current) 
 3) Subscribe blocks over gRPC.
 (Current) 

benches/bench_tx_send_and_confirm.ts

@@ -76,7 +76,7 @@ export async function main() {
 }
 
 main().then(x => {
-    console.log('finished sucessfully')
+    console.log('finished successfully')
 }).catch(e => {
     console.log('caught an error : ' + e)
 })

benches/bench_txs_send.ts

@@ -89,7 +89,7 @@ const skip_confirmations = get_postional_arg(5, false) === "true";
             }
 
         }
-        console.log("sucesses : " + successes)
+        console.log("successes : " + successes)
         console.log("failures : " + failures)
         //console.log("time taken to send : " + time_taken_to_send)
     }

cluster-endpoints/src/rpc_polling/poll_blocks.rs

@@ -126,7 +126,7 @@ pub fn poll_block(
 
     //slot poller
     let slot_poller = tokio::spawn(async move {
-        log::info!("block listner started");
+        log::info!("block listener started");
         let current_slot = rpc_client
             .get_slot()
             .await

cluster-endpoints/src/rpc_polling/poll_slots.rs

@@ -90,7 +90,7 @@ pub fn poll_slots(
                                 processed_slot: current_slot,
                                 estimated_processed_slot: estimated_slot,
                             })
-                            .context("Connot send slot notification")?;
+                            .context("Cannot send slot notification")?;
                     }
                 }
             }

quic-forward-proxy/README.md

@@ -95,7 +95,7 @@ Implementation Details
   * _proxy_ will maintain multiple quic connection per TPU according to the Solana validator quic policy
   * _proxy_ will use lightweight quic streams to send the transactions
 * inbound traffic (from Lite RPC)
-  * client-proxy-communcation is done via QUIC using a custom wire format
+  * client-proxy-communication is done via QUIC using a custom wire format
   * _proxy_ supports only quic ATM but that could be extended to support other protocols
   * _proxy_ should perform client authentication by TLS (see [issue](https://github.com/blockworks-foundation/lite-rpc/issues/167))
 * _proxy_ uses a single queue (channel) for buffering the transactions from any inbound connection

quic-forward-proxy/src/quinn_auto_reconnect.rs

@@ -29,7 +29,7 @@ enum ConnectionState {
 }
 
 pub struct AutoReconnect {
-    // endoint should be configures with keep-alive and idle timeout
+    // endpoint should be configures with keep-alive and idle timeout
     endpoint: Endpoint,
     current: RwLock<ConnectionState>,
     pub target_address: SocketAddr,