diff --git a/docs/07-scheduler.md b/docs/07-scheduler.md
index 3085ba6..e0eebe5 100644
--- a/docs/07-scheduler.md
+++ b/docs/07-scheduler.md
@@ -243,8 +243,8 @@ Output:
 [{"effect":"NoSchedule","key":"node.kubernetes.io/not-ready"}]
 ```
 
-As you can see, our node has taint with efect no schedule. The reason of this????
-But lets fix this.
+As you can see, our node has taint with efect no schedule.
+Lets fix this.
 ```bash
 kubectl taint nodes $(hostname -a) node.kubernetes.io/not-ready:NoSchedule-
 ```
@@ -262,7 +262,7 @@ hello-world   1/1     Running   0          29m   10.240.1.3   example-server   <
 
 As you can see out pod is in running state, means that scheduler works as expected.
 
-Now we need to clean-up our wirkspace
+Now we need to clean-up our workspace
 ```bash
 kubectl delete -f pod.yaml
 ```
diff --git a/docs/img/07_cluster_architecture_scheduler.png b/docs/img/07_cluster_architecture_scheduler.png
index e475961..74471d0 100644
Binary files a/docs/img/07_cluster_architecture_scheduler.png and b/docs/img/07_cluster_architecture_scheduler.png differ
diff --git a/docs/img/08_cluster_architecture_controller_manager.png b/docs/img/08_cluster_architecture_controller_manager.png
index 84bd1c9..86d4263 100644
Binary files a/docs/img/08_cluster_architecture_controller_manager.png and b/docs/img/08_cluster_architecture_controller_manager.png differ