diff --git a/Documentation/developer/getting_started.rst b/Documentation/developer/getting_started.rst
index b0a231660..c13cae026 100644
--- a/Documentation/developer/getting_started.rst
+++ b/Documentation/developer/getting_started.rst
@@ -1,5 +1,5 @@
 
-Getting Started as a Contributer
+Getting Started as a Contributor
 ================================
 
 Icarus Verilog development is centered around the github repository at
@@ -218,7 +218,7 @@ first push the branch up to github:
 Then go to github.com to create your pull request. `Create your pull request
 against the "master" branch of the upstream repository
 <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork>`_,
-or the version branch that you are working on. Your pull reuqest will be run
+or the version branch that you are working on. Your pull request will be run
 through continuous integration, and reviewed by one of the main
 authors. Feedback may be offered to your PR, and once accepted, an approved
 individual will merge it for you. Then you are done.
diff --git a/Documentation/developer/version_stamps.rst b/Documentation/developer/version_stamps.rst
index c748113f7..ba0ace79d 100644
--- a/Documentation/developer/version_stamps.rst
+++ b/Documentation/developer/version_stamps.rst
@@ -9,7 +9,7 @@ These are the only files that have version information in them:
 * verilog.spec      -- Used to stamp RPM packages
 
 When versions are changed, the above files need to be edited to account for
-the new version information. The following used to have verion information in
+the new version information. The following used to have version information in
 them, but now their version information is generated:
 
 The version_tag.h file is generated from git tag information using