Fix README and rule documetation

* Change CMDLets to cmdlets
* Change ``` for inline code to `

Author: Kapil Borle

README.md

@@ -14,14 +14,14 @@ Announcements
 
 Introduction
 ============
-PSScriptAnalyzer is a static code checker for Windows PowerShell modules and scripts. PSScriptAnalyzer checks the quality of Windows PowerShell code by running a set of rules. 
-The rules are based on PowerShell best practices identified by PowerShell Team and the community. It generates DiagnosticResults (errors and warnings) to inform users about potential 
+PSScriptAnalyzer is a static code checker for Windows PowerShell modules and scripts. PSScriptAnalyzer checks the quality of Windows PowerShell code by running a set of rules.
+The rules are based on PowerShell best practices identified by PowerShell Team and the community. It generates DiagnosticResults (errors and warnings) to inform users about potential
 code defects and suggests possible solutions for improvements.
 
-PSScriptAnalyzer is shipped with a collection of built-in rules that checks various aspects of PowerShell code such as presence of uninitialized variables, usage of PSCredential Type, 
+PSScriptAnalyzer is shipped with a collection of built-in rules that checks various aspects of PowerShell code such as presence of uninitialized variables, usage of PSCredential Type,
 usage of Invoke-Expression etc. Additional functionalities such as exclude/include specific rules are also supported.
 
-PSScriptAnalyzer CMDLets
+PSScriptAnalyzer Cmdlets
 ======================
 ``` PowerShell
 Get-ScriptAnalyzerRule [-CustomizedRulePath <string[]>] [-Name <string[]>] [<CommonParameters>] [-Severity <string[]>]
@@ -79,7 +79,7 @@ cd path/to/PSScriptAnalyzer
 Import-Module /path/to/PSScriptAnalyzer/out/PSScriptAnalyzer
 ```
 
-To confirm installation: run ```Get-ScriptAnalyzerRule``` in the PowerShell console to obtain the built-in rules
+To confirm installation: run `Get-ScriptAnalyzerRule` in the PowerShell console to obtain the built-in rules
 
 Suppressing Rules
 =================
@@ -112,7 +112,7 @@ function SuppressTwoVariables()
 }
 ```
 
-Use the `SuppressMessageAttribute`'s `Scope` property to limit rule suppression to functions or classes within the attribute's scope. 
+Use the `SuppressMessageAttribute`'s `Scope` property to limit rule suppression to functions or classes within the attribute's scope.
 
 Use the value `Function` to suppress violations on all functions within the attribute's scope. Use the value `Class` to suppress violations on all classes within the attribute's scope:
 
@@ -173,8 +173,8 @@ Param(
 
 Settings Support in ScriptAnalyzer
 ========================================
-Settings that describe ScriptAnalyzer rules to include/exclude based on ```Severity``` can be created and supplied to
-```Invoke-ScriptAnalyzer``` using the ```Setting``` parameter. This enables a user to create a custom configuration for a specific environment.
+Settings that describe ScriptAnalyzer rules to include/exclude based on `Severity` can be created and supplied to
+`Invoke-ScriptAnalyzer` using the `Setting` parameter. This enables a user to create a custom configuration for a specific environment.
 
 Using Settings support:
 
@@ -237,12 +237,12 @@ public System.Collections.Generic.IEnumerable<IRule> GetRule(string[] moduleName
 
 Violation Correction
 ====================
-Most violations can be fixed by replacing the violation causing content with the correct alternative. 
+Most violations can be fixed by replacing the violation causing content with the correct alternative.
 
-In an attempt to provide the user with the ability to correct the violation we provide a property, ```SuggestedCorrections```, in each DiagnosticRecord instance,
+In an attempt to provide the user with the ability to correct the violation we provide a property, `SuggestedCorrections`, in each DiagnosticRecord instance,
 that contains information needed to rectify the violation.
 
-For example, consider a script ```C:\tmp\test.ps1``` with the following content:
+For example, consider a script `C:\tmp\test.ps1` with the following content:
 ``` PowerShell
 PS> Get-Content C:\tmp\test.ps1
 gci C:\

RuleDocumentation/AvoidAlias.md

@@ -1,27 +1,27 @@
-#AvoidAlias 
+#AvoidAlias
 **Severity Level: Warning**
 
 ##Description
-An alias is an alternate name or nickname for a CMDLet or for a command element, such as a function, script, file, or executable file. 
+An alias is an alternate name or nickname for a CMDLet or for a command element, such as a function, script, file, or executable file.
 You can use the alias instead of the command name in any Windows PowerShell commands.
 
-Every PowerShell author learns the actual command names, but different authors learn and use different aliases. Aliases can make code difficult to read, understand and 
+Every PowerShell author learns the actual command names, but different authors learn and use different aliases. Aliases can make code difficult to read, understand and
 impact availability.
 
 When developing PowerShell content that will potentially need to be maintained over time, either by the original author or others, you should use full command names.
 
 The use of full command names also allows for syntax highlighting in sites and applications like GitHub and Visual Studio Code.
 
 ##How to Fix
