From 90d4921dd32326c9772a28e3ac3f139ab9a79e67 Mon Sep 17 00:00:00 2001
From: Jeffrey Snover <private@jsnover.com>
Date: Wed, 27 Sep 2017 14:37:13 -0400
Subject: [PATCH] Add a CR to CommandNotFoundException error string

We're here at PowerShell Unplugged at Ignite, and this error message could *really* use a carriage return!
---
 .../resources/DiscoveryExceptions.resx                         | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/System.Management.Automation/resources/DiscoveryExceptions.resx b/src/System.Management.Automation/resources/DiscoveryExceptions.resx
index cad3084524b..5b405b81939 100644
--- a/src/System.Management.Automation/resources/DiscoveryExceptions.resx
+++ b/src/System.Management.Automation/resources/DiscoveryExceptions.resx
@@ -136,7 +136,8 @@
     <value>Cannot retrieve an instance of CommandDiscovery.</value>
   </data>
   <data name="CommandNotFoundException" xml:space="preserve">
-    <value>The term '{0}' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.</value>
+    <value>The term '{0}' is not recognized as the name of a cmdlet, function, script file, or operable program.
+      Check the spelling of the name, or if a path was included, verify that the path is correct and try again.</value>
   </data>
   <data name="CmdletNotFoundException" xml:space="preserve">
     <value>Argument '{0}' is not recognized as a cmdlet: {1}</value>