spelling: display messages (#2135)

spelling: resource strings (display messages and comments)

src/System.Management.Automation/resources/CatalogStrings.resx

@@ -118,7 +118,7 @@
     <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
   </resheader>
   <data name="CatalogDefintionFileNotGenerated" xml:space="preserve">
-    <value>Unable to generate catalog defintion file.</value>
+    <value>Unable to generate catalog definition file.</value>
   </data>
   <data name="AddFileToCatalog" xml:space="preserve">
     <value>Adding file '{0}' to the catalog. Relative path of file in catalog is '{1}'.</value>
@@ -151,7 +151,7 @@
     <value>Catalog version is not valid. We only support catalog version {0} and version {1}.</value>
   </data>
   <data name="UnableToOpenCatalogDefinitionFile" xml:space="preserve">
-    <value>Unable to open catalog defintion file.</value>
+    <value>Unable to open catalog definition file.</value>
   </data>
   <data name="FoundDuplicateFileMemberInCatalog" xml:space="preserve">
     <value>Found multiple entries of file member {0} in the catalog.</value>

src/System.Management.Automation/resources/CmdletizationCoreResources.resx

@@ -163,7 +163,7 @@
     <value>Cannot process the ObjectModelWrapper attribute. The {0} type defines the {1} cmdlet parameter with a {2} attribute parameter that is ignored.  Verify that the Cmdlet Definition XML specifies a valid type in the ObjectModelWrapper attribute and retry.</value>
     <comment>{StrContains="ObjectModelWrapper"}
 {0} is a placeholder for a .NET class name.  Example: System.Net.IPAddress
-{1} is a placeholder for a cmdlet parameter name.  Example: 'ProcesId'
+{1} is a placeholder for a cmdlet parameter name.  Example: 'ProcessId'
 {2} is a placeholder for a name of a property of ParameterAttribute class. Example: ValueFromPipelineByPropertyName </comment>
   </data>
   <data name="ScriptWriter_ParameterNameConflictsWithCommonParameters" xml:space="preserve">

src/System.Management.Automation/resources/ParserStrings.resx

@@ -971,7 +971,7 @@ Possible matches are</value>
     <value>Exception parsing MOF file '{0}':{1}.</value>
   </data>
   <data name="MissingConfigurationName" xml:space="preserve">
-    <value>The name for the configuration is missing. Provide the missing name as a simple name, string, or string-valued expresson.</value>
+    <value>The name for the configuration is missing. Provide the missing name as a simple name, string, or string-valued expression.</value>
   </data>
   <data name="MissingRequiredResourcesArgument" xml:space="preserve">
     <value>Missing argument to -Resources. The argument to the -Resource parameter must be a comma-separated list of names or constant strings naming modules to reference for resource type definitions.</value>
@@ -1008,7 +1008,7 @@ Possible matches are</value>
     <value>Missing '=' operator after key in property assignment.</value>
   </data>
   <data name="DuplicatePropertyInInstanceDefinition" xml:space="preserve">
-    <value>Duplicate property assignements are not allowed in an instance definition.</value>
+    <value>Duplicate property assignments are not allowed in an instance definition.</value>
   </data>
   <data name="DuplicateCimClassDefinition" xml:space="preserve">
     <value>A second CIM class definition for '{0}' was found while processing the schema file '{1}'. This class was already defined in the file(s) '{2}'. Remove the redundant definition, and then try again.</value>

src/System.Management.Automation/resources/RemotingErrorIdStrings.resx

@@ -1268,7 +1268,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such
   <data name="InvalidIdleTimeoutOption" xml:space="preserve">
     <value>The specified IdleTimeout session option {0} (seconds) is not a valid period.  Specify an IdleTimeout value that is greater than or equal to the minimum allowed {1} (seconds).</value>
     <comment>{0} is a placeholder for the provided idletimeout
-{1} is a placeholder for the miniumum allowed idletimeout value</comment>
+{1} is a placeholder for the minimum allowed idletimeout value</comment>
   </data>
   <data name="DISCVisibilityAndAutoLoadingCannotBeBothSpecified" xml:space="preserve">
     <value>The cmdlet "{0}" or the alias "{1}" cannot be present when "{2}","{3}","{4}" or "{5}" keys are specified in the session configuration file.</value>
@@ -1393,7 +1393,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such
     <value>The job cannot be debugged because there is no host UI available.  Make sure you are running this command in a PowerShell host that implements PSHostUserInterface.</value>
   </data>
   <data name="CannotDebugJobInvalidDebuggerMode" xml:space="preserve">
-    <value>The job cannot be debugged because the host debugger mode is set to None or Default.  The host debugger mode must be LocalScript and/or RemoteSript.</value>
+    <value>The job cannot be debugged because the host debugger mode is set to None or Default.  The host debugger mode must be LocalScript and/or RemoteScript.</value>
   </data>
   <data name="FoundMultipleJobsWithId" xml:space="preserve">
     <value>Multiple jobs were found with Id {0}.  Debug-Job can debug only one job at a time.</value>
@@ -1447,7 +1447,7 @@ All WinRM sessions connected to Windows PowerShell session configurations, such
     <value>The supplied plugin context is not valid.</value>
   </data>
   <data name="WSManPluginInvalidArgSet" xml:space="preserve">
-    <value>Powershell plugin encounterd a fatal error while processing {0} arguments.</value>
+    <value>Powershell plugin encountered a fatal error while processing {0} arguments.</value>
   </data>
   <data name="WSManPluginInvalidCommandContext" xml:space="preserve">
     <value>The supplied command context is not valid.</value>
@@ -1489,19 +1489,19 @@ All WinRM sessions connected to Windows PowerShell session configurations, such
     <value>PowerShell plugin does not understand the option {0}. Make sure the client is compatible with the build {1} and the protocol version {2} of PowerShell.</value>
   </data>
   <data name="WSManPluginProtocolVersionNotFound" xml:space="preserve">
-    <value>An option with name {0} is expected from the client. Make sure the client is compatible with the build {1} and the protocl version {2} of PowerShell.</value>
+    <value>An option with name {0} is expected from the client. Make sure the client is compatible with the build {1} and the protocol version {2} of PowerShell.</value>
   </data>
   <data name="WSManPluginProtocolVersionNotMatch" xml:space="preserve">
     <value>&lt;PSProtocolVersionError ServerProtocolVersion="{0}" ServerBuildVersion="{1}"&gt;Powershell plugin does not support the protocol version {2} requested by client.&lt;/PSProtocolVersionError&gt;</value>
   </data>
   <data name="WSManPluginReportContextFailed" xml:space="preserve">
-    <value>Powershell plugin encounterd a fatal error while reporting context to WSMan service.</value>
+    <value>Powershell plugin encountered a fatal error while reporting context to WSMan service.</value>
   </data>
   <data name="WSManPluginSessionCreationFailed" xml:space="preserve">
     <value>Unable to create managed server session.</value>
   </data>
   <data name="WSManPluginShutdownRegistrationFailed" xml:space="preserve">
-    <value>Powershell plugin encounterd a fatal error registering a wait handle for shutdown notification.</value>
+    <value>Powershell plugin encountered a fatal error registering a wait handle for shutdown notification.</value>
   </data>
   <data name="ServerDriverRemoteHostAlreadyPushed" xml:space="preserve">
     <value>Cannot enter Runspace because a Runspace is already pushed in this session.</value>