spelling, minor fixes

Author: cfsamson

ch02/aa-os-threads/Cargo.toml renamed to ch02/a-os-threads/Cargo.toml

@@ -1,5 +1,5 @@
 [package]
-name = "aa-os-threads"
+name = "a-os-threads"
 version = "0.1.0"
 edition = "2021"
 

ch02/aa-os-threads/src/main.rs renamed to ch02/a-os-threads/src/main.rs

@@ -1,5 +1,5 @@
 [package]
-name = "aa-raw-syscall"
+name = "a-raw-syscall"
 version = "0.1.0"
 edition = "2021"
 

ch03/a-raw-syscall/Cargo.toml

@@ -1,5 +1,5 @@
 [package]
-name = "ab-normal-syscall"
+name = "b-normal-syscall"
 version = "0.1.0"
 edition = "2021"
 

ch03/b-normal-syscall/Cargo.toml

@@ -1,5 +1,5 @@
 [package]
-name = "b-epoll"
+name = "a-epoll"
 version = "0.1.0"
 edition = "2021"
 

ch03/b-normal-syscall/README.md

@@ -7,22 +7,21 @@ You can run the example by simply writing `cargo run`
 
 ## Note
 
-There is one downside of having a local server on the same machine to mimmic
+There is one downside of having a local server on the same machine to mimic
 real life behavior. The network will never be slow, and packages will never
 need to be resent. Latency is not a problem either.
 
 For example, encountering an actual `io::WouldBlock` error when reading
 from a `TcpStream` that's reported as ready is very hard, but if you
-want to test it out I manage to reliably get that error by simply transferring
+want to test it out I managed to reliably get that error by simply transferring
 so much data that the OS needs to do extra work to handle it.
 
 You can reproduce it if you make som minor changes to the delayserver code
-as well as the program in main.rs as outlined below. Simply copy and replace
-the appropirate functions with these will do it.
-
+as well as the program in `main.rs`` as outlined below. Simply copy and replace
+the appropriate functions with these will do it.
 
 First, change the `delay` function on the delayserver to return huge amount of fill data
-(enough to force a `WouldBlock` error on the reciever):
+(enough to force a `WouldBlock` error on the receiver):
 
 ```rust
 #[get("/{delay}/{message}")]
@@ -71,4 +70,3 @@ fn handle_events(events: &[Event], streams: &mut [TcpStream]) -> Result<usize> {
     Ok(handled_events)
 }
 ```
-

ch04/a-epoll/Cargo.toml

@@ -43,4 +43,4 @@ cargo run
 The implementation is wildly unsafe and only focuses on getting a working example running.
 The focus is on explaining the concepts as simply as possible and not best practices.
 
-While a fiber implementation like this will never be possible to do fully in safe Rust, there are many ways to make it safer, and it's a good readers excercise to do so. Just beware that you might have to change the API somewhat to make it safer since mutating global statics using raw pointers (and any mutating of what Rust assumes are exclusive borrows using the tricks we do in the `call` function) are a shure way to get undefined behavior and this example is no exception to that.
+While a fiber implementation like this will never be possible to do fully in safe Rust, there are many ways to make it safer, and it's a good readers exercise to do so. Just beware that you might have to change the API somewhat to make it safer since mutating global statics using raw pointers (and any mutating of what Rust assumes are exclusive borrows using the tricks we do in the `call` function) are a sure way to get undefined behavior and this example is no exception to that.

ch04/a-epoll/README.md

@@ -1,5 +1,5 @@
 [package]
-name = "b-reactor-executor"
+name = "a-coroutine"
 version = "0.1.0"
 edition = "2021"
 

ch05/d-fibers-closure/README.md

@@ -1,5 +1,5 @@
 [package]
-name = "b-reactor-executor"
+name = "c-reactor-executor"
 version = "0.1.0"
 edition = "2021"