crates/biome_configuration/src/analyzer/assist/actions.rs (1)

181-184: Make the summary language-agnostic

The config field describes an action used in both JS and JSON. Consider removing “JSON” to avoid narrowing the scope.

-    #[doc = "Sort the keys of a JSON object in natural order."]
+    #[doc = "Sort object keys in natural order."]

Also applies to: 196-199

xtask/codegen/src/generate_configuration.rs (1)

495-498: Follow-through: align top-level ‘recommended’ docs too

For full consistency, consider updating the top-level generated structs (Actions/Rules) as well:

-                /// It enables the assist actions recommended by Biome. `true` by default.
+                /// Enables the assist actions recommended by Biome. `true` by default.

-                /// It enables the lint rules recommended by Biome. `true` by default.
+                /// Enables the lint rules recommended by Biome. `true` by default.

Also applies to: 634-637

crates/biome_js_analyze/src/assist/source/use_sorted_keys.rs (1)

21-43: Polish documentation comments

• Fix typos: “e.g. [k]: 1” and “if one exists”.
• Replace “Since ES2020…” with “Per the ECMAScript specification…” to avoid a brittle year reference.

-    /// This rule will consider spread/calculated keys e.g [k]: 1 as
-    /// non-sortable. Instead, whenever it encounters a non-sortable key, it
-    /// will sort all the previous sortable keys up until the nearest
-    /// non-sortable key, if one exist. This prevents breaking the override of
-    /// certain keys using spread keys.
+    /// This rule considers spread/calculated keys (e.g. `[k]: 1`) as non-sortable.
+    /// When it encounters a non-sortable key, it sorts preceding sortable keys
+    /// up to the nearest non-sortable key. This prevents breaking overrides of
+    /// certain keys introduced via spread keys.
@@
-    /// Sorting the keys of an object technically changes the semantics of the
-    /// program. It affects the result of operations like
-    /// `Object.getOwnPropertyNames`. Since ES2020, operations like `for-in`
-    /// loops, `Object.keys`, and `JSON.stringify` are guaranteed to process
-    /// string keys in insertion order.
+    /// Sorting object keys can change program semantics (e.g. the result of
+    /// `Object.getOwnPropertyNames`). Per the ECMAScript specification,
+    /// operations such as `for-in` loops, `Object.keys`, and `JSON.stringify`
+    /// process string keys in insertion order.

Also update the options section phrasing (see next comment).

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

Learnt from: CR
PR: biomejs/biome#0
File: CONTRIBUTING.md:0-0
Timestamp: 2025-08-11T11:40:38.097Z
Learning: For documentation of rules/assists/options, use inline Rustdoc in source code; other docs updates should go to the website repo’s next branch.

Learnt from: CR
PR: biomejs/biome#0
File: crates/biome_analyze/CONTRIBUTING.md:0-0
Timestamp: 2025-08-17T08:56:30.831Z
Learning: Applies to crates/biome_analyze/crates/**/lib/src/**/nursery/**/*.rs : Use `domains` in `declare_lint_rule!` when applicable; recommended rules with domains enable only when the domain is active

Learnt from: CR
PR: biomejs/biome#0
File: crates/biome_analyze/CONTRIBUTING.md:0-0
Timestamp: 2025-08-17T08:56:30.831Z
Learning: Applies to crates/biome_analyze/crates/biome_rule_options/lib/**/*.rs : Define per-rule options in the `biome_rule_options` crate under `lib/`, with serde- and schemars-compatible derives and `#[serde(rename_all = "camelCase", deny_unknown_fields, default)]`