Removing bad single and double quotes from articles (#4823)

Author: DCtheGeek

dsc/configurations/configurations.md

@@ -118,7 +118,7 @@ When you call the configuration, it:
   If there is more than one node, a MOF file will be created for each node.
 
 > [!NOTE]
-> The MOF file contains all of the configuration information for the target node. Because of this, it’s important to keep it secure.
+> The MOF file contains all of the configuration information for the target node. Because of this, it's important to keep it secure.
 > For more information, see [Securing the MOF file](../pull-server/secureMOF.md).
 
 Compiling the first configuration above results in the following folder structure:

dsc/configurations/import-dscresource.md

@@ -99,8 +99,8 @@ Configuration SchemaValidationInCorrectEnumValue
     {
         WindowsFeature ROLE1
         {
-            Name = “Telnet-Client”
-            Ensure = “Invalid”
+            Name = "Telnet-Client"
+            Ensure = "Invalid"
         }
     }
 }
@@ -109,7 +109,7 @@ Configuration SchemaValidationInCorrectEnumValue
 Compiling this Configuration results in an error.
 
 ```output
-PSDesiredStateConfiguration\WindowsFeature: At least one of the values ‘Invalid’ is not supported or valid for property ‘Ensure’ on class ‘WindowsFeature’. Please specify only supported values: Present, Absent.
+PSDesiredStateConfiguration\WindowsFeature: At least one of the values 'Invalid' is not supported or valid for property 'Ensure' on class 'WindowsFeature'. Please specify only supported values: Present, Absent.
 ```
 
 Intellisense and schema validation allow you to catch more errors during parse and compilation time, avoiding complications at run time.

dsc/configurations/separatingEnvData.md

@@ -266,21 +266,21 @@ $MyData =
     AllNodes =
     @(
         @{
-            NodeName           = “*”
-            LogPath            = “C:\Logs”
+            NodeName           = "*"
+            LogPath            = "C:\Logs"
         },
 
         @{
-            NodeName = “VM-1”
-            SiteContents = “C:\Site1”
-            SiteName = “Website1”
+            NodeName = "VM-1"
+            SiteContents = "C:\Site1"
+            SiteName = "Website1"
         },
 
 
         @{
-            NodeName = “VM-2”;
-            SiteContents = “C:\Site2”
-            SiteName = “Website2”
+            NodeName = "VM-2"
+            SiteContents = "C:\Site2"
+            SiteName = "Website2"
         }
     );
 
@@ -300,12 +300,12 @@ configuration WebsiteConfig
         {
             Name         = $Node.SiteName
             PhysicalPath = $Node.SiteContents
-            Ensure       = “Present”
+            Ensure       = "Present"
         }
 
         File ConfigFile
         {
-            DestinationPath = $Node.SiteContents + “\\config.xml”
+            DestinationPath = $Node.SiteContents + "\\config.xml"
             Contents = $ConfigurationData.NonNodeData.ConfigFileContents
         }
     }

dsc/getting-started/azureDscexthistory.md

@@ -158,7 +158,7 @@ This article will provide information about each version of the Azure DSC VM Ext
 - **Environment:** Azure
 - **Remarks:** This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSes, it installs the [Windows Management Framework 5.0 RTM](https://blogs.msdn.microsoft.com/powershell/2015/12/16/windows-management-framework-wmf-5-0-rtm-is-now-available/) (installing WMF requires a reboot).
 - **New features:**
-  - Support for WMF 5.1 Preview. When first published, this version was an optional upgrade and you had to specify Wmfversion = ‘5.1PP’ in Resource Manager templates to install WMF 5.1 preview. Wmfversion = ‘latest’ still installs the [WMF 5.0 RTM](https://blogs.msdn.microsoft.com/powershell/2015/12/16/windows-management-framework-wmf-5-0-rtm-is-now-available/). For more information on WMF 5.1 preview, see [this blog](https://blogs.msdn.microsoft.com/powershell/2016/07/16/announcing-windows-management-framework-wmf-5-1-preview/).
+  - Support for WMF 5.1 Preview. When first published, this version was an optional upgrade and you had to specify Wmfversion = '5.1PP' in Resource Manager templates to install WMF 5.1 preview. Wmfversion = 'latest' still installs the [WMF 5.0 RTM](https://blogs.msdn.microsoft.com/powershell/2015/12/16/windows-management-framework-wmf-5-0-rtm-is-now-available/). For more information on WMF 5.1 preview, see [this blog](https://blogs.msdn.microsoft.com/powershell/2016/07/16/announcing-windows-management-framework-wmf-5-1-preview/).
   - Minor other fixes and improvements were added.
 
 ### Version  2.19
@@ -180,7 +180,7 @@ This article will provide information about each version of the Azure DSC VM Ext
 - **Remarks:** This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSes, it installs the [Windows Management Framework 5.0 RTM](https://blogs.msdn.microsoft.com/powershell/2015/12/16/windows-management-framework-wmf-5-0-rtm-is-now-available/) (installing WMF requires a reboot).
 - **New features:**
   - Make telemetry non-blocking when an error occurs during telemetry hotfix download (known Azure DNS issue) or during install.
-  - Fix for the intermittent issue where extension stops processing configuration after a reboot. This was causing the DSC Extension to remain in ‘transitioning’ state.
+  - Fix for the intermittent issue where extension stops processing configuration after a reboot. This was causing the DSC Extension to remain in 'transitioning' state.
   - Minor other fixes and improvements were added.
 
 ### Version 2.17
@@ -203,7 +203,7 @@ This article will provide information about each version of the Azure DSC VM Ext
 - **Remarks:** This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSes, it installs the [Windows Management Framework 5.0 RTM](https://blogs.msdn.microsoft.com/powershell/2015/12/16/windows-management-framework-wmf-5-0-rtm-is-now-available/) (installing WMF requires a reboot).
 - **New features:**
   - Improvement in error handling and other minor bug fixes.
-  - New property in DSC Extension settings. ‘ForcePullAndApply’ in AdvancedOptions is added to enable the DSC Extension enact DSC configurations when the refresh mode is Pull (as opposed to the default Push mode). For more information, please refer to [this blog](https://blogs.msdn.microsoft.com/powershell/2016/02/26/arm-dsc-extension-settings/) to get more information on the DSC Extension settings.
+  - New property in DSC Extension settings. 'ForcePullAndApply' in AdvancedOptions is added to enable the DSC Extension enact DSC configurations when the refresh mode is Pull (as opposed to the default Push mode). For more information, please refer to [this blog](https://blogs.msdn.microsoft.com/powershell/2016/02/26/arm-dsc-extension-settings/) to get more information on the DSC Extension settings.
 
 ### Version 2.15
 
@@ -213,7 +213,7 @@ This article will provide information about each version of the Azure DSC VM Ext
 - **Environment:** Azure
 - **Remarks:** This version uses DSC as included in Windows Server 2016 Technical Preview; for other Windows OSes, it installs the [Windows Management Framework 5.0 RTM](https://blogs.msdn.microsoft.com/powershell/2015/12/16/windows-management-framework-wmf-5-0-rtm-is-now-available/) (installing WMF requires a reboot).
 - **New features:**
-  - In extension version 2.14, changes to install WMF RTM were included. While upgrading from extension version 2.13.2.0 to 2.14.0.0, you may notice that some DSC cmdlets fail or your configuration fails with an error – ‘No Instance found with given property values’. For more information, see the [DSC release notes](https://msdn.microsoft.com/en-us/powershell/wmf/limitation_dsc). The workarounds for these issues have been added in 2.15 version.
+  - In extension version 2.14, changes to install WMF RTM were included. While upgrading from extension version 2.13.2.0 to 2.14.0.0, you may notice that some DSC cmdlets fail or your configuration fails with an error – 'No Instance found with given property values'. For more information, see the [DSC release notes](https://msdn.microsoft.com/en-us/powershell/wmf/limitation_dsc). The workarounds for these issues have been added in 2.15 version.
   - Unfortunately, if you have already installed version 2.14 and are running into one of the above two issues, you will need to perform these steps manually.  In an elevated PowerShell session:
     - `Remove-Item -Path $env:SystemRoot\system32\Configuration\DSCEngineCache.mof`
     - `mofcomp $env:windir\system32\wbem\DscCoreConfProv.mof`

dsc/getting-started/lnxGettingStarted.md

@@ -120,7 +120,7 @@ $Sess=New-CimSession -Credential $credential -ComputerName $Node -Port 5986 -Aut
 ```
 
 > [!NOTE]
-> For “Push” mode, the user credential must be the root user on the Linux computer.
+> For "Push" mode, the user credential must be the root user on the Linux computer.
 > Only SSL/TLS connections are supported for DSC for Linux, the `New-CimSession` must be used with the –UseSSL parameter set to $true.
 > The SSL certificate used by OMI (for DSC) is specified in the file: `/opt/omi/etc/omiserver.conf` with the properties: pemfile and keyfile.
 > If this certificate is not trusted by the Windows computer that you are running the [New-CimSession](/powershell/module/CimCmdlets/New-CimSession) cmdlet on, you can choose to ignore certificate validation with the CIMSession Options: `-SkipCACheck $true -SkipCNCheck $true -SkipRevocationCheck $true`

dsc/managing-nodes/metaConfig4.md

@@ -24,7 +24,7 @@ The following lists the Local Configuration Manager properties that you can set
 - **CertificateID**: The thumbprint of a certificate used to secure credentials passed in a configuration. For more information see [Want to secure credentials in Windows PowerShell Desired State Configuration?](https://blogs.msdn.microsoft.com/powershell/2014/01/31/want-to-secure-credentials-in-windows-powershell-desired-state-configuration/).
 - **ConfigurationID**: Indicates a GUID which is used to get a particular configuration file from a pull service. The GUID ensures that the correct configuration file is accessed.
 - **ConfigurationMode**: Specifies how the Local Configuration Manager actually applies the configuration to the target nodes. It can take the following values:
-  - **ApplyOnly**: With this option, DSC applies the configuration and does nothing further unless a new configuration is detected, either by you sending a new configuration directly to the target node or if you are connecting to a pull service and DSC discovers a new configuration when it checks with the pull service. If the target node’s configuration drifts, no action is taken.
+  - **ApplyOnly**: With this option, DSC applies the configuration and does nothing further unless a new configuration is detected, either by you sending a new configuration directly to the target node or if you are connecting to a pull service and DSC discovers a new configuration when it checks with the pull service. If the target node's configuration drifts, no action is taken.
   - **ApplyAndMonitor**: With this option (which is the default), DSC applies any new configurations, whether sent by you directly to the target node or discovered on a pull service. Thereafter, if the configuration of the target node drifts from the configuration file, DSC reports the discrepancy in logs. For more about DSC logging, see [Using Event Logs to Diagnose Errors in Desired State Configuration](http://blogs.msdn.com/b/powershell/archive/2014/01/03/using-event-logs-to-diagnose-errors-in-desired-state-configuration.aspx).
   - **ApplyAndAutoCorrect**: With this option, DSC applies any new configurations, whether sent by you directly to the target node or discovered on a pull service. Thereafter, if the configuration of the target node drifts from the configuration file, DSC reports the discrepancy in logs, and then attempts to adjust the target node configuration to bring in compliance with the configuration file.
 - **ConfigurationModeFrequencyMins**: Represents the frequency (in minutes) at which the background application of DSC attempts to implement the current configuration on the target node. The default value is 15. This value can be set in conjunction with RefreshMode. When RefreshMode is set to PULL, the target node contacts the configuration service at an interval set by RefreshFrequencyMins and downloads the current configuration. Regardless of the RefreshMode value, at the interval set by ConfigurationModeFrequencyMins, the consistency engine applies the latest configuration that was downloaded to the target node. RefreshFrequencyMins should be set to an integer multiple of ConfigurationModeFrequencyMins.
@@ -33,7 +33,7 @@ The following lists the Local Configuration Manager properties that you can set
 - **DownloadManagerName**: Indicates the name of the configuration and module download manager.
 - **RebootNodeIfNeeded**: Set this to `$true` to allow resources to reboot the Node using the `$global:DSCMachineStatus` flag. Otherwise, you will have to manually reboot the node for any configuration that requires it. The default value is `$false`. To use this setting when a reboot condition is enacted by something other than DSC (such as Windows Installer), combine this setting with the [xPendingReboot](https://github.com/powershell/xpendingreboot) module.
 - **RefreshFrequencyMins**: Used when you have set up a pull service. Represents the frequency (in minutes) at which the Local Configuration Manager contacts a pull service to download the current configuration. This value can be set in conjunction with ConfigurationModeFrequencyMins. When RefreshMode is set to PULL, the target node contacts the pull service at an interval set by RefreshFrequencyMins and downloads the current configuration. At the interval set by ConfigurationModeFrequencyMins, the consistency engine then applies the latest configuration that was downloaded to the target node. If RefreshFrequencyMins is not set to an integer multiple of ConfigurationModeFrequencyMins, the system will round it up. The default value is 30.
-- **RefreshMode**: Possible values are **Push** (the default) and **Pull**. In the “push” configuration, you must place a configuration file on each target node, using any client computer. In the “pull” mode, you must set up a pull service for Local Configuration Manager to contact and access the configuration files.
+- **RefreshMode**: Possible values are **Push** (the default) and **Pull**. In the "push" configuration, you must place a configuration file on each target node, using any client computer. In the "pull" mode, you must set up a pull service for Local Configuration Manager to contact and access the configuration files.
 
 > [!NOTE]
 > The LCM starts the **ConfigurationModeFrequencyMins** cycle based on:
@@ -55,7 +55,7 @@ as shown in the following example.
 ```powershell
 Configuration ExampleConfig
 {
-    Node “Server001”
+    Node "Server001"
     {
         LocalConfigurationManager
         {

dsc/overview/authoringAdvanced.md

@@ -104,20 +104,20 @@ Configuration Name
 {
   File 1
   {
-    Ensure = “Present”
-    Path = “c:\inetpub\file1.zip”
-    Source = “http://uri/file1.zip”
+    Ensure = "Present"
+    Path = "c:\inetpub\file1.zip"
+    Source = "http://uri/file1.zip"
   }
   Service A
   {
-    Ensure = “Present”
-    Name = “ServiceA”
-    Status = “Running”
+    Ensure = "Present"
+    Name = "ServiceA"
+    Status = "Running"
   }
   SecurityBaseline Settings
   {
-    Ensure = “Present”
-    Datacenter = “NorthAmerica”
+    Ensure = "Present"
+    Datacenter = "NorthAmerica"
   }
 }
 ```

dsc/overview/overview.md

@@ -19,15 +19,15 @@ DSC is a management platform in PowerShell that enables you to manage your IT an
 DSC is a declarative platform used for configuration, deployment, and management of systems. It consists of three primary components:
 
 - [Configurations](../configurations/configurations.md) are declarative PowerShell scripts which define and configure instances of resources.
-    Upon running the configuration, DSC (and the resources being called by the configuration) will simply “make it so”,
+    Upon running the configuration, DSC (and the resources being called by the configuration) will simply "make it so",
     ensuring that the system exists in the state laid out by the configuration.
     DSC configurations are also idempotent: the Local Configuration Manager (LCM) will continue to ensure that machines are configured in whatever state the configuration declares.
 - [Resources](../resources/resources.md) are the "make it so" part of DSC. They contain the code that put and keep the target of a configuration in the specified state.
     Resources reside in PowerShell modules and can be written to model something as generic as a file or a Windows process,
     or as specific as an IIS server or a VM running in Azure.
 - The [Local Configuration Manager (LCM)](../managing-nodes/metaConfig.md) is the engine by which DSC facilitates the interaction between resources and configurations.
     The LCM regularly polls the system using the control flow implemented by resources to ensure that the state defined by a configuration is maintained.
-    If the system is out of state, the LCM makes calls to the code in resources to “make it so” according to the configuration.
+    If the system is out of state, the LCM makes calls to the code in resources to "make it so" according to the configuration.
 
 ## See Also
 

dsc/pull-server/pullClientConfigID4.md

@@ -62,7 +62,7 @@ Configuration PullClientConfigId
         RefreshFrequencyMins = 30;
         ConfigurationModeFrequencyMins = 30;
         ConfigurationMode = "ApplyAndAutoCorrect";
-        DownloadManagerCustomData = @{ServerUrl = "http://PullServer:8080/PSDSCPullServer/PSDSCPullServer.svc"; AllowUnsecureConnection = “TRUE”}
+        DownloadManagerCustomData = @{ServerUrl = "http://PullServer:8080/PSDSCPullServer/PSDSCPullServer.svc"; AllowUnsecureConnection = "TRUE"}
     }
 }
 PullClientConfigId -Output "."

dsc/pull-server/pullServerSMB.md

@@ -171,8 +171,8 @@ For more information about configuring the LCM, see [Setting up a pull client us
 > You **MUST** specify a **ConfigurationID** in the **Settings** block of a metaconfiguration for an SMB pull server, even if you are only pulling resources.
 
 ```powershell
-$secpasswd = ConvertTo-SecureString “Pass1Word” -AsPlainText -Force
-$mycreds = New-Object System.Management.Automation.PSCredential (“TestUser”, $secpasswd)
+$secpasswd = ConvertTo-SecureString "Pass1Word" -AsPlainText -Force
+$mycreds = New-Object System.Management.Automation.PSCredential ("TestUser", $secpasswd)
 
 [DSCLocalConfigurationManager()]
 configuration SmbCredTest