diff --git a/docs/releaseprocedures.rst b/docs/releaseprocedures.rst
index 520983fa8a1f0da46f0c85b9d0608a3665ed9bcb..a45070e423b4b0a2aba6b7a983d0c559f20eb290 100644
--- a/docs/releaseprocedures.rst
+++ b/docs/releaseprocedures.rst
@@ -173,7 +173,7 @@ When releasing a new minor/major version, procedure is as follows:
 15. Commit the changes::
 
       git add docs/
-      git commits -m "$ISSUE: Preparing for release $NEW_VERSION."
+      git commit -m "$ISSUE: Preparing for release $NEW_VERSION."
 
 16. Create annotated and signed Git tag::
 
@@ -199,7 +199,7 @@ When releasing a new minor/major version, procedure is as follows:
 20. Commit the changes::
 
       git add docs/
-      git commits -m "$ISSUE: Bumping version to ${NEW_VERSION%.*}-dev (switching back to development)."
+      git commit -m "$ISSUE: Bumping version to ${NEW_VERSION%.*}-dev (switching back to development)."
 
 21. Verify GnuPG signatures::
 
@@ -239,7 +239,7 @@ When releasing a new minor/major version, procedure is as follows:
 28. Commit the changes::
 
       git add docs/
-      git commits -m "$ISSUE: Creating maintenance branch for release $NEW_VERSION."
+      git commit -m "$ISSUE: Creating maintenance branch for release $NEW_VERSION."
 
 29. Push the maintenance branch::
 
@@ -342,7 +342,7 @@ When releasing a new patch release, procedure is as follows:
 16. Commit the changes::
 
       git add docs/
-      git commits -m "$ISSUE: Preparing for release $NEW_VERSION."
+      git commit -m "$ISSUE: Preparing for release $NEW_VERSION."
 
 17. Create annotated and signed Git tag::
 
@@ -368,7 +368,7 @@ When releasing a new patch release, procedure is as follows:
 21. Commit the changes::
 
       git add docs/
-      git commits -m "$ISSUE: Bumping version to ${NEW_VERSION%.*}-maint (switching back to maintenance)."
+      git commit -m "$ISSUE: Bumping version to ${NEW_VERSION%.*}-maint (switching back to maintenance)."
 
 22. Verify GnuPG signatures::