diff --git a/src/sixth-basics.md b/src/sixth-basics.md
index 5360e2c..31738de 100644
--- a/src/sixth-basics.md
+++ b/src/sixth-basics.md
@@ -15,7 +15,7 @@ impl<T> LinkedList<T> {
 }
 ```
 
-PhantomData is a weird type with no fields so you just make one by, saying its type name. *shrug*
+PhantomData is a weird type with no fields, so you just make one by saying its type name. *shrug*
 
 ```rust ,ignore
 pub fn push_front(&mut self, elem: T) {
@@ -183,4 +183,4 @@ test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; fini
 
 Hooray, we're perfect!
 
-...Right?
\ No newline at end of file
+...Right?
diff --git a/src/sixth-variance.md b/src/sixth-variance.md
index 7b6aa17..fe17523 100644
--- a/src/sixth-variance.md
+++ b/src/sixth-variance.md
@@ -130,7 +130,7 @@ This is extremely annoying for Exactly Me as a person who has spent a lot of tim
 
 > Unlike `*mut T`, `NonNull<T>` was chosen to be covariant over `T`. This makes it possible to use `NonNull<T>` when building covariant types, but introduces the risk of unsoundness if used in a type that shouldn’t actually be covariant.
 
-But hey, it's interface is built around `*mut T`, what's the deal! Is it just magic?! Let's look:
+But hey, its interface is built around `*mut T`, what's the deal! Is it just magic?! Let's look:
 
 ```rust
 pub struct NonNull<T> {