PowerShell · daxian-dbw · Sep 7, 2017 · Sep 6, 2017 · Sep 6, 2017 · Sep 7, 2017
diff --git a/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx b/src/Microsoft.PowerShell.Commands.Diagnostics/resources/GetEventResources.resx
@@ -268,7 +268,7 @@ The defined template is following:
     <value>This cmdlet can be run only on Microsoft Windows 7 and above.</value>
   </data>
   <data name="Description" xml:space="preserve">
-    <value>This Windows PowerShell snap-in contains Windows Eventing and Performance Counter cmdlets.</value>
+    <value>This PowerShell snap-in contains Windows Eventing and Performance Counter cmdlets.</value>
   </data>
   <data name="NoMatchingCounterSetsInFile" xml:space="preserve">
     <value>Cannot find any performance counter sets in the {0} files that match the following: {1}.</value>

diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ComputerResources.resx
@@ -238,7 +238,7 @@
     <value>Verifying that the computer has been restarted...</value>
   </data>
   <data name="WaitForPowerShell" xml:space="preserve">
-    <value>Waiting for Windows PowerShell connectivity...</value>
+    <value>Waiting for PowerShell connectivity...</value>
   </data>
   <data name="WaitForRestartToBegin" xml:space="preserve">
     <value>Waiting for the restart to begin...</value>

diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ManagementMshSnapInResources.resx
@@ -118,7 +118,7 @@
     <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
   </resheader>
   <data name="Description" xml:space="preserve">
-    <value>This Windows PowerShell Snap-In contains management cmdlets that are used to manage Windows components.  </value>
+    <value>This PowerShell Snap-In contains management cmdlets that are used to manage Windows components.  </value>
   </data>
   <data name="Vendor" xml:space="preserve">
     <value>Microsoft Corporation</value>

diff --git a/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx b/src/Microsoft.PowerShell.Commands.Management/resources/ServiceResources.resx
@@ -199,6 +199,6 @@
     <value>Service '{1} ({0})' resume failed.</value>
   </data>
   <data name="ComputerAccessDenied" xml:space="preserve">
-    <value>The command cannot be used to configure the service '{0}' because access to computer '{1}' is denied. Run Windows PowerShell as admin and run your command again.</value>
+    <value>The command cannot be used to configure the service '{0}' because access to computer '{1}' is denied. Run PowerShell as admin and run your command again.</value>
   </data>
 </root>
diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/Debugger.resx
@@ -142,7 +142,7 @@
     <value>You cannot debug the default host Runspace using this cmdlet. To debug the default Runspace use the normal debugging commands from the host.</value>
   </data>
   <data name="RunspaceDebuggingNoHostRunspaceOrDebugger" xml:space="preserve">
-    <value>Cannot debug Runspace. The host has no debugger. Try debugging the Runspace inside the Windows PowerShell console or the Windows PowerShell ISE, both of which have built-in debuggers.</value>
+    <value>Cannot debug Runspace. The host has no debugger. Try debugging the Runspace inside the PowerShell console or with Visual Studio Code, both of which have built-in debuggers.</value>
   </data>
   <data name="RunspaceDebuggingNoHost" xml:space="preserve">
     <value>Cannot debug Runspace. There is no host or host UI. The debugger requires a host and host UI for debugging.</value>

diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/FormatAndOut_out_gridview.resx
@@ -121,7 +121,7 @@
     <value>The data format is not supported by Out-GridView.</value>
   </data>
   <data name="RestartPowerShell" xml:space="preserve">
-    <value>Microsoft .NET Framework 4.5 was installed while one or more Windows PowerShell sessions were running. To use the {0} cmdlet, close all Windows PowerShell windows, and then open a new Windows PowerShell window.</value>
+    <value>Microsoft .NET Framework 4.5 was installed while one or more PowerShell sessions were running. To use the {0} cmdlet, close all PowerShell windows, and then open a new PowerShell window.</value>
   </data>
   <data name="TypeColumnName" xml:space="preserve">
     <value>Type</value>

diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/ImplicitRemotingStrings.resx
@@ -145,16 +145,16 @@
     <value>Extended type definition has been skipped for the '{0}' type because its name did not match the value of the FormatTypeName parameter.</value>
   </data>
   <data name="ErrorSkippedUnsafeCommandName" xml:space="preserve">
-    <value>Proxy creation has been skipped for the '{0}' command, because Windows PowerShell could not verify the safety of the command name.</value>
+    <value>Proxy creation has been skipped for the '{0}' command, because PowerShell could not verify the safety of the command name.</value>
   </data>
   <data name="ErrorSkippedUnsafeParameterName" xml:space="preserve">
