Fix incorrect case/capitalization in ref docs (#11941)

This ensures the following components have the correct/consistent case
throughout the reference documentation:

Preference variable, PS environment variable, PS drive, PS provider,
PS command name, PS command argument, PS module, PS file extension,
PS host name/application, #Requires statement, parameter name,
about_* topic, member name, scope modifier, keyword, operator,
calculated property key/value, attribute, type accelerator,
type literal/name, WMI namespace/class, variable name,
special character, comment-based help keyword, product/company name,
Windows drive letter/directory, Windows/Unix environment variable

In addition, changes include fixes to incorrect terminology (e.g.,
referring to a keyword as a command) and formatting of PS syntax
elements (non-exhaustive).

Author: surfingoldelephant

reference/docs-conceptual/developer/cmdlet/how-to-invoke-a-cmdlet-from-within-a-cmdlet.md

@@ -14,7 +14,7 @@ computer. The call to the `Get-Process` cmdlet is equivalent to the following co
 retrieves all the processes whose names start with the characters "a" through "t".
 
 ```powershell
-Get-Process -name [a-t]*
+Get-Process -Name [a-t]*
 ```
 
 > [!IMPORTANT]

reference/docs-conceptual/developer/cmdlet/how-to-support-jobs.md

@@ -30,7 +30,7 @@ information about background jobs, see [Background Jobs](./background-jobs.md).
 1. Create an object that derives from the
    [System.Management.Automation.Job](/dotnet/api/System.Management.Automation.Job) class. This
    object can be a custom job object or one of the job objects provided by Windows PowerShell, such
-   a [System.Management.Automation.Pseventjob](/dotnet/api/System.Management.Automation.PSEventJob)
+   a [System.Management.Automation.PSEventJob](/dotnet/api/System.Management.Automation.PSEventJob)
    object.
 
     The following example shows a custom job object.
@@ -172,7 +172,7 @@ using System.Diagnostics;            // Diagnostics namespace for retrieving
 //    user/documents/WindowsPowerShell/modules/GetProcessSample06
 //
 // To import the module, run the following command: Import-Module GetProcessSample06.
-// To test the cmdlet, run the following command: Get-Proc -name <process name>
+// To test the cmdlet, run the following command: Get-Proc -Name <process name>
 //
 
 //

reference/docs-conceptual/developer/cmdlet/how-to-validate-an-argument-count.md

@@ -9,7 +9,7 @@ title: How to Validate an Argument Count
 This example shows how to specify a validation rule that the Windows PowerShell runtime can use to check the number of arguments (the count) that a parameter accepts before the cmdlet is run. You set this validation rule by declaring the ValidateCount attribute.
 
 > [!NOTE]
-> For more information about the class that defines this attribute, see [System.Management.Automation.Validatecountattribute](/dotnet/api/System.Management.Automation.ValidateCountAttribute).
+> For more information about the class that defines this attribute, see [System.Management.Automation.ValidateCountAttribute](/dotnet/api/System.Management.Automation.ValidateCountAttribute).
 
 ## To validate an argument count
 

reference/docs-conceptual/developer/cmdlet/how-to-validate-an-argument-pattern.md

@@ -9,7 +9,7 @@ title: How to Validate an Argument Pattern
 This example shows how to specify a validation rule that the Windows PowerShell runtime can use to check the character pattern of the parameter argument before the cmdlet is run. You set this validation rule by declaring the ValidatePattern attribute.
 
 > [!NOTE]
-> For more information about the class that defines this attribute, see [System.Management.Automation.Validatepatternattribute](/dotnet/api/System.Management.Automation.ValidatePatternAttribute).
+> For more information about the class that defines this attribute, see [System.Management.Automation.ValidatePatternAttribute](/dotnet/api/System.Management.Automation.ValidatePatternAttribute).
 
 ## To validate an argument pattern
 

reference/docs-conceptual/developer/cmdlet/how-to-validate-an-argument-range.md

@@ -9,7 +9,7 @@ title: How to Validate an Argument Range
 This example shows how to specify a validation rule that the Windows PowerShell runtime can use to check the minimum and maximum values of the parameter argument before the cmdlet is run. You set this validation rule by declaring the ValidateRange attribute.
 
 > [!NOTE]
-> For more information about the class that defines this attribute, see [System.Management.Automation.Validaterangeattribute](/dotnet/api/System.Management.Automation.ValidateRangeAttribute).
+> For more information about the class that defines this attribute, see [System.Management.Automation.ValidateRangeAttribute](/dotnet/api/System.Management.Automation.ValidateRangeAttribute).
 
 ### To validate an argument range
 

reference/docs-conceptual/developer/cmdlet/how-to-validate-an-argument-set.md

@@ -9,7 +9,7 @@ title: How to Validate an Argument Set
 This example shows how to specify a validation rule that the Windows PowerShell runtime can use to check the parameter argument before the cmdlet is run. This validation rule provides a set of the valid values for the parameter argument.
 
 > [!NOTE]
-> For more information about the class that defines this attribute, see [System.Management.Automation.Validatesetattribute](/dotnet/api/System.Management.Automation.ValidateSetAttribute).
+> For more information about the class that defines this attribute, see [System.Management.Automation.ValidateSetAttribute](/dotnet/api/System.Management.Automation.ValidateSetAttribute).
 
 ## To validate an argument set
 
@@ -31,7 +31,7 @@ For more information about how to declare this attribute, see [ValidateSet Attri
 
 ## See Also
 
-[System.Management.Automation.Validatesetattribute](/dotnet/api/System.Management.Automation.ValidateSetAttribute)
+[System.Management.Automation.ValidateSetAttribute](/dotnet/api/System.Management.Automation.ValidateSetAttribute)
 
 [ValidateSet Attribute Declaration](./validateset-attribute-declaration.md)
 

reference/docs-conceptual/developer/cmdlet/how-to-validate-the-argument-length.md

@@ -9,7 +9,7 @@ title: How to Validate the Argument Length
 This example shows how to specify a validation rule that the Windows PowerShell runtime can use to check the number of characters (the length) of the parameter argument before the cmdlet is run. You set this validation rule by declaring the ValidateLength attribute.
 
 > [!NOTE]
-> For more information about the class that defines this attribute, see [System.Management.Automation.Validatelengthattribute](/dotnet/api/System.Management.Automation.ValidateLengthAttribute).
+> For more information about the class that defines this attribute, see [System.Management.Automation.ValidateLengthAttribute](/dotnet/api/System.Management.Automation.ValidateLengthAttribute).
 
 ## To validate the argument length
 

reference/docs-conceptual/developer/cmdlet/interpreting-errorrecord-objects.md

@@ -121,7 +121,7 @@ used to identify the error. This information is available through the following
 
 - [System.Management.Automation.Cmdlet.WriteError][4]
 
-- [System.Management.Automation.Cmdlet.Throwterminatingerror*][3]
+- [System.Management.Automation.Cmdlet.ThrowTerminatingError*][3]
 
 - [Adding Non-Terminating Error Reporting to Your Cmdlet](./adding-non-terminating-error-reporting-to-your-cmdlet.md)
 

reference/docs-conceptual/developer/cmdlet/parameter-attribute-declaration.md

@@ -101,7 +101,7 @@ hidden from the user for tab expansion and IntelliSense. The default is `false`.
 
 ## See Also
 
-- [System.Management.Automation.Parameterattribute][05]
+- [System.Management.Automation.ParameterAttribute][05]
 - [Cmdlet Parameter Names][07]
 - [Writing a Windows PowerShell Cmdlet][02]
 

reference/docs-conceptual/developer/cmdlet/requesting-confirmation-from-cmdlets.md

@@ -67,11 +67,11 @@ If the cmdlet or provider must send a message but not request confirmation, it c
 
 Cmdlets and providers first call the following methods to request confirmation before they attempt to perform an operation that changes a system outside of Windows PowerShell:
 
-- [System.Management.Automation.Cmdlet.Shouldprocess](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess)
+- [System.Management.Automation.Cmdlet.ShouldProcess](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess)
 
-- [System.Management.Automation.Provider.Cmdletprovider.Shouldprocess](/dotnet/api/System.Management.Automation.Provider.CmdletProvider.ShouldProcess)
+- [System.Management.Automation.Provider.CmdletProvider.ShouldProcess](/dotnet/api/System.Management.Automation.Provider.CmdletProvider.ShouldProcess)
 
-They do so by calling the [System.Management.Automation.Cmdlet.Shouldprocess](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) method, which prompts the user to confirm the operation based on how the user invoked the command.
+They do so by calling the [System.Management.Automation.Cmdlet.ShouldProcess](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) method, which prompts the user to confirm the operation based on how the user invoked the command.
 
 ## See Also