docs: update formatter and linter docs
MODIFY
crates/rome_analyze/CONTRIBUTING.md
crates/rome_analyze/CONTRIBUTING.md
@@ -8,7 +8,7 @@ static check.
First of all, you need to identify the crate where you want to implement the rule. If the rule
is going to be implemented for the JavaScript language (and its super languages), then the rule
-will be implemented inside the `rome_js_analyzer` crate.
+will be implemented inside the `rome_js_analyze` crate.
Rules are divided by capabilities:
- `analyzers/` folder contains rules that don't require any particular capabilities;

MODIFY
crates/rome_js_formatter/src/lib.rs
crates/rome_js_formatter/src/lib.rs
//! Rome's official JavaScript formatter.
//!
//! ## Implement the formatter
-//!`
+//!
//! Our formatter is node based. Meaning that each AST node knows how to format itself. In order to implement
//! the formatting, a node has to implement the trait `FormatNode`.
//!
//! Our formatter has its own [internal IR](https://en.wikipedia.org/wiki/Intermediate_representation), it creates its own abstraction from an AST.
//!
//! The developer won't be creating directly this IR, but they will use a series of utilities that will help
-//! to create this IR. The whole IR is represented by the `enum` `FormatElement`. Please refer to [its internal
-//! documentation](#build-the-documentation) to understand the meaning of each variant.
+//! to create this IR. The whole IR is represented by the `enum` `FormatElement`.
//!
//!
//!

docs: update formatter and linter docs (#3536)