diff --git a/docs/mdsource/naming.source.md b/docs/mdsource/naming.source.md
index a99cdd388d..6653a73714 100644
--- a/docs/mdsource/naming.source.md
+++ b/docs/mdsource/naming.source.md
@@ -277,9 +277,9 @@ eg. add the following to `.gitignore`
 `*.received/`
 
 
-## Received and multi-targetting
+## Received and multi-targeting
 
-When a test project uses more than one `TargetFrameworks` (eg `<TargetFrameworks>net48;net7.0</TargetFrameworks>`) the runtime and version will be always be added as a uniqueness to the received file. This prevents file locking contenction when the tests from both target framework run in parallel.
+When a test project uses more than one `TargetFrameworks` (eg `<TargetFrameworks>net48;net7.0</TargetFrameworks>`) the runtime and version will be always be added as a uniqueness to the received file. This prevents file locking contention when the tests from both target framework run in parallel.
 
 
 ## Orphaned verified files
diff --git a/docs/naming.md b/docs/naming.md
index da54bf8e7e..2c21105c5f 100644
--- a/docs/naming.md
+++ b/docs/naming.md
@@ -778,9 +778,9 @@ eg. add the following to `.gitignore`
 `*.received/`
 
 
-## Received and multi-targetting
+## Received and multi-targeting
 
-When a test project uses more than one `TargetFrameworks` (eg `<TargetFrameworks>net48;net7.0</TargetFrameworks>`) the runtime and version will be always be added as a uniqueness to the received file. This prevents file locking contenction when the tests from both target framework run in parallel.
+When a test project uses more than one `TargetFrameworks` (eg `<TargetFrameworks>net48;net7.0</TargetFrameworks>`) the runtime and version will be always be added as a uniqueness to the received file. This prevents file locking contention when the tests from both target framework run in parallel.
 
 
 ## Orphaned verified files