docs(dev-guide/linting): improve wording

Author: rami3l

doc/dev-guide/src/linting.md

@@ -14,24 +14,21 @@ $ cargo clippy --all --all-targets --all-features -- -D warnings
 
 ## Rust-Analyzer
 
-When using  [`rust-analyzer`](https://rust-analyzer.github.io/) integration in the IDE of your choice, you might want to set the `rust-analyzer.cargo.features` configuration to `"all"` (check the [`rust-analyzer` manual](https://rust-analyzer.github.io/manual.html#configuration) for more details).
+When using [`rust-analyzer`](https://rust-analyzer.github.io/)'s clippy integration in the IDE of your choice, apart from setting the `rust-analyzer.check.command` property to `"clippy"`, you might also want to set the `rust-analyzer.cargo.features` property to `"all"` (check the [`rust-analyzer` manual](https://rust-analyzer.github.io/manual.html#configuration) for more details).
 
 ### VSCode/VSCodium setup
 
-Add 
+In your project's `.vscode/settings.json`[^vscode-global-cfg], add the following:
 
-```json
-"rust-analyzer.cargo.features": "all":,
+```jsonc
+"rust-analyzer.check.command": "clippy",
+"rust-analyzer.cargo.features": "all",
 ```
 
-in your project at `.vscode/settings.json`
+[^vscode-global-cfg]:
+    Alternatively, if you want to apply the configuration to all your Rust projects,
+    you can add it to your global configuration at `~/.config/Code/User/settings.json` instead.
 
-or
-
-to your global configuration `~/.config/Code/User/settings.json` (although you need to be aware that this will apply to all your Rust projects).
-
-
-## Rationale
-
-`rustup` uses cargo [features](https://doc.rust-lang.org/cargo/reference/features.html) in order to setup [conditional compilation](https://doc.rust-lang.org/reference/conditional-compilation.html) for integration tests as the `#[cfg(test)]` is only available for unit tests. To this end, the `test` feature has been created, however it then needs to be activated in order for tests and linting to fully work. As a shortcut we then propose to activate all features. However, if you encounter an issue, you could try activating only the `test` feature by setting the `rust-analyzer.cargo.features` configuration to `["test"]`.
+### Rationale
 
+`rustup` uses cargo [features](https://doc.rust-lang.org/cargo/reference/features.html) in order to setup [conditional compilation](https://doc.rust-lang.org/reference/conditional-compilation.html) for integration tests as the `#[cfg(test)]` is only available for unit tests. To this end, the `test` feature has been created, however it then needs to be activated in order for linting to fully work. As a shortcut we then propose to activate all features. However, if you encounter an issue, you could try activating only the `test` feature by setting the `rust-analyzer.cargo.features` configuration to `["test"]`.