diff --git a/libcontainer/nsenter/README.md b/libcontainer/nsenter/README.md
index 32a2fc322..823323e97 100644
--- a/libcontainer/nsenter/README.md
+++ b/libcontainer/nsenter/README.md
@@ -18,7 +18,7 @@ which will give the process of the container that should be joined. Namespaces f
 be found from `/proc/[pid]/ns` and set by `setns` syscall.
 
 And then get the pipe number from `_LIBCONTAINER_INITPIPE`, error message could
-be transfered through it. If tty is added, `_LIBCONTAINER_CONSOLE_PATH` will 
+be transferred through it. If tty is added, `_LIBCONTAINER_CONSOLE_PATH` will 
 have value and start a console for output.
 
 Finally, `nsexec()` will clone a child process , exit the parent process and let 
diff --git a/man/runc-spec.8.md b/man/runc-spec.8.md
index b2b2915d5..482c8c3a1 100644
--- a/man/runc-spec.8.md
+++ b/man/runc-spec.8.md
@@ -38,7 +38,7 @@ must be unique on your host.
 An alternative for generating a customized spec config is to use "ocitools", the
 sub-command "ocitools generate" has lots of options that can be used to do any
 customizations as you want, see [ocitools](https://github.com/opencontainers/ocitools)
-to get more infomation.
+to get more information.
 
 When starting a container through runc, runc needs root privilege. If not
 already running as root, you can use sudo to give runc root privilege. For
diff --git a/spec.go b/spec.go
index 0ecf75f09..d4da3a553 100644
--- a/spec.go
+++ b/spec.go
@@ -51,7 +51,7 @@ must be unique on your host.
 An alternative for generating a customized spec config is to use "ocitools", the
 sub-command "ocitools generate" has lots of options that can be used to do any
 customizations as you want, see [ocitools](https://github.com/opencontainers/ocitools)
-to get more infomation.
+to get more information.
 
 When starting a container through runc, runc needs root privilege. If not
 already running as root, you can use sudo to give runc root privilege. For