Fix a few typos (#12325)

Blake-Madden · web-flow · commit 433f35a5d9e2 · 2025-09-01T09:37:35.000-05:00
diff --git a/LICENSE.md b/LICENSE.md
@@ -41,7 +41,7 @@ licenses.
   other rights in the material. A licensor may make special requests, such as
   asking that all changes be marked or described. Although not required by our
   licenses, you are encouraged to respect those requests where reasonable.
-  More_considerations for the public:
+  More considerations for the public:
   [wiki.creativecommons.org/Considerations_for_licensors][03]
 
 ---
diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/About.md b/reference/5.1/Microsoft.PowerShell.Core/About/About.md
@@ -450,7 +450,7 @@ that is passed to it.
 
 ### [about_Registry_Provider](about_Registry_Provider.md)
 
-Describes teh features and functions of the Registry provider.
+Describes the features and functions of the Registry provider.
 
 ### [about_Regular_Expressions](about_Regular_Expressions.md)
 
diff --git a/reference/5.1/Microsoft.PowerShell.Management/Add-Computer.md b/reference/5.1/Microsoft.PowerShell.Management/Add-Computer.md
@@ -458,7 +458,7 @@ FQDN format. By default, no domain controller is specified.
 
 Beginning in August 2024, security hardening for domain join requires that you use the FQDN of the
 domain controller. For example: `DC1.contoso.com`. For more information, see
-[NetJoin Domain Join Hardning Changes](https://support.microsoft.com/topic/kb5020276-netjoin-domain-join-hardening-changes-2b65a0f3-1f4c-42ef-ac0f-1caaf421baf8).
+[NetJoin Domain Join Hardening Changes](https://support.microsoft.com/topic/kb5020276-netjoin-domain-join-hardening-changes-2b65a0f3-1f4c-42ef-ac0f-1caaf421baf8).
 
 ```yaml
 Type: System.String
diff --git a/reference/7.4/Microsoft.PowerShell.Core/About/about_Trap.md b/reference/7.4/Microsoft.PowerShell.Core/About/about_Trap.md
@@ -255,7 +255,7 @@ By default, when a terminating error is thrown, execution transfers to the trap
 statement. After the `trap` block is run, control returns to the next statement
 block after the location of the error.
 
-For example, when a terminating error occurs in an `foreach` statement, the
+For example, when a terminating error occurs in a `foreach` statement, the
 `trap` statement is run and execution continues at the next statement after the
 `foreach` block, not within the `foreach` block.
 
diff --git a/reference/7.4/Microsoft.PowerShell.Utility/Add-Type.md b/reference/7.4/Microsoft.PowerShell.Utility/Add-Type.md
@@ -624,7 +624,7 @@ them. However, using `Add-Type` is still permitted to allow scripts to be implic
 any version of PowerShell.
 
 Assemblies in the GAC can be loaded by type name, rather than by path. Loading assemblies from an
-arbitrary path requires `Add-Type`, since those assemblies can't not be loaded automatically.
+arbitrary path requires `Add-Type`, since those assemblies can't be loaded automatically.
 
 ## RELATED LINKS
 
diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/About.md b/reference/7.5/Microsoft.PowerShell.Core/About/About.md
@@ -460,7 +460,7 @@ that is passed to it.
 
 ### [about_Registry_Provider](about_Registry_Provider.md)
 
-Describes teh features and functions of the Registry provider.
+Describes the features and functions of the Registry provider.
 
 ### [about_Regular_Expressions](about_Regular_Expressions.md)
 
diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Parameter_Sets.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Parameter_Sets.md
@@ -68,7 +68,7 @@ handling.
 `__AllParameterSets` is the name of the default parameter set when an explicit
 default name is not used.
 
-Setting the `ParameterSetName` of a the **Parameter** attribute to
+Setting the `ParameterSetName` of the **Parameter** attribute to
 `__AllParameterSets` is equivalent to not assigning a `ParameterSetName`. In
 both cases the parameter belongs to all parameter sets.
 
diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Trap.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Trap.md
@@ -255,7 +255,7 @@ By default, when a terminating error is thrown, execution transfers to the trap
 statement. After the `trap` block is run, control returns to the next statement
 block after the location of the error.
 
-For example, when a terminating error occurs in an `foreach` statement, the
+For example, when a terminating error occurs in a `foreach` statement, the
 `trap` statement is run and execution continues at the next statement after the
 `foreach` block, not within the `foreach` block.
 
diff --git a/reference/7.5/Microsoft.PowerShell.Utility/Add-Type.md b/reference/7.5/Microsoft.PowerShell.Utility/Add-Type.md
@@ -625,7 +625,7 @@ them. However, using `Add-Type` is still permitted to allow scripts to be implic
 any version of PowerShell.
 
 Assemblies in the GAC can be loaded by type name, rather than by path. Loading assemblies from an
-arbitrary path requires `Add-Type`, since those assemblies can't not be loaded automatically.
+arbitrary path requires `Add-Type`, since those assemblies can't be loaded automatically.
 
 ## RELATED LINKS
 
diff --git a/reference/7.6/Microsoft.PowerShell.Core/About/about_Switch.md b/reference/7.6/Microsoft.PowerShell.Core/About/about_Switch.md
@@ -210,7 +210,7 @@ switch ( ([datetime]'1 Jan 1970').DayOfWeek ) {
 
 The **DayOfWeek** property of the date object is an enumeration. While
 enumerations can be compared to their numeric or string values, the `switch`
-statement converts the value to a the string representation of the enumeration.
+statement converts the value to a string representation of the enumeration.
 
 ```Output
 The string value matches a Thursday.
diff --git a/reference/7.6/Microsoft.PowerShell.Core/About/about_Trap.md b/reference/7.6/Microsoft.PowerShell.Core/About/about_Trap.md
@@ -255,7 +255,7 @@ By default, when a terminating error is thrown, execution transfers to the trap
 statement. After the `trap` block is run, control returns to the next statement
 block after the location of the error.
 
-For example, when a terminating error occurs in an `foreach` statement, the
+For example, when a terminating error occurs in a `foreach` statement, the
 `trap` statement is run and execution continues at the next statement after the
 `foreach` block, not within the `foreach` block.
 
diff --git a/reference/7.6/Microsoft.PowerShell.Utility/Add-Type.md b/reference/7.6/Microsoft.PowerShell.Utility/Add-Type.md
@@ -624,7 +624,7 @@ them. However, using `Add-Type` is still permitted to allow scripts to be implic
 any version of PowerShell.
 
 Assemblies in the GAC can be loaded by type name, rather than by path. Loading assemblies from an
-arbitrary path requires `Add-Type`, since those assemblies can't not be loaded automatically.
+arbitrary path requires `Add-Type`, since those assemblies can't be loaded automatically.
 
 ## RELATED LINKS
 
diff --git a/reference/7.6/Microsoft.PowerShell.Utility/Register-ObjectEvent.md b/reference/7.6/Microsoft.PowerShell.Utility/Register-ObjectEvent.md
@@ -128,7 +128,7 @@ Finally, we run the `Enable-ProcessCreationEvent` function in the remote session
 ### Example 4: Use the dynamic module in the PSEventJob object
 
 This example shows how to use the dynamic module in the **PSEventJob** object that is created when
-you include an **Action** in an event registration. First we create and and enable a timer object,
+you include an **Action** in an event registration. First we create and enable a timer object,
 then set the interval of the timer to 500 (milliseconds). The `Register-ObjectEvent` cmdlet
 registers the **Elapsed** event of the timer object. The **PSEventJob** object is saved in the
 `$Job` variable and is also available in the **Action** property of the event subscriber. For more
