Fix a few typos (#11072)

Fix some typos in three files that were grammatically incorrect.

Author: guanyuming-he

reference/docs-conceptual/community/contributing/pull-requests.md

@@ -18,10 +18,10 @@ is published to `learn.microsoft.com`.
 
 Before starting any changes, create a working branch in your local copy of the PowerShell-Docs
 repository. When working locally, be sure to synchronize your local repository before creating your
-working branch. The working branch should be created from an update-to-date copy of the `main`
+working branch. The working branch should be created from an up-to-date copy of the `main`
 branch.
 
-All pull requests should target the `main` branch. Don't submit change to the `live` branch. Changes
+All pull requests should target the `main` branch. Don't submit changes to the `live` branch. Changes
 made in the `main` branch get merged into `live`, overwriting any changes made to `live`.
 
 ## Make the pull request process work better for everyone
@@ -41,7 +41,7 @@ changed files. Large PRs are difficult to review and are more prone to contain e
 When renaming or deleting files, there must be an issue associated with the PR. That issue must
 discuss the need to rename or delete the files.
 
-Avoid mixing content additions or change with file renames and deletes. Any file that's renamed or
+Avoid mixing content additions or changes with file renames and deletes. Any file that's renamed or
 deleted must be added to the global redirection file. When possible, update any files that link to
 the renamed or deleted content, including any TOC files.
 

reference/docs-conceptual/dsc/overview.md

@@ -17,7 +17,7 @@ There are three versions of DSC available:
   With the release of PowerShell 7.2, the **PSDesiredStateConfiguration** module is no longer
   included in the PowerShell package. Separating DSC into its own module allows us to invest and
   develop DSC independent of PowerShell and reduces the size of the PowerShell package. Users of DSC
-  will enjoy the benefit of upgrading DSC without the need to upgrade PowerShell, accelerating time
+  will enjoy the benefit of upgrading DSC without the need to upgrade PowerShell, accelerating the time
   to deployment of new DSC features. Users that want to continue using DSC v2 can download
   **PSDesiredStateConfiguration** 2.0.5 from the PowerShell Gallery.
 - DSC 3.0 is the new version of DSC. This version is a preview release that is still being
@@ -26,7 +26,7 @@ There are three versions of DSC available:
   Automanage.
 
 The documentation for DSC has been moved to a new location so that we can manage the DSC
-version-specific information separate from the versions of PowerShell.
+version-specific information separately from the versions of PowerShell.
 
 See the new documentation in [Desired State Configuration 2.0][02].
 

reference/docs-conceptual/security/security-features.md

@@ -86,7 +86,7 @@ throwing errors. The log messages describe what restrictions would apply if the
   session on a locked down machine.
 
 - PowerShell 7.2 now disallows scripts from using COM objects in AppLocker system lock down
-  conditions. Cmdlet that use COM or DCOM internally aren't affected.
+  conditions. Cmdlets that use COM or DCOM internally aren't affected.
 
 ### Security Servicing Criteria