chore: fix some typos

console-api/README.md

@@ -37,7 +37,7 @@ system consists of two primary components:
 * _instrumentation_, embedded in the application, which collects data from the
   async runtime and exposes it over the console's wire format
 * _consumers_, such as the [`tokio-console`] command-line application, which
-  connect to the instrumented application, recieve telemetry data, and display
+  connect to the instrumented application, receive telemetry data, and display
   it to the user
 
 The wire format [protobuf] bindings in this crate are used by both the

console-subscriber/README.md

@@ -34,7 +34,7 @@ system consists of two primary components:
 * _instrumentation_, embedded in the application, which collects data from the
   async runtime and exposes it over the console's [wire format]
 * _consumers_, such as the [`tokio-console`] command-line application, which
-  connect to the instrumented application, recieve telemetry data, and display
+  connect to the instrumented application, receive telemetry data, and display
   it to the user
 
 This crate implements the instrumentation-side interface using data

console-subscriber/src/record.rs

@@ -95,7 +95,7 @@ fn record_io(file: File, rx: Receiver<Event>) -> io::Result<()> {
         },
     )?;
 
-    // wait to recieve an event...
+    // wait to receive an event...
     while let Ok(event) = rx.recv() {
         // TODO: what to do if file error?
         write(&mut file, &event)?;

tokio-console/README.md

@@ -35,7 +35,7 @@ system consists of two primary components:
   collects data from the async runtime and exposes it over the console's wire
   format
 * 🛰️ _consumers_, which connect to the instrumented application,
-  recieve telemetry data, and display it to the user
+  receive telemetry data, and display it to the user
 
 This crate is the primary consumer of `tokio-console` telemetry, a command-line
 application that provides an interactive debugging interface.