PowerShell · iSazonov · Sep 3, 2017 · Sep 2, 2017
diff --git a/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx b/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx
@@ -185,7 +185,7 @@
     <value>The following export destination path is ambiguous: {0}.</value>
   </data>
   <data name="CounterPathIsInvalid" xml:space="preserve">
-    <value>The {0} performance counter path  is not valid.</value>
+    <value>The {0} performance counter path is not valid.</value>
   </data>
   <data name="CounterSampleDataInvalid" xml:space="preserve">
     <value>The data in one of the performance counter samples is not valid. View the Status property for each PerformanceCounterSample object to make sure it contains valid data.</value>
@@ -280,7 +280,7 @@ The defined template is following:
     <value>Cooked Values</value>
   </data>
   <data name="Counter1FileLimit" xml:space="preserve">
-    <value>You cannot import more than one comma-separated (.csv) or tab-separated (.tsv) performance counter file  in each command.</value>
+    <value>You cannot import more than one comma-separated (.csv) or tab-separated (.tsv) performance counter file in each command.</value>
   </data>
 
 </root>
diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/EventlogResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/EventlogResources.resx
@@ -166,7 +166,7 @@
     <value>Do you want to remove the "{0}" source from the "{1}" computer?</value>
   </data>
   <data name="InvalidOverflowAction" xml:space="preserve">
-    <value>Retention days is valid only if the overflow action is "OverwriteOlder". Please change  and try again.</value>
+    <value>Retention days is valid only if the overflow action is "OverwriteOlder". Please change and try again.</value>
   </data>
   <data name="InvalidArgument" xml:space="preserve">
     <value>Specify a valid value for the number of retention days.</value>

diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx
@@ -139,7 +139,7 @@
     <value>Could not resolve remote alias '{0}'.</value>
   </data>
   <data name="ErrorSkippedNonRequestedCommand" xml:space="preserve">
-    <value>Proxy creation has been skipped for the '{0}' command, because the name did not match the value of the Name  parameter.</value>
+    <value>Proxy creation has been skipped for the '{0}' command, because the name did not match the value of the Name parameter.</value>
   </data>
   <data name="ErrorSkippedNonRequestedTypeDefinition" xml:space="preserve">
     <value>Extended type definition has been skipped for the '{0}' type because its name did not match the value of the FormatTypeName parameter.</value>

diff --git a/src/System.Management.Automation/resources/AutomationExceptions.resx b/src/System.Management.Automation/resources/AutomationExceptions.resx
@@ -127,7 +127,7 @@
     <value>Cannot process argument because the value of argument "{0}" is null. Change the value of argument "{0}" to a non-null value.</value>
   </data>
   <data name="ArgumentOutOfRange" xml:space="preserve">
-    <value>Cannot process argument because the value of argument "{0}" is out of range. Change argument "{0}" to  a value that is within range.</value>
+    <value>Cannot process argument because the value of argument "{0}" is out of range. Change argument "{0}" to a value that is within range.</value>
   </data>
   <data name="InvalidOperation" xml:space="preserve">
     <value>Cannot perform operation because operation "{0}" is not valid. Remove operation "{0}", or investigate why it is not valid.</value>

diff --git a/src/System.Management.Automation/resources/DebuggerStrings.resx b/src/System.Management.Automation/resources/DebuggerStrings.resx
     <value> {0}, {1,-16} Stop operation and exit the debugger</value>
   </data>
   <data name="GetStackTraceHelp" xml:space="preserve">
-    <value> {0}, Get-PSCallStack  Display call stack</value>
+    <value> {0}, Get-PSCallStack Display call stack</value>
   </data>
   <data name="ListHelp" xml:space="preserve">
     <value> {0}, {1,-16} List source code for the current script.  </value>

diff --git a/src/System.Management.Automation/resources/DiscoveryExceptions.resx b/src/System.Management.Automation/resources/DiscoveryExceptions.resx
@@ -194,7 +194,7 @@ The #requires statement must be in one of the following formats:
     <value>A #requires statement has specified only a shellID. #Requires statements must specify a required Windows PowerShell snap-in when running in Windows PowerShell.</value>
   </data>
   <data name="RequiresElevation" xml:space="preserve">
-    <value>The script '{0}' cannot be run because it contains a "#requires" statement for running as Administrator. The current Windows PowerShell session is not running as Administrator. Start Windows PowerShell by  using the Run as Administrator option, and then try running the script again.</value>
+    <value>The script '{0}' cannot be run because it contains a "#requires" statement for running as Administrator. The current Windows PowerShell session is not running as Administrator. Start Windows PowerShell by using the Run as Administrator option, and then try running the script again.</value>
   </data>
   <data name="PSSnapInNameVersion" xml:space="preserve">
     <value>{0} (Version {1})</value>

diff --git a/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx b/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx
@@ -1030,7 +1030,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such
     <value>Modules to import when applied to a session</value>
   </data>
   <data name="DISCPowerShellVersionComment" xml:space="preserve">
-    <value>Version of the Windows PowerShell engine to use  when applied to a session</value>
+    <value>Version of the Windows PowerShell engine to use when applied to a session</value>
   </data>
   <data name="DISCProcessorArchitectureComment" xml:space="preserve">
     <value>Processor architecture to use when applied to a session</value>
@@ -1369,7 +1369,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such
     <value>The remote session to which you are connected does not support remote debugging. You must connect to a remote computer that is running Windows PowerShell {0} or greater.</value>
   </data>
   <data name="ICMInvalidSessionState" xml:space="preserve">
-    <value>Because the session state for session {0}, {1}, {2} is not equal to Open, you cannot run a command  in the session.  The session state is {3}.</value>
+    <value>Because the session state for session {0}, {1}, {2} is not equal to Open, you cannot run a command in the session.  The session state is {3}.</value>
   </data>
   <data name="ICMNoValidRunspaces" xml:space="preserve">
     <value>No valid sessions were specified.  Ensure you provide valid sessions that are in the Opened state and are available to run commands.</value>