docs: Standardize "Note" blockquote usage (#11724)
Standardize the blockquote "Notes" usage, so all places are using the `>` blockquote notation, as well as a consistent style for the "Note" word. PS: Thought that bolding the word "**Note**" would make for a higher visual distinction, so went for it in all existing cases! No strong feelings, though; happy to roll back to just "Note:" if that's preferrable! Release Notes: - N/A
This commit is contained in:
@@ -64,10 +64,10 @@ You can also only execute a single ESLint rule when using `fixAll`:
|
||||
}
|
||||
```
|
||||
|
||||
**Note:** the other formatter you have configured will still run, after ESLint.
|
||||
So if your language server or prettier configuration don't format according to
|
||||
ESLint's rules, then they will overwrite what ESLint fixed and you end up with
|
||||
errors.
|
||||
> **Note:** the other formatter you have configured will still run, after ESLint.
|
||||
> So if your language server or prettier configuration don't format according to
|
||||
> ESLint's rules, then they will overwrite what ESLint fixed and you end up with
|
||||
> errors.
|
||||
|
||||
If you **only** want to run ESLint on save, you can configure code actions as
|
||||
the formatter (requires Zed `0.130.x`):
|
||||
|
||||
Reference in New Issue
Block a user