diff --git a/docs/Debug-shim-guide.md b/docs/Debug-shim-guide.md
index bcbf372cb3..b1528c816a 100644
--- a/docs/Debug-shim-guide.md
+++ b/docs/Debug-shim-guide.md
@@ -5,7 +5,7 @@ process that is run by the runtime manager (containerd/CRI-O), and controlled by
 sending gRPC requests to it.
 Starting the shim with a debugger then just gives you a process that waits for
 commands on its socket, and if the runtime manager doesn't start it, it won't
-send request to it.
+send requests to it.
 
 A first method is to attach a debugger to the process that was started by the
 runtime manager.
@@ -17,7 +17,7 @@ and the actual shim binary. This allows to start the shim with a debugger, and
 wait for a client debugger connection before execution, allowing debugging of the
 kata runtime from the very beginning.
 
-## Prerequisite
+## Prerequisites
 
 At the time of writing, a debugger was used only with the go shim, but a similar
 process should be doable with runtime-rs. This documentation will be enhanced
diff --git a/docs/Developer-Guide.md b/docs/Developer-Guide.md
index 65f99f0105..2be4e851c2 100644
--- a/docs/Developer-Guide.md
+++ b/docs/Developer-Guide.md
@@ -27,7 +27,7 @@ to build the Kata Containers components from source.
 
 > **Note:**
 >
-> If you decide to build from sources, you should be aware of the
+> If you decide to build from source, you should be aware of the
 > implications of using an unpackaged system which will not be automatically
 > updated as new [releases](https://github.com/kata-containers/kata-containers/releases) are made available.