diff --git a/src/courses/profile-dev-test/07.md b/src/courses/profile-dev-test/07.md
index b68dbfd4b..dcedf2b03 100644
--- a/src/courses/profile-dev-test/07.md
+++ b/src/courses/profile-dev-test/07.md
@@ -81,7 +81,7 @@ The choice between micro and massive PRs can significantly impact the workflows
 
 - **Patch and Release Updates:** These updates typically involve minor changes or additions, which can be easily managed with either micro or massive PRs. The choice depends on your team's preference for review speed and context switching.
 
-- **Major Version or Large Jump Release Updates:** These updates require a thorough review of every single control and requirement. They also necessitate extensive testing, both automated (via the CI/CD testing matrix) and manual. In this scenario, the overhead of managing multiple micro or mini PRs can be substantial. However, the benefit is that it allows for more granitary control and review of changes. It's also easier to isolate and fix issues that arise during testing.
+- **Major Version or Large Jump Release Updates:** These updates require a thorough review of every single control and requirement. They also necessitate extensive testing, both automated (via the CI/CD testing matrix) and manual. In this scenario, the overhead of managing multiple micro or mini PRs can be substantial. However, the benefit is that it allows for more granular control and review of changes. It's also easier to isolate and fix issues that arise during testing.
 
 ## Practice Exercise