-Use the full CMDLet name and not an alias.
+Use the full cmdlet name and not an alias.
 
 ##Example
-###Wrong： 
+###Wrong：
 ``` PowerShell
 gps | Where-Object {$_.WorkingSet -gt 20000000}
 ```
 
-###Correct: 
+###Correct:
 ``` PowerShell
 Get-Process | Where-Object {$_.WorkingSet -gt 20000000}
 ```

RuleDocumentation/AvoidDefaultTrueValueSwitchParameter.md

@@ -1,4 +1,4 @@
-#AvoidDefaultTrueValueSwitchParameter 
+#AvoidDefaultTrueValueSwitchParameter
 **Severity Level: Warning**
 
 ##Description
@@ -8,7 +8,7 @@ Switch parameters for commands should default to false.
 Change the default value of the switch parameter to be false.
 
 ##Example
-###Wrong：    
+###Wrong：
 ``` PowerShell
 function Test-Script
 {
@@ -17,15 +17,15 @@ function Test-Script
     (
         [String]
         $Param1,
-        
+
         [switch]
         $Switch=$True
     )
     ...
 }
 ```
 
-###Correct:    
+###Correct:
 ``` PowerShell
 function Test-Script
 {

RuleDocumentation/AvoidEmptyCatchBlock.md

@@ -1,10 +1,10 @@
-#AvoidEmptyCatchBlock 
+#AvoidEmptyCatchBlock
 **Severity Level: Warning**
 
 ##Description
-Empty catch blocks are considered a poor design choice as they result in the errors occurring in a ```try``` block not being acted upon.
- 
-While this does not inherently lead to issues, they should be avoid where possible. 
+Empty catch blocks are considered a poor design choice as they result in the errors occurring in a `try` block not being acted upon.
+
+While this does not inherently lead to issues, they should be avoided wherever possible.
 
 ##How to Fix
 Use ```Write-Error``` or ```throw``` statements within the catch block.

RuleDocumentation/AvoidGlobalVars.md

@@ -1,9 +1,9 @@
-#AvoidGlobalVars 
+#AvoidGlobalVars
 **Severity Level: Warning**
 
 ##Description
-A variable is a unit of memory in which values are stored. Windows PowerShell controls access to variables, functions, aliases, and drives through a mechanism known as scoping. 
-Variables and functions that are present when Windows PowerShell starts have been created in the global scope. 
+A variable is a unit of memory in which values are stored. Windows PowerShell controls access to variables, functions, aliases, and drives through a mechanism known as scoping.
+Variables and functions that are present when Windows PowerShell starts have been created in the global scope.
 
 Globally scoped variables include:
 * Automatic variables

RuleDocumentation/AvoidInvokingEmptyMembers.md

@@ -1,20 +1,20 @@
-#AvoidInvokingEmptyMembers
+#AvoidInvokingEmptyMembers
 **Severity Level: Warning**
 
 ##Description
 Invoking non-constant members can cause potential bugs. Please double check the syntax to make sure that invoked members are constants.
 
 ##How to Fix
-Provide the requested members for a given type or class. 
+Provide the requested members for a given type or class.
 
 ##Example
-###Wrong：    
+###Wrong：
 ``` PowerShell
 $MyString = "abc"
 $MyString.('len'+'gth')
 ```
 
-###Correct:    
+###Correct:
 ``` PowerShell
 $MyString = "abc"
 $MyString.('length')

RuleDocumentation/AvoidNullOrEmptyHelpMessageAttribute.md

@@ -1,12 +1,12 @@
-#AvoidNullOrEmtpyHelpMessageAttribute
+#AvoidNullOrEmtpyHelpMessageAttribute
 **Severity Level: Warning**
 
 ##Description
-The value of the ```HelpMessage``` attribute should not be an empty string or a null value as this causes PowerShell's interpreter to throw an mirror when executing the
-function or CMDLet.
+The value of the `HelpMessage` attribute should not be an empty string or a null value as this causes PowerShell's interpreter to throw an mirror when executing the
+function or cmdlet.
 
 ##How to Fix
-Specify a value for the ```HelpMessage``` attribute.
+Specify a value for the `HelpMessage` attribute.
 
 ##Example
 ###Wrong:
@@ -15,7 +15,7 @@ Function BadFuncEmptyHelpMessageEmpty
 {
 	Param(
 		[Parameter(HelpMessage='')]
-		[String] 
+		[String]
 		$Param
 	)
 
@@ -26,7 +26,7 @@ Function BadFuncEmptyHelpMessageNull
 {
 	Param(
 		[Parameter(HelpMessage=$null)]
-		[String] 
+		[String]
 		$Param
 	)
 
@@ -37,7 +37,7 @@ Function BadFuncEmptyHelpMessageNoAssignment
 {
 	Param(
 		[Parameter(HelpMessage)]
-		[String] 
+		[String]
 		$Param
 	)
 
@@ -51,7 +51,7 @@ Function GoodFuncHelpMessage
 {
 	Param(
 		[Parameter(HelpMessage='This is helpful')]
-		[String] 
+		[String]
 		$Param
 	)
 

RuleDocumentation/AvoidReservedCharInCmdlet.md

@@ -1,16 +1,16 @@
-#AvoidReservedCharInCmdlet
+#AvoidReservedCharInCmdlet
 **Severity Level: Error**
 
 ##Description
-You cannot use following reserved characters in a function or CMDLet name as these can cause parsing or runtime errors.
+You cannot use following reserved characters in a function or cmdlet name as these can cause parsing or runtime errors.
 
-Reserved Characters include: ```#,(){}[]&/\\$^;:\"'<>|?@`*%+=~``` 
+Reserved Characters include: `#,(){}[]&/\\$^;:\"'<>|?@`*%+=~`
 
 ##How to Fix
 Remove reserved characters from names.
 
 ##Example
-###Wrong： 
+###Wrong：
 ``` PowerShell
 function MyFunction[1]
 {...}

RuleDocumentation/AvoidReservedParams.md

@@ -1,4 +1,4 @@
-#AvoidReservedParams
+#AvoidReservedParams
 **Severity Level: Error**
 
 ##Description
@@ -8,14 +8,14 @@ You cannot use reserved common parameters in an advanced function.
 Change the name of the parameter.
 
 ##Example
-###Wrong： 
+###Wrong：
 ``` PowerShell
 function Test
 {
     [CmdletBinding]
     Param
     (
-        $ErrorVariable, 
+        $ErrorVariable,
         $Parameter2
     )
 }
@@ -28,7 +28,7 @@ function Test
     [CmdletBinding]
     Param
     (
-        $Err, 
+        $Err,
         $Parameter2
     )
 }

RuleDocumentation/AvoidShouldContinueWithoutForce.md

@@ -1,17 +1,17 @@
-#AvoidShouldContinueWithoutForce
+#AvoidShouldContinueWithoutForce
 **Severity Level: Warning**
 
 ##Description
 Functions that use ShouldContinue should have a boolean force parameter to allow user to bypass it.
 
-You can get more details by running ```Get-Help about_Functions_CmdletBindingAttribute``` and ```Get-Help about_Functions_Advanced_Methods``` command in Windows PowerShell.
+You can get more details by running `Get-Help about_Functions_CmdletBindingAttribute` and `Get-Help about_Functions_Advanced_Methods` command in Windows PowerShell.
 
 ##How to Fix
-Call the ```ShouldContinue``` method in advanced functions when ```ShouldProcess``` method returns ```$true```. 
+Call the `ShouldContinue` method in advanced functions when `ShouldProcess` method returns `$true`.
 
 ##Example
 ###Wrong:
-``` PowerShell 
+``` PowerShell
 Function Test-ShouldContinue
 {
     [CmdletBinding(SupportsShouldProcess=$true)]
@@ -20,7 +20,7 @@ Function Test-ShouldContinue
         $MyString = 'blah'
     )
 
-    if ($PsCmdlet.ShouldContinue("ShouldContinue Query", "ShouldContinue Caption")) 
+    if ($PsCmdlet.ShouldContinue("ShouldContinue Query", "ShouldContinue Caption"))
 	{
         ...
     }
@@ -38,7 +38,7 @@ Function Test-ShouldContinue
         [Switch]$Force
     )
 
-    if ($PsBoundParameters.ContainsKey('force') -or $PsCmdlet.ShouldContinue("ShouldContinue Query", "ShouldContinue Caption")) 
+    if ($Force -or $PsCmdlet.ShouldContinue("ShouldContinue Query", "ShouldContinue Caption"))
 	{
         ...
     }

RuleDocumentation/AvoidTrapStatement.md

@@ -1,31 +1,31 @@
-#AvoidTrapStatement
+#AvoidTrapStatement
 **Severity Level: Warning**
 
 ##Description
-The ```Trap``` keyword specifies a list of statements to run when a terminating error occurs. 
+The `Trap` keyword specifies a list of statements to run when a terminating error occurs.
 
 Trap statements handle the terminating errors and allow execution of the script or function to continue instead of stopping.
 
-Traps are intended for the use of administrators and not for script and CMDLet developers. PowerShell scripts and CMDLets should make use 
-of ```try{} catch{} finally{}``` statements.
+Traps are intended for the use of administrators and not for script and cmdlet developers. PowerShell scripts and cmdlets should make use
+of `try{} catch{} finally{}` statements.
 
 ##How to Fix
-Replace ```Trap``` statements with ```try{} catch{} finally{}``` statements.
+Replace `Trap` statements with `try{} catch{} finally{}` statements.
 
 ##Example
-###Wrong：    
+###Wrong：
 ``` PowerShell
-function Test-Trap 
+function Test-Trap
 {
     trap {"Error found: $_"}
 }
 ```
 
-###Correct:    
+###Correct:
 ``` PowerShell
-function Test-Trap 
+function Test-Trap
 {
-    try 
+    try
     {
         $a = New-Object "NonExistentObjectType"
         $a | Get-Member