Commandline examples fix

CHANGELOG.md

@@ -3,9 +3,10 @@
 
 ### Version 1.4.1
 
-* Github Issue 54: [New Feature] Support for DB2/SQLLite string concatenation operator
-* Github Issue 48: [Bugfix] Correction to SQL 2012 add-in install folder *UNTESTED*
-* Github Issue 52: [Bugfix] Fix to space-indent saving in formatting plugin options (SSMS, Notepad++)
+* Github Issue #54: [New Feature] Support for DB2/SQLLite string concatenation operator
+* Github Issue #48: [Bugfix] Correction to SQL 2012 add-in install folder *UNTESTED*
+* Github Issue #52: [Bugfix] Fix to space-indent saving in formatting plugin options (SSMS, Notepad++)
+* [Bugfix] Fix examples in commandline help to correspond to existing options [thanks John Landmesser for the bug report]
 
 
 ### Version 1.3.1

PoorMansTSqlFormatterCmdLine/GeneralLanguageContent.es.resx

@@ -191,7 +191,7 @@ Se puede proporcionar el codigo SQL por tubería (pipe) en vez de proporcionar u
 
 Exemplos:
 
-SqlFormatter TestFiles\* /is:"  " /tc /uc- 
+SqlFormatter TestFiles\* /is:"  " /tc /uk- 
 
 SqlFormatter test*.sql /o:resultfile.sql
 

PoorMansTSqlFormatterCmdLine/GeneralLanguageContent.fr.resx

@@ -191,7 +191,7 @@ Vous pouvez aussi utilizer un Tube (/tuyeau/pipe) pour proportionner le SQL d'en
 
 Par exemple:
 
-SqlFormatter TestFiles\* /is:"  " /tc /uc- 
+SqlFormatter TestFiles\* /is:"  " /tc /uk- 
 
 SqlFormatter test*.sql /o:resultfile.sql
 

PoorMansTSqlFormatterCmdLine/GeneralLanguageContent.resx

@@ -190,7 +190,7 @@ You can also pipe the SQL to be formatted in (UTF-8 encoding), and then no input
 
 Examples:
 
-SqlFormatter TestFiles\* /is:"  " /tc /uc- 
+SqlFormatter TestFiles\* /is:"  " /tc /uk- 
 
 SqlFormatter test*.sql /o:resultfile.sql