Change double quotes to single in docs where possible (#1911)

Author: sdwheeler

docs/Rules/AlignAssignmentStatement.md

@@ -19,17 +19,17 @@ are aligned or not. Consider the following example in which the key value pairs
 
 ```powershell
 $hashtable = @{
-    property1 = "value"
-    anotherProperty = "another value"
+    property1 = 'value'
+    anotherProperty = 'another value'
 }
 ```
 
 Alignment in this case would look like the following.
 
 ```powershell
 $hashtable = @{
-    property1       = "value"
-    anotherProperty = "another value"
+    property1       = 'value'
+    anotherProperty = 'another value'
 }
 ```
 

docs/Rules/AvoidGlobalAliases.md

@@ -28,7 +28,7 @@ Use other scope modifiers for new aliases.
 ### Wrong
 
 ```powershell
-New-Alias -Name Name -Value Value -Scope "Global"
+New-Alias -Name Name -Value Value -Scope Global
 ```
 
 ### Correct

docs/Rules/AvoidInvokingEmptyMembers.md

@@ -23,13 +23,13 @@ Provide the requested members for a given type or class.
 ### Wrong
 
 ```powershell
-$MyString = "abc"
+$MyString = 'abc'
 $MyString.('len'+'gth')
 ```
 
 ### Correct
 
 ```powershell
-$MyString = "abc"
+$MyString = 'abc'
 $MyString.('length')
 ```

docs/Rules/AvoidOverwritingBuiltInCmdlets.md

@@ -26,7 +26,7 @@ following your settings file.
 @{
     'Rules' = @{
         'PSAvoidOverwritingBuiltInCmdlets' = @{
-            'PowerShellVersion' = @("core-6.1.0-windows")
+            'PowerShellVersion' = @('core-6.1.0-windows')
         }
     }
 }
@@ -38,8 +38,8 @@ following your settings file.
 
 The parameter `PowerShellVersion` is a list of allowlists that ship with PSScriptAnalyzer.
 
-**Note**: The default value for `PowerShellVersion` is `"core-6.1.0-windows"` if PowerShell 6 or
-later is installed, and `"desktop-5.1.14393.206-windows"` if it is not.
+**Note**: The default value for `PowerShellVersion` is `core-6.1.0-windows` if PowerShell 6 or
+later is installed, and `desktop-5.1.14393.206-windows` if it is not.
 
 Usually, patched versions of PowerShell have the same cmdlet data, therefore only settings of major
 and minor versions of PowerShell are supplied. One can also create a custom settings file as well

docs/Rules/AvoidShouldContinueWithoutForce.md

@@ -33,7 +33,7 @@ Function Test-ShouldContinue
         $MyString = 'blah'
     )
 
-    if ($PsCmdlet.ShouldContinue("ShouldContinue Query", "ShouldContinue Caption"))
+    if ($PsCmdlet.ShouldContinue('ShouldContinue Query', 'ShouldContinue Caption'))
     {
         ...
     }
@@ -52,7 +52,7 @@ Function Test-ShouldContinue
         [Switch]$Force
     )
 
-    if ($Force -or $PsCmdlet.ShouldContinue("ShouldContinue Query", "ShouldContinue Caption"))
+    if ($Force -or $PsCmdlet.ShouldContinue('ShouldContinue Query', 'ShouldContinue Caption'))
     {
         ...
     }

docs/Rules/AvoidUsingComputerNameHardcoded.md

@@ -25,7 +25,7 @@ Remove hard coded computer names.
 ```powershell
 Function Invoke-MyRemoteCommand ()
 {
-    Invoke-Command -Port 343 -ComputerName "hardcoderemotehostname"
+    Invoke-Command -Port 343 -ComputerName hardcoderemotehostname
 }
 ```
 
@@ -45,7 +45,7 @@ Function Invoke-MyCommand ($ComputerName)
 ```powershell
 Function Invoke-MyLocalCommand ()
 {
-    Invoke-Command -Port 343 -ComputerName "hardcodelocalhostname"
+    Invoke-Command -Port 343 -ComputerName 'hardcodelocalhostname'
 }
 ```
 

docs/Rules/AvoidUsingConvertToSecureStringWithPlainText.md

@@ -30,14 +30,14 @@ module from the PowerShell Gallery.
 ### Wrong
 
 ```powershell
-$UserInput = Read-Host "Please enter your secure code"
+$UserInput = Read-Host 'Please enter your secure code'
 $EncryptedInput = ConvertTo-SecureString -String $UserInput -AsPlainText -Force
 ```
 
 ### Correct
 
 ```powershell
-$SecureUserInput = Read-Host "Please enter your secure code" -AsSecureString
+$SecureUserInput = Read-Host 'Please enter your secure code' -AsSecureString
 $EncryptedInput = ConvertFrom-SecureString -String $SecureUserInput
 $SecureString = ConvertTo-SecureString -String $EncryptedInput
 ```

docs/Rules/AvoidUsingEmptyCatchBlock.md

@@ -41,7 +41,7 @@ try
 }
 catch [DivideByZeroException]
 {
-    Write-Error "DivideByZeroException"
+    Write-Error 'DivideByZeroException'
 }
 
 try
@@ -50,6 +50,6 @@ try
 }
 catch [DivideByZeroException]
 {
-    throw "DivideByZeroException"
+    throw 'DivideByZeroException'
 }
 ```

docs/Rules/AvoidUsingInvokeExpression.md

@@ -26,7 +26,7 @@ Remove the use of `Invoke-Expression`.
 ### Wrong
 
 ```powershell
-Invoke-Expression "Get-Process"
+Invoke-Expression 'Get-Process'
 ```
 
 ### Correct

docs/Rules/AvoidUsingWMICmdlet.md

@@ -48,12 +48,12 @@ Change to the equivalent CIM based cmdlet.
 
 ```powershell
 Get-WmiObject -Query 'Select * from Win32_Process where name LIKE "myprocess%"' | Remove-WmiObject
-Invoke-WmiMethod -Class Win32_Process -Name "Create" -ArgumentList @{ CommandLine = "notepad.exe" }
+Invoke-WmiMethod -Class Win32_Process -Name 'Create' -ArgumentList @{ CommandLine = 'notepad.exe' }
 ```
 
 ### Correct
 
 ```powershell
 Get-CimInstance -Query 'Select * from Win32_Process where name LIKE "myprocess%"' | Remove-CIMInstance
-Invoke-CimMethod -ClassName Win32_Process -MethodName "Create" -Arguments @{ CommandLine = "notepad.exe" }
+Invoke-CimMethod -ClassName Win32_Process -MethodName 'Create' -Arguments @{ CommandLine = 'notepad.exe' }
 ```