Update markdowns (#1559)

CHANGELOG.md

@@ -1,6 +1,7 @@
 ### Version 2.3.0 - Pre-release
 
 - support for flat config files
+- support for single problem underline.
 - various [bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=is%3Aclosed+milestone%3A2.4.0)
 
 ### Version 2.2.6

README.md

@@ -274,16 +274,16 @@ This extension contributes the following variables to the [settings](https://cod
 - `eslint.format.enable` (@since 2.0.0) - uses ESlint as a formatter for files that are validated by ESLint. If enabled please ensure to disable other formatters if you want to make this the default. A good way to do so is to add the following setting `"[javascript]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }` for JavaScript. For TypeScript you need to add `"[typescript]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }`.
 - `eslint.onIgnoredFiles` (@since 2.0.10): used to control whether warnings should be generated when trying to lint ignored files. Default is `off`. Can be set to `warn`.
 - `editor.codeActionsOnSave` (@since 2.0.0): this setting now supports an entry `source.fixAll.eslint`. If set to true all auto-fixable ESLint errors from all plugins will be fixed on save. You can also selectively enable and disabled specific languages using VS Code's language scoped settings. To disable `codeActionsOnSave` for HTML files use the following setting:
-
-```json
+  ```json
   "[html]": {
     "editor.codeActionsOnSave": {
       "source.fixAll.eslint": false
     }
   }
-```
-
-The old `eslint.autoFixOnSave` setting is now deprecated and can safely be removed. Please also note that if you use ESLint as your default formatter you should turn off `editor.formatOnSave` when you have turned on `editor.codeActionsOnSave`. Otherwise you file gets fixed twice which in unnecessary.
+  ```
+  The old `eslint.autoFixOnSave` setting is now deprecated and can safely be removed. Please also note that if you use ESLint as your default formatter you should turn off `editor.formatOnSave` when you have turned on `editor.codeActionsOnSave`. Otherwise you file gets fixed twice which in unnecessary.
+- `eslint.problems.shortenToSingleLine`: (@since 2.3.0) - Shortens the text spans of underlined problems to their first related line.
+- `eslint.experimental.useFlatConfig`: (@since 2.3.0) - Enables support of experimental Flat Config (aka eslint.config.js, supported by ESLint version 8.21 or later)
 
 ## Settings Migration
 

package.json

@@ -74,7 +74,7 @@
 				"eslint.problems.shortenToSingleLine": {
 					"type": "boolean",
 					"default": false,
-					"description": "Shorten the text spans of underlined problems to their first related line.",
+					"description": "Shortens the text spans of underlined problems to their first related line.",
 					"scope": "resource"
 				},
 				"eslint.nodeEnv": {
@@ -192,7 +192,7 @@
 					"scope": "resource",
 					"type": "boolean",
 					"default": false,
-					"description": "Enable support of experimental Flat Config (aka eslint.config.js, supported by ESLint version 8.21 or later)."
+					"description": "Enables support of experimental Flat Config (aka eslint.config.js, supported by ESLint version 8.21 or later)."
 				},
 				"eslint.workingDirectories": {
 					"scope": "resource",