diff --git a/ways_of_working/processes/reviews.md b/ways_of_working/processes/reviews.md
index 9517498..8ad70d1 100644
--- a/ways_of_working/processes/reviews.md
+++ b/ways_of_working/processes/reviews.md
@@ -182,4 +182,4 @@ As an example, check out the [TB-TT CI](https://github.com/wp-media/TB-TT/blob/d
             exit 1
           fi
         shell: bash
-```
\ No newline at end of file
+```
diff --git a/ways_of_working/processes/version_control.md b/ways_of_working/processes/version_control.md
index d954976..541f998 100644
--- a/ways_of_working/processes/version_control.md
+++ b/ways_of_working/processes/version_control.md
@@ -93,4 +93,4 @@ Every release must have a corresponding release note in our corresponding Notion
 To be useful and readable, releases notes must:
 - Reference the corresponding version number, product and date;
 - List all technical changes with a link to the corresponding GitHub issue or PR (for automated release notes, the automated release description from GitHub should be leveraged);
-- Explain the impact and changes experienced from a user perspective.
\ No newline at end of file
+- Explain the impact and changes experienced from a user perspective.
diff --git a/ways_of_working/team/missions_and_purposes_of_the_engineering_team.md b/ways_of_working/team/missions_and_purposes_of_the_engineering_team.md
index 9ee93fe..3f42fc8 100644
--- a/ways_of_working/team/missions_and_purposes_of_the_engineering_team.md
+++ b/ways_of_working/team/missions_and_purposes_of_the_engineering_team.md
@@ -3,7 +3,7 @@ notion_page: https://www.notion.so/wpmedia/Missions-Purposes-of-the-Engineering-
 title: Missions & Purposes of the Engineering team
 ---
 
-# Missions & Purposes of the Engineering teams
+# Missions & Purposes of the Engineering team
 
 ## Engineering team