Fix markdown headings in rule documentation (#716)

* Fix markdown headers in rule documentation

Most rule documentation markdown files had headers of the form '#header' or '##header'. This commit fixes those issues.

Some documentation markdown markdown files were in UTF8 and the rest in ASCII. This commit converts all markdown files to ASCII encoding.

* Add new line after heading, if not present

Author: Kapil Borle

RuleDocumentation/AvoidAlias.md

@@ -1,7 +1,9 @@
-# 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.
 You can use the alias instead of the command name in any Windows PowerShell commands.
 
@@ -13,13 +15,16 @@ When developing PowerShell content that will potentially need to be maintained o
 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.
 
 ## Alias Whitelist
+
 To prevent `PSScriptAnalyzer` from flagging your preferred aliases, create a whitelist of the aliases in your settings file and point `PSScriptAnalyzer` to use the settings file. For example, to disable `PSScriptAnalyzer` from flagging `cd`, which is an alias of `Set-Location`, set the settings file content to the following.
 
 ```PowerShell
 # PSScriptAnalyzerSettings.psd1
+
 @{
     'Rules' = @{
         'PSAvoidUsingCmdletAliases' = @{
@@ -30,12 +35,15 @@ To prevent `PSScriptAnalyzer` from flagging your preferred aliases, create a whi
 ```
 
 ## Example
-### Wrong：
+
+### Wrong?
+
 ``` PowerShell
 gps | Where-Object {$_.WorkingSet -gt 20000000}
 ```
 
 ### Correct:
+
 ``` PowerShell
 Get-Process | Where-Object {$_.WorkingSet -gt 20000000}
 ```

RuleDocumentation/AvoidDefaultTrueValueSwitchParameter.md

@@ -1,14 +1,19 @@
-#AvoidDefaultTrueValueSwitchParameter
+# AvoidDefaultTrueValueSwitchParameter
+
 **Severity Level: Warning**
 
-##Description
+## Description
+
 Switch parameters for commands should default to false.
 
-##How to Fix
+## How
+
 Change the default value of the switch parameter to be false.
 
-##Example
-###Wrong：
+## Example
+
+### Wrong
+
 ``` PowerShell
 function Test-Script
 {
@@ -25,7 +30,8 @@ function Test-Script
 }
 ```
 
-###Correct:
+### Correct
+
 ``` PowerShell
 function Test-Script
 {

RuleDocumentation/AvoidEmptyCatchBlock.md

@@ -1,16 +1,21 @@
-#AvoidEmptyCatchBlock
+# AvoidEmptyCatchBlock
+
 **Severity Level: Warning**
 
-##Description
+## 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 avoided wherever possible.
 
-##How to Fix
+## How
+
 Use ```Write-Error``` or ```throw``` statements within the catch block.
 
-##Example
-###Wrong:
+## Example
+
+### Wrong
+
 ``` PowerShell
 try
 {
@@ -21,7 +26,8 @@ catch [DivideByZeroException]
 }
 ```
 
-###Correct:
+### Correct
+
 ``` PowerShell
 try
 {

RuleDocumentation/AvoidGlobalAliases.md

@@ -1,22 +1,28 @@
-#AvoidGlobalAliases
+# AvoidGlobalAliases
+
 **Severity Level: Warning**
 
-##Description
+## Description
+
 Globally scoped aliases override existing aliases within the sessions with matching names. This name collision can cause difficult to debug issues for consumers of modules and scripts.  
 
 
 To understand more about scoping, see ```Get-Help about_Scopes```.
 
-##How to Fix
+## How
+
 Use other scope modifiers for new aliases.
 
-##Example
-###Wrong:
+## Example
+
+### Wrong
+
 ``` PowerShell
 New-Alias -Name Name -Value Value -Scope "Global"
 ```
 
-###Correct:
+### Correct
+
 ``` PowerShell
 New-Alias -Name Name1 -Value Value
-```
+```

RuleDocumentation/AvoidGlobalFunctions.md

@@ -1,22 +1,28 @@
-#AvoidGlobalFunctions
+# AvoidGlobalFunctions
+
 **Severity Level: Warning**
 
-##Description
+## Description
+
 Globally scoped functions override existing functions within the sessions with matching names. This name collision can cause difficult to debug issues for consumers of modules.  
 
 
 To understand more about scoping, see ```Get-Help about_Scopes```.
 
-##How to Fix
+## How
+
 Use other scope modifiers for functions.
 
-##Example
-###Wrong:
+## Example
+
+### Wrong
+
 ``` PowerShell
 function global:functionName {}
 ```
 
-###Correct:
+### Correct
+
 ``` PowerShell
 function functionName {} 
-```
+```

RuleDocumentation/AvoidGlobalVars.md

@@ -1,7 +1,9 @@
-#AvoidGlobalVars
+# AvoidGlobalVars
+
 **Severity Level: Warning**
 
-##Description
+## 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.
 
@@ -12,11 +14,14 @@ Globally scoped variables include:
 
 To understand more about scoping, see ```Get-Help about_Scopes```.
 
-##How to Fix
+## How
+
 Use other scope modifiers for variables.
 
-##Example
-###Wrong:
+## Example
+
+### Wrong
+
 ``` PowerShell
 $Global:var1 = $null
 function Test-NotGlobal ($var)
@@ -25,7 +30,8 @@ function Test-NotGlobal ($var)
 }
 ```
 
-###Correct:
+### Correct
+
 ``` PowerShell
 $var1 = $null
 function Test-NotGlobal ($var1, $var2)

RuleDocumentation/AvoidInvokingEmptyMembers.md

@@ -1,20 +1,26 @@
-#AvoidInvokingEmptyMembers
+# AvoidInvokingEmptyMembers
+
 **Severity Level: Warning**
 
-##Description
+## 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
+## How
+
 Provide the requested members for a given type or class.
 
-##Example
-###Wrong：
+## Example
+
+### Wrong
+
 ``` PowerShell
 $MyString = "abc"
 $MyString.('len'+'gth')
 ```
 
-###Correct:
+### Correct
+
 ``` PowerShell
 $MyString = "abc"
 $MyString.('length')

RuleDocumentation/AvoidNullOrEmptyHelpMessageAttribute.md

@@ -1,15 +1,20 @@
-#AvoidNullOrEmtpyHelpMessageAttribute
+# AvoidNullOrEmtpyHelpMessageAttribute
+
 **Severity Level: Warning**
 
-##Description
+## 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.
 
-##How to Fix
+## How
+
 Specify a value for the `HelpMessage` attribute.
 
-##Example
-###Wrong:
+## Example
+
+### Wrong
+
 ``` PowerShell
 Function BadFuncEmptyHelpMessageEmpty
 {
@@ -45,7 +50,8 @@ Function BadFuncEmptyHelpMessageNoAssignment
 }
 ```
 
-###Correct:
+### Correct
+
 ``` PowerShell
 Function GoodFuncHelpMessage
 {

RuleDocumentation/AvoidReservedCharInCmdlet.md

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

RuleDocumentation/AvoidReservedParams.md

@@ -1,14 +1,19 @@
-#AvoidReservedParams
+# AvoidReservedParams
+
 **Severity Level: Error**
 
-##Description
+## Description
+
 You cannot use reserved common parameters in an advanced function.
 
-##How to Fix
+## How
+
 Change the name of the parameter.
 
-##Example
-###Wrong：
+## Example
+
+### Wrong
+
 ``` PowerShell
 function Test
 {
@@ -21,7 +26,8 @@ function Test
 }
 ```
 
-###Correct:
+### Correct
+
 ``` PowerShell
 function Test
 {