diff --git a/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx b/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx index 6f3f81dcce3..b734263cad5 100644 --- a/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx +++ b/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx @@ -185,7 +185,7 @@ The following export destination path is ambiguous: {0}. - The {0} performance counter path is not valid. + The {0} performance counter path is not valid. 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. @@ -280,7 +280,7 @@ The defined template is following: Cooked Values - You cannot import more than one comma-separated (.csv) or tab-separated (.tsv) performance counter file in each command. + You cannot import more than one comma-separated (.csv) or tab-separated (.tsv) performance counter file in each command. diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/EventlogResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/EventlogResources.resx index 70ef2ba399d..cee97f4adae 100644 --- a/src/Microsoft.PowerShell.Commands.Management/resources/EventlogResources.resx +++ b/src/Microsoft.PowerShell.Commands.Management/resources/EventlogResources.resx @@ -166,7 +166,7 @@ Do you want to remove the "{0}" source from the "{1}" computer? - Retention days is valid only if the overflow action is "OverwriteOlder". Please change and try again. + Retention days is valid only if the overflow action is "OverwriteOlder". Please change and try again. Specify a valid value for the number of retention days. diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx index 6a7bba0a3e3..45757177a0b 100644 --- a/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx +++ b/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx @@ -139,7 +139,7 @@ Could not resolve remote alias '{0}'. - Proxy creation has been skipped for the '{0}' command, because the name did not match the value of the Name parameter. + Proxy creation has been skipped for the '{0}' command, because the name did not match the value of the Name parameter. Extended type definition has been skipped for the '{0}' type because its name did not match the value of the FormatTypeName parameter. diff --git a/src/System.Management.Automation/resources/AutomationExceptions.resx b/src/System.Management.Automation/resources/AutomationExceptions.resx index 7bac162fd54..b765eed227e 100644 --- a/src/System.Management.Automation/resources/AutomationExceptions.resx +++ b/src/System.Management.Automation/resources/AutomationExceptions.resx @@ -127,7 +127,7 @@ Cannot process argument because the value of argument "{0}" is null. Change the value of argument "{0}" to a non-null value. - Cannot process argument because the value of argument "{0}" is out of range. Change argument "{0}" to a value that is within range. + Cannot process argument because the value of argument "{0}" is out of range. Change argument "{0}" to a value that is within range. Cannot perform operation because operation "{0}" is not valid. Remove operation "{0}", or investigate why it is not valid. diff --git a/src/System.Management.Automation/resources/DebuggerStrings.resx b/src/System.Management.Automation/resources/DebuggerStrings.resx index 77c87ee7796..15465afae54 100644 --- a/src/System.Management.Automation/resources/DebuggerStrings.resx +++ b/src/System.Management.Automation/resources/DebuggerStrings.resx @@ -154,7 +154,7 @@ {0}, {1,-16} Stop operation and exit the debugger - {0}, Get-PSCallStack Display call stack + {0}, Get-PSCallStack Display call stack {0}, {1,-16} List source code for the current script. diff --git a/src/System.Management.Automation/resources/DiscoveryExceptions.resx b/src/System.Management.Automation/resources/DiscoveryExceptions.resx index 80acab9ad65..2d7efadaba1 100644 --- 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: A #requires statement has specified only a shellID. #Requires statements must specify a required Windows PowerShell snap-in when running in Windows PowerShell. - 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. + 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. {0} (Version {1}) diff --git a/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx b/src/System.Management.Automation/resources/RemotingErrorIdStrings.resx index 30290babfd6..d81f6048b19 100644 --- 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 Modules to import when applied to a session - Version of the Windows PowerShell engine to use when applied to a session + Version of the Windows PowerShell engine to use when applied to a session Processor architecture to use when applied to a session @@ -1369,7 +1369,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such 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. - 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}. + 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}. No valid sessions were specified. Ensure you provide valid sessions that are in the Opened state and are available to run commands.