diff --git a/CODE_REVIEW_GUIDELINES.md b/CODE_REVIEW_GUIDELINES.md
index 502a2bb..d6175cf 100644
--- a/CODE_REVIEW_GUIDELINES.md
+++ b/CODE_REVIEW_GUIDELINES.md
@@ -1,6 +1,6 @@
 # Overall:
 
-- Does the contribution referece an existing Issue?
+- Does the contribution reference an existing Issue?
 - Are the requirements well defined?
 
 
diff --git a/SWIFTLINT.md b/SWIFTLINT.md
index 584de03..cc4c732 100644
--- a/SWIFTLINT.md
+++ b/SWIFTLINT.md
@@ -2,7 +2,7 @@
 
 The SwiftLint configuration on this repo is based on the great work of the raywenderlich.com folks [The Official raywenderlich.com Swift Style Guide](https://github.com/raywenderlich/swift-style-guide).
 
-The purpose of this guide is to provide a base format for our Swift codebase. This guide describes what are the rules enforced by our swift lint rules and should beused when contributing or reviewing code. 
+The purpose of this guide is to provide a base format for our Swift codebase. This guide describes what are the rules enforced by our swift lint rules and should be used when contributing or reviewing code. 
 
 These guides use SwiftLint as a standard. You can learn more about SwiftLint by visiting its [official documentation page](https://github.com/realm/SwiftLint).
 
diff --git a/docs/CODING_GUIDELINES.md b/docs/CODING_GUIDELINES.md
index af259dd..e1e66b1 100644
--- a/docs/CODING_GUIDELINES.md
+++ b/docs/CODING_GUIDELINES.md
@@ -9,7 +9,7 @@ When creating new files, please use the provided templates when applicable. You
 
 # Type definition structure
 
-When defining new type or modificating an existing one, please follow the convention below:
+When defining new type or modifying an existing one, please follow the convention below:
 
 ````
 Type