chore: correct typos docs (#12600)

I reviewed the entire repository, no more typos found in docs. 
Hope this helps streamline the project!
Best regards,
Bilogweb3

---------

Co-authored-by: Aleksandr Logunov <alex.logunov@near.org>

chain/indexer/CHANGELOG.md

@@ -3,7 +3,7 @@
 ## 1.38.x
 
 * Make `build_streamer_message` public to allow custom indexer to reuse this function (e.g. build an indexer that streams optimistic block finalities, indexer that streams only blocks satisfying some condition, etc.)
-* Add local cache for delayed local receipts to avoid fetching blocks from the node everytime we need to find a delayed local receipt
+* Add local cache for delayed local receipts to avoid fetching blocks from the node every time we need to find a delayed local receipt
   * Add metric to watch how far back in the history we went to find a delayed local receipt when cache didn't work
 * Remove unnecessary `#[async_recursion]` from `build_streamer_message` function
 * Clean up some useless debug logs and add more useful ones

chain/telemetry/README.md

@@ -5,6 +5,6 @@ Telemetry is sent from all the nearcore binaries (that enabled it in the config.
 
 The data that is sent over is of type TelemetryInfo, and is signed with the server's key.
 
-It contains info about the code (release version), server (cpu, memory and network speeds), and chain (node_id, status, peer connected, block height etc).
+It contains info about the code (release version), server (cpu, memory and network speeds), and chain (node_id, status, peers connected, block height etc).
 
-TODO: add pointer to the code, that is used by the receiving server.
+TODO: add pointer to the code, that is used by the receiving server.

runtime/near-vm/README.md

@@ -6,7 +6,7 @@ changed, but the documentation is not up-to-date yet.
 The philosophy of Wasmer was to be very modular by design. It's
 composed of a set of crates. We can group them as follows:
 
-* `api` — The public Rust API exposes everything a user needs to use Wasmer programatically through
+* `api` — The public Rust API exposes everything a user needs to use Wasmer programmatically through
   the `wasmer` crate,
 * `cache` — The traits and types to cache compiled WebAssembly modules,
 * `cli` — The Wasmer CLI itself,
@@ -15,7 +15,7 @@ composed of a set of crates. We can group them as follows:
   * `compiler-singlepass` — A WebAssembly compiler based on our own compilation infrastructure;
     recommended for compilation-time speed performance.
 * `derive` — A set of procedural macros used inside Wasmer,
-* `engine` — The general abstraction for creating an engine, which is responsible of leading the
+* `engine` — The general abstraction for creating an engine, which is responsible for leading the
   compiling and running flow. Using the same compiler, the runtime performance will be
   approximately the same, however the way it stores and loads the executable code will differ:
   * `engine-universal` — stores the code in a custom file format, and loads it in memory,