diff --git a/CMakeLists.txt b/CMakeLists.txt
index 3a16cdcc1fa2fabdcd8a8ec61ad5b9c005aecdba..85add0ba1e5f05cea2af0386b4a1bae3cfd5a93c 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -49,7 +49,7 @@ set(UNITY_EXTENSION_FIXTURE_ENABLED $<BOOL:${UNITY_EXTENSION_FIXTURE}>)
 set(UNITY_EXTENSION_MEMORY_ENABLED $<OR:${UNITY_EXTENSION_FIXTURE_ENABLED},$<BOOL:${UNITY_EXTENSION_MEMORY}>>)
 
 if(${UNITY_EXTENSION_FIXTURE})
-    message(STATUS "Unity: Bulding with the fixture extension.")
+    message(STATUS "Unity: Building with the fixture extension.")
 endif()
 
 if(${UNITY_EXTENSION_MEMORY})
diff --git a/README.md b/README.md
index cab2de39fa7325249521375a7f1989f2e7af55b3..cdfb3bb98909d169878da1904737228e98ceab13 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ __Copyright (c) 2007 - 2021 Unity Project by Mike Karlesky, Mark VanderVoord, an
 Welcome to the Unity Test Project, one of the main projects of ThrowTheSwitch.org. Unity Test is a 
 unit testing framework built for C, with a focus on working with embedded toolchains. 
 
-This project is made to test code targetting microcontrollers big and small. The core project is a 
+This project is made to test code targeting microcontrollers big and small. The core project is a 
 single C file and a pair of headers, allowing it to the added to your existing build setup without 
 too much headache. You may use any compiler you wish, and may use most existing build systems
 including make, cmake, etc. If you'd like to leave the hard work to us, you might be interested
diff --git a/docs/UnityConfigurationGuide.md b/docs/UnityConfigurationGuide.md
index de691fdf28495529c51d4c18f213541d0898a9dc..6514fcd4d31572643c05af89d4710f4ec32b4d93 100644
--- a/docs/UnityConfigurationGuide.md
+++ b/docs/UnityConfigurationGuide.md
@@ -446,7 +446,7 @@ _Example:_
 These options  give you control of the `TEST_ASSERT_EQUAL` and the
 `TEST_ASSERT_NOT_EQUAL` shorthand assertions. Historically, Unity treated the
 former as an alias for an integer comparison. It treated the latter as a direct
-comparison using `!=`. This assymetry was confusing, but there was much
+comparison using `!=`. This asymmetry was confusing, but there was much
 disagreement as to how best to treat this pair of assertions. These four options
 will allow you to specify how Unity will treat these assertions.
 
diff --git a/extras/eclipse/error_parsers.txt b/extras/eclipse/error_parsers.txt
index 94e34ff385f92fb7999ac1bc0356d2daac97d841..dfe8b8365b34a1cbd2d15e55c03eb8c693277562 100644
--- a/extras/eclipse/error_parsers.txt
+++ b/extras/eclipse/error_parsers.txt
@@ -2,7 +2,7 @@ Eclipse error parsers
 =====================
 
 These are a godsend for extracting  & quickly navigating to
-warnings & error messages from console output. Unforunately
+warnings & error messages from console output.Unfortunately
 I don't know how to write an Eclipse plugin so you'll have
 to add them manually.
 
diff --git a/src/unity.c b/src/unity.c
index be3528fadd646ba91c3470d26bdd95c64e748376..e83a9dcfcdf8207452ea6b371e54fc81423de4f3 100644
--- a/src/unity.c
+++ b/src/unity.c
@@ -13,7 +13,7 @@
 #define PROGMEM
 #endif
 
-/* If omitted from header, declare overrideable prototypes here so they're ready for use */
+/* If omitted from header, declare overridable prototypes here so they're ready for use */
 #ifdef UNITY_OMIT_OUTPUT_CHAR_HEADER_DECLARATION
 void UNITY_OUTPUT_CHAR(int);
 #endif
diff --git a/test/rakefile b/test/rakefile
index e5f3b748f6dcb3a360075196c2e75cfdf7cffbcf..9bbde93fac3bb63c806c038028950be5a149f3fc 100644
--- a/test/rakefile
+++ b/test/rakefile
@@ -26,7 +26,7 @@ task :prepare_for_tests => TEMP_DIRS
 
 include RakefileHelpers
 
-# Load proper GCC as defult configuration
+# Load proper GCC as default configuration
 DEFAULT_CONFIG_FILE = 'gcc_auto_stdint.yml'
 configure_toolchain(DEFAULT_CONFIG_FILE)