-    <value>Proxy creation has been skipped for the '{0}' command, because Windows PowerShell could not verify the safety of a parameter name: '{1}'.</value>
+    <value>Proxy creation has been skipped for the '{0}' command, because PowerShell could not verify the safety of a parameter name: '{1}'.</value>
   </data>
   <data name="ErrorSkippedUnsafeParameterSetName" xml:space="preserve">
-    <value>Proxy creation has been skipped for the '{0}' command, because Windows PowerShell could not verify the safety of a parameter set name: '{1}'.</value>
+    <value>Proxy creation has been skipped for the '{0}' command, because PowerShell could not verify the safety of a parameter set name: '{1}'.</value>
   </data>
   <data name="ErrorSkippedUnsafeAliasName" xml:space="preserve">
-    <value>Proxy creation has been skipped for the '{0}' command, because Windows PowerShell could not verify the safety of a parameter alias name: '{1}'.</value>
+    <value>Proxy creation has been skipped for the '{0}' command, because PowerShell could not verify the safety of a parameter alias name: '{1}'.</value>
   </data>
   <data name="ErrorCommandSkippedBecauseOfShadowing" xml:space="preserve">
     <value>Proxy creation has been skipped for the following command: '{0}', because it would shadow an existing local command.  Use the AllowClobber parameter if you want to shadow existing local commands.</value>
@@ -211,7 +211,7 @@
     <value>Completed.</value>
   </data>
   <data name="CredentialRequestTitle" xml:space="preserve">
-    <value>Windows PowerShell Credential Request</value>
+    <value>PowerShell Credential Request</value>
   </data>
   <data name="CredentialRequestBody" xml:space="preserve">
     <value>Enter your credentials for {0}.</value>

diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/ImportLocalizedDataStrings.resx
@@ -124,18 +124,18 @@
     <value>The FileName parameter was not specified. The FileName parameter is required when Import-LocalizedData is not called from a script file.</value>
   </data>
   <data name="ErrorOpeningFile" xml:space="preserve">
-    <value>The following error occurred while Windows PowerShell was opening the data file '{0}':
+    <value>The following error occurred while PowerShell was opening the data file '{0}':
 {1}.</value>
   </data>
   <data name="ErrorLoadingDataFile" xml:space="preserve">
-    <value>The following error occurred while Windows PowerShell was loading the '{0}' script data file:
+    <value>The following error occurred while PowerShell was loading the '{0}' script data file:
 {1}.</value>
   </data>
   <data name="FileNameParameterCannotHavePath" xml:space="preserve">
     <value>The argument for the FileName parameter should not contain a path.</value>
   </data>
   <data name="CannotFindPsd1File" xml:space="preserve">
-    <value>Cannot find the Windows PowerShell data file '{0}' in directory '{1}', or in any parent culture directories.</value>
+    <value>Cannot find the PowerShell data file '{0}' in directory '{1}', or in any parent culture directories.</value>
   </data>
   <data name="CannotDefineSupportedCommand" xml:space="preserve">
     <value>Cannot import localized data. The definition of additional supported commands is not allowed in this language mode.</value>

diff --git a/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx b/src/Microsoft.PowerShell.Commands.Utility/resources/UtilityMshSnapinResources.resx
@@ -118,12 +118,12 @@
     <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
   </resheader>
   <data name="Description" xml:space="preserve">
-    <value>This Windows PowerShell snap-in contains utility cmdlets that are used to view and organize data in different ways.</value>
+    <value>This PowerShell snap-in contains utility cmdlets that are used to view and organize data in different ways.</value>
   </data>
   <data name="Vendor" xml:space="preserve">
     <value>Microsoft Corporation</value>
   </data>
   <data name="Name" xml:space="preserve">
-    <value>Windows PowerShell utility snap-in</value>
+    <value>PowerShell utility snap-in</value>
   </data>
 </root>
diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/CommandLineParameterParserStrings.resx
@@ -141,11 +141,11 @@
 PowerShell[.exe] -Help | -? | /?
 
 -PSConsoleFile
-    Loads the specified Windows PowerShell console file. To create a console
-    file, use Export-Console in Windows PowerShell.
+    Loads the specified PowerShell console file. To create a console
+    file, use Export-Console in PowerShell.
 
 -Version
-    Starts the specified version of Windows PowerShell.
+    Starts the specified version of PowerShell.
 
 -NoLogo
     Hides the copyright banner at startup.
@@ -163,37 +163,37 @@ PowerShell[.exe] -Help | -? | /?
     Uses a single-threaded apartment for the execution thread.
 
 -OutputFormat
-    Determines how output from Windows PowerShell is formatted. Valid values
+    Determines how output from PowerShell is formatted. Valid values
     are "Text" (text strings) or "XML" (serialized CLIXML format).
 
 -InputFormat
-    Describes the format of data sent to Windows PowerShell. Valid values are
+    Describes the format of data sent to PowerShell. Valid values are
     "Text" (text strings) or "XML" (serialized CLIXML format).
 
 -ConfigurationName
-    Specifies a configuration endpoint in which Windows PowerShell is run.
+    Specifies a configuration endpoint in which PowerShell is run.
     This can be any endpoint registered on the local machine including the
-    default Windows PowerShell remoting endpoints or a custom endpoint having
+    default PowerShell remoting endpoints or a custom endpoint having
     specific user role capabilities.
 
 -Command
     Executes the specified commands (and any parameters) as though they were
-    typed at the Windows PowerShell command prompt, and then exits, unless
+    typed at the PowerShell command prompt, and then exits, unless
     NoExit is specified. The value of Command can be "-", a string. or a
     script block.
 
     If the value of Command is "-", the command text is read from standard
     input.
 
     Script blocks must be enclosed in braces ({}). You can specify a script
-    block only when running PowerShell.exe in Windows PowerShell. The results
+    block only when running PowerShell.exe in PowerShell. The results
     of the script are returned to the parent shell as deserialized XML objects,
     not live objects.
 
     If the value of Command is a string, Command must be the last parameter
     in the command , because any characters typed after the command are
     interpreted as the command arguments.
-       To write a string that runs a Windows PowerShell command, use the format:
+       To write a string that runs a PowerShell command, use the format:
     "&amp; {&lt;command&gt;}"
     where the quotation marks indicate a string and the invoke operator (&amp;)
     causes the command to be run.
@@ -249,7 +249,7 @@ EXAMPLES
     <value>Processing -WindowStyle '{0}' failed: {1}.</value>
   </data>
   <data name="InvalidFileArgumentExtension" xml:space="preserve">
-    <value>Processing -File '{0}' failed because the file does not have a '.ps1' extension. Specify a valid Windows PowerShell script file name, and then try again.</value>
+    <value>Processing -File '{0}' failed because the file does not have a '.ps1' extension. Specify a valid PowerShell script file name, and then try again.</value>
   </data>
   <data name="ArgumentFileDoesNotExist" xml:space="preserve">
     <value>The argument '{0}' is not recognized as the name of a script file. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.</value>

diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostStrings.resx
@@ -136,27 +136,27 @@
     <value>The shell cannot be started. A failure occurred during initialization:</value>
   </data>
   <data name="UnhandledExceptionShutdownMessage" xml:space="preserve">
-    <value>An error has occurred that was not properly handled. Additional information is shown below. The Windows PowerShell process will exit.</value>
+    <value>An error has occurred that was not properly handled. Additional information is shown below. The PowerShell process will exit.</value>
   </data>
   <data name="TranscriptPrologue" xml:space="preserve">
     <value>**********************
-Windows PowerShell transcript start
+PowerShell transcript start
 Start time: {0:yyyyMMddHHmmss}
 Username  : {1}\{2}
 Machine   : {3} ({4})
 **********************</value>
   </data>
   <data name="TranscriptEpilogue" xml:space="preserve">
     <value>**********************
-Windows PowerShell transcript end
+PowerShell transcript end
 End time: {0:yyyyMMddHHmmss}
 **********************</value>
   </data>
   <data name="ConsoleHostIsSingleton" xml:space="preserve">
     <value>An instance of the ConsoleHost class has already been created for this process.</value>
   </data>
   <data name="InitialCommandNotExecuted" xml:space="preserve">
-    <value>Command '{0}' could not be run because some Windows PowerShell Snap-Ins did not load.</value>
+    <value>Command '{0}' could not be run because some PowerShell Snap-Ins did not load.</value>
   </data>
   <data name="CommandNotExecuted" xml:space="preserve">
     <value>Command '{0}' was not run as the session in which it was intended to run was either closed or broken</value>

diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ConsoleHostUserInterfaceStrings.resx
@@ -190,6 +190,6 @@
     <value>WARNING: {0}</value>
   </data>
   <data name="ReadFailsOnNonInteractiveFlag" xml:space="preserve">
-    <value>Windows PowerShell is in NonInteractive mode. Read and Prompt functionality is not available.</value>
+    <value>PowerShell is in NonInteractive mode. Read and Prompt functionality is not available.</value>
   </data>
 </root>
diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/HostMshSnapinResources.resx
@@ -118,12 +118,12 @@
     <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
   </resheader>
   <data name="Description" xml:space="preserve">
-    <value>This Windows PowerShell snap-in contains cmdlets (such as Start-Transcript and Stop-Transcript) that are provided for use with the Windows PowerShell console host.</value>
+    <value>This PowerShell snap-in contains cmdlets (such as Start-Transcript and Stop-Transcript) that are provided for use with the PowerShell console host.</value>
   </data>
   <data name="Vendor" xml:space="preserve">
     <value>Microsoft Corporation</value>
   </data>
   <data name="Name" xml:space="preserve">
-    <value>Host Windows PowerShell Snap-In.</value>
+    <value>Host PowerShell Snap-In.</value>
   </data>
 </root>
diff --git a/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx b/src/Microsoft.PowerShell.ConsoleHost/resources/ManagedEntranceStrings.resx
@@ -134,11 +134,11 @@ Copyright (C) Microsoft Corporation. All rights reserved.</value>
 PowerShell[.exe] -Help | -? | /?
 
 -PSConsoleFile
-    Loads the specified Windows PowerShell console file. To create a console
-    file, use Export-Console in Windows PowerShell.
+    Loads the specified PowerShell console file. To create a console
+    file, use Export-Console in PowerShell.
 
 -Version
-    Starts the specified version of Windows PowerShell.
+    Starts the specified version of PowerShell.
     Enter a version number with the parameter, such as "-version 2.0".
 
 -NoLogo
@@ -155,7 +155,7 @@ PowerShell[.exe] -Help | -? | /?
     Start the shell using a multithreaded apartment.
 
 -NoProfile
-    Does not load the Windows PowerShell profile.
+    Does not load the PowerShell profile.
 
 -NonInteractive
     Does not present an interactive prompt to the user.
@@ -164,25 +164,25 @@ PowerShell[.exe] -Help | -? | /?
     Present an interactive prompt to the user.
 
 -InputFormat
-    Describes the format of data sent to Windows PowerShell. Valid values are
+    Describes the format of data sent to PowerShell. Valid values are
     "Text" (text strings) or "XML" (serialized CLIXML format).
 
 -OutputFormat
-    Determines how output from Windows PowerShell is formatted. Valid values
+    Determines how output from PowerShell is formatted. Valid values
     are "Text" (text strings) or "XML" (serialized CLIXML format).
 
 -WindowStyle
     Sets the window style to Normal, Minimized, Maximized or Hidden.
 
 -EncodedCommand
     Accepts a base-64-encoded string version of a command. Use this parameter
-    to submit commands to Windows PowerShell that require complex quotation
+    to submit commands to PowerShell that require complex quotation
     marks or curly braces.
 
 -ConfigurationName
-    Specifies a configuration endpoint in which Windows PowerShell is run.
+    Specifies a configuration endpoint in which PowerShell is run.
     This can be any endpoint registered on the local machine including the
-    default Windows PowerShell remoting endpoints or a custom endpoint having
+    default PowerShell remoting endpoints or a custom endpoint having
     specific user role capabilities.
 
 -File
@@ -196,12 +196,12 @@ PowerShell[.exe] -Help | -? | /?
 -ExecutionPolicy
     Sets the default execution policy for the current session and saves it
     in the $env:PSExecutionPolicyPreference environment variable.
-    This parameter does not change the Windows PowerShell execution policy
+    This parameter does not change the PowerShell execution policy
     that is set in the registry.
 
 -Command
     Executes the specified commands (and any parameters) as though they were
-    typed at the Windows PowerShell command prompt, and then exits, unless
+    typed at the PowerShell command prompt, and then exits, unless
     NoExit is specified. The value of Command can be "-", a string. or a
     script block.
 
@@ -210,14 +210,14 @@ PowerShell[.exe] -Help | -? | /?
 
     If the value of Command is a script block, the script block must be enclosed
     in braces ({}). You can specify a script block only when running PowerShell.exe
-    in Windows PowerShell. The results of the script block are returned to the
+    in PowerShell. The results of the script block are returned to the
     parent shell as deserialized XML objects, not live objects.
 
     If the value of Command is a string, Command must be the last parameter
     in the command , because any characters typed after the command are
     interpreted as the command arguments.
 
-    To write a string that runs a Windows PowerShell command, use the format:
+    To write a string that runs a PowerShell command, use the format:
     "&amp; {&lt;command&gt;}"
     where the quotation marks indicate a string and the invoke operator (&amp;)
     causes the command to be executed.