diff --git a/.vitepress/data/rules.json b/.vitepress/data/rules.json
index 76e2439e82f..d8b26effdeb 100644
--- a/.vitepress/data/rules.json
+++ b/.vitepress/data/rules.json
@@ -1237,7 +1237,7 @@
     "value": "no-useless-rename",
     "category": "correctness",
     "type_aware": false,
-    "fix": "pending",
+    "fix": "fixable_fix",
     "default": true,
     "docs_url": "https://oxc.rs/docs/guide/usage/linter/rules/eslint/no-useless-rename.html"
   },
@@ -4412,7 +4412,7 @@
   {
     "scope": "typescript",
     "value": "prefer-optional-chain",
-    "category": "style",
+    "category": "nursery",
     "type_aware": true,
     "fix": "fixable_fix",
     "default": false,
diff --git a/src/docs/guide/usage/formatter/generated-config.md b/src/docs/guide/usage/formatter/generated-config.md
index 329fa51cfc3..83ec48d097e 100644
--- a/src/docs/guide/usage/formatter/generated-config.md
+++ b/src/docs/guide/usage/formatter/generated-config.md
@@ -4,256 +4,964 @@ search: false
 
 # Configuration options for the Oxfmt.
 
-Most options are the same as Prettier's options.
-See also <https://prettier.io/docs/options>
-
+Most options are the same as Prettier's options, but not all of them.
 In addition, some options are our own extensions.
 
 ## arrowParens
 
-type: `"always" | "avoid" | null`
+type: `"always" | "avoid"`
+
+Include parentheses around a sole arrow function parameter.
 
-Include parentheses around a sole arrow function parameter. (Default: `"always"`)
+- Default: `"always"`
 
 ## bracketSameLine
 
-type: `boolean | null`
+type: `boolean`
+
+Put the `>` of a multi-line HTML (HTML, JSX, Vue, Angular) element at the end of the last line,
+instead of being alone on the next line (does not apply to self closing elements).
 
-Put the `>` of a multi-line JSX element at the end of the last line
-instead of being alone on the next line. (Default: `false`)
+- Default: `false`
 
 ## bracketSpacing
 
-type: `boolean | null`
+type: `boolean`
 
-Print spaces between brackets in object literals. (Default: `true`)
+Print spaces between brackets in object literals.
+
+- Default: `true`
 
 ## embeddedLanguageFormatting
 
-type: `"auto" | "off" | null`
+type: `"auto" | "off"`
+
+Control whether to format embedded parts (For example, CSS-in-JS, or JS-in-Vue, etc.) in the file.
 
-Control whether to format embedded parts in the file.
-e.g. JS-in-Vue, CSS-in-JS, etc. (Default: `"auto"`)
+NOTE: XXX-in-JS support is incomplete.
+JS-in-XXX is fully supported but still be handled by Prettier.
+
+- Default: `"auto"`
 
 ## endOfLine
 
-type: `"lf" | "crlf" | "cr" | null`
+type: `"lf" | "crlf" | "cr"`
+
+Which end of line characters to apply.
+
+NOTE: `"auto"` is not supported.
 
-Which end of line characters to apply. (Default: `"lf"`)
+- Default: `"lf"`
+- Overrides `.editorconfig.end_of_line`
 
 ## experimentalSortImports
 
-type: `object | null`
+type: `object`
+
+Experimental: Sort import statements.
+
+Using the similar algorithm as [eslint-plugin-perfectionist/sort-imports](https://perfectionist.dev/rules/sort-imports).
+For details, see each field's documentation.
+
+- Default: Disabled
+
+### experimentalSortImports.customGroups
+
+type: `array`
+
+Define your own groups for matching very specific imports.
+
+The `customGroups` list is ordered: The first definition that matches an element will be used.
+Custom groups have a higher priority than any predefined group.
+
+If you want a predefined group to take precedence over a custom group,
+you must write a custom group definition that does the same as what the predefined group does, and put it first in the list.
+
+- Default: `[]`
+
+#### experimentalSortImports.customGroups[n]
+
+type: `object`
+
+##### experimentalSortImports.customGroups[n].elementNamePattern
 
-Experimental: Sort import statements. (Default: disabled)
+type: `string[]`
+
+default: `[]`
+
+List of import name prefixes to match for this group.
+
+##### experimentalSortImports.customGroups[n].groupName
+
+type: `string`
+
+default: `""`
+
+Name of the custom group, used in the `groups` option.
 
 ### experimentalSortImports.groups
 
-type: `array | null`
+type: `array`
+
+Specifies a list of predefined import groups for sorting.
+
+Each import will be assigned a single group specified in the groups option (or the `unknown` group if no match is found).
+The order of items in the `groups` option determines how groups are ordered.
+
+Within a given group, members will be sorted according to the type, order, ignoreCase, etc. options.
 
-Custom groups configuration for organizing imports.
-Each array element represents a group, and multiple group names in the same array are treated as one.
-Accepts both `string` and `string[]` as group elements.
+Individual groups can be combined together by placing them in an array.
+The order of groups in that array does not matter.
+All members of the groups in the array will be sorted together as if they were part of a single group.
+
+Predefined groups are characterized by a single selector and potentially multiple modifiers.
+You may enter modifiers in any order, but the selector must always come at the end.
+
+The list of selectors is sorted from most to least important:
+
+- `type` — TypeScript type imports.
+- `side-effect-style` — Side effect style imports.
+- `side-effect` — Side effect imports.
+- `style` — Style imports.
+- `index` — Main file from the current directory.
+- `sibling` — Modules from the same directory.
+- `parent` — Modules from the parent directory.
+- `subpath` — Node.js subpath imports.
+- `internal` — Your internal modules.
+- `builtin` — Node.js Built-in Modules.
+- `external` — External modules installed in the project.
+- `import` — Any import.
+
+The list of modifiers is sorted from most to least important:
+
+- `side-effect` — Side effect imports.
+- `type` — TypeScript type imports.
+- `value` — Value imports.
+- `default` — Imports containing the default specifier.
+- `wildcard` — Imports containing the wildcard (`* as`) specifier.
+- `named` — Imports containing at least one named specifier.
+- `multiline` — Imports on multiple lines.
+- `singleline` — Imports on a single line.
+
+See also <https://perfectionist.dev/rules/sort-imports#groups> for details.
+
+- Default: See below
+
+```json
+[
+  "type-import",
+  ["value-builtin", "value-external"],
+  "type-internal",
+  "value-internal",
+  ["type-parent", "type-sibling", "type-index"],
+  ["value-parent", "value-sibling", "value-index"],
+  "unknown"
+]
+```
 
 #### experimentalSortImports.groups[n]
 
-type: `string[]`
+type: `array | string`
+
+##### experimentalSortImports.groups[n][n]
+
+type: `string`
 
 ### experimentalSortImports.ignoreCase
 
-type: `boolean | null`
+type: `boolean`
+
+Specifies whether sorting should be case-sensitive.
 
-Ignore case when sorting. (Default: `true`)
+- Default: `true`
 
 ### experimentalSortImports.internalPattern
 
 type: `string[]`
 
-Glob patterns to identify internal imports.
+Specifies a prefix for identifying internal imports.
+
+This is useful for distinguishing your own modules from external dependencies.
+
+- Default: `["~/", "@/"]`
 
 ### experimentalSortImports.newlinesBetween
 
-type: `boolean | null`
+type: `boolean`
+
+Specifies whether to add newlines between groups.
 
-Add newlines between import groups. (Default: `true`)
+When `false`, no newlines are added between groups.
+
+- Default: `true`
 
 ### experimentalSortImports.order
 
-type: `"asc" | "desc" | null`
+type: `"asc" | "desc"`
+
+Specifies whether to sort items in ascending or descending order.
 
-Sort order. (Default: `"asc"`)
+- Default: `"asc"`
 
 ### experimentalSortImports.partitionByComment
 
-type: `boolean | null`
+type: `boolean`
+
+Enables the use of comments to separate imports into logical groups.
+
+When `true`, all comments will be treated as delimiters, creating partitions.
+
+```js
+import { b1, b2 } from "b";
+// PARTITION
+import { a } from "a";
+import { c } from "c";
+```
 
-Partition imports by comments. (Default: `false`)
+- Default: `false`
 
 ### experimentalSortImports.partitionByNewline
 
-type: `boolean | null`
+type: `boolean`
 
-Partition imports by newlines. (Default: `false`)
+Enables the empty line to separate imports into logical groups.
+
+When `true`, formatter will not sort imports if there is an empty line between them.
+This helps maintain the defined order of logically separated groups of members.
+
+```js
+import { b1, b2 } from "b";
+
+import { a } from "a";
+import { c } from "c";
+```
+
+- Default: `false`
 
 ### experimentalSortImports.sortSideEffects
 
-type: `boolean | null`
+type: `boolean`
+
+Specifies whether side effect imports should be sorted.
 
-Sort side-effect imports. (Default: `false`)
+By default, sorting side-effect imports is disabled for security reasons.
+
+- Default: `false`
 
 ## experimentalSortPackageJson
 
-type: `object | boolean | null`
+type: `object | boolean`
+
+Experimental: Sort `package.json` keys.
+
+The algorithm is NOT compatible with [prettier-plugin-sort-packagejson](https://github.com/matzkoh/prettier-plugin-packagejson).
+But we believe it is clearer and easier to navigate.
+For details, see each field's documentation.
 
-Experimental: Sort `package.json` keys. (Default: `true`)
+- Default: `true`
 
 ### experimentalSortPackageJson.sortScripts
 
-type: `boolean | null`
+type: `boolean`
 
-Sort the `scripts` field alphabetically. (Default: `false`)
+Sort the `scripts` field alphabetically.
 
-## experimentalTailwindcss
+- Default: `false`
 
-type: `object | null`
+## experimentalTailwindcss
 
-Experimental: Sort Tailwind CSS classes in string literals.
+type: `object`
 
-When enabled, `Oxfmt` sorts Tailwind CSS classes using the same algorithm as
-[`prettier-plugin-tailwindcss`](https://github.com/tailwindlabs/prettier-plugin-tailwindcss).
+Experimental: Sort Tailwind CSS classes.
 
-See [`TailwindcssConfig`] for available options.
+Using the same algorithm as [prettier-plugin-tailwindcss](https://github.com/tailwindlabs/prettier-plugin-tailwindcss).
+Option names omit the `tailwind` prefix used in the original plugin (e.g., `config` instead of `tailwindConfig`).
+For details, see each field's documentation.
 
-(Default: disabled)
+- Default: Disabled
 
 ### experimentalTailwindcss.attributes
 
 type: `string[]`
 
-List of attributes that contain Tailwind CSS classes.
+List of attribute prefixes that contain Tailwind CSS classes.
 
-Note: Regex patterns are not yet supported.
+NOTE: Regex patterns are not yet supported.
 
-Example: `["myClassProp", ":class"]`
-
-Default: `["class", "className"]`
+- Default: `["class", "className"]`
+- Example: `["myClassProp", ":class"]`
 
 ### experimentalTailwindcss.config
 
-type: `string | null`
+type: `string`
 
 Path to your Tailwind CSS configuration file (v3).
 
-Note: Paths are resolved relative to the Oxfmt configuration file.
+NOTE: Paths are resolved relative to the Oxfmt configuration file.
 
-Default: `"./tailwind.config.js"`
+- Default: Automatically find `"tailwind.config.js"`
 
 ### experimentalTailwindcss.functions
 
 type: `string[]`
 
-List of custom function names that contain Tailwind CSS classes.
-
-Note: Regex patterns are not yet supported.
+List of custom function name prefixes that contain Tailwind CSS classes.
 
-Example: `["clsx", "cn", "cva", "tw"]`
+NOTE: Regex patterns are not yet supported.
 
-Default: `[]`
+- Default: `[]`
+- Example: `["clsx", "cn", "cva", "tw"]`
 
 ### experimentalTailwindcss.preserveDuplicates
 
-type: `boolean | null`
+type: `boolean`
 
 Preserve duplicate classes.
 
-Default: `false`
+- Default: `false`
 
 ### experimentalTailwindcss.preserveWhitespace
 
-type: `boolean | null`
+type: `boolean`
 
 Preserve whitespace around classes.
 
-Default: `false`
+- Default: `false`
 
 ### experimentalTailwindcss.stylesheet
 
-type: `string | null`
+type: `string`
 
 Path to your Tailwind CSS stylesheet (v4).
 
-Note: Paths are resolved relative to the Oxfmt configuration file.
+NOTE: Paths are resolved relative to the Oxfmt configuration file.
+
+- Default: Installed Tailwind CSS's `theme.css`
+
+## htmlWhitespaceSensitivity
+
+type: `"css" | "strict" | "ignore"`
 
-Example: `"./src/app.css"`
+Specify the global whitespace sensitivity for HTML, Vue, Angular, and Handlebars.
+
+- Default: `"css"`
 
 ## ignorePatterns
 
 type: `string[]`
 
-Ignore files matching these glob patterns. Current working directory is used as the root.
+Ignore files matching these glob patterns.
+Patterns are based on the location of the Oxfmt configuration file.
+
+- Default: `[]`
 
 ## insertFinalNewline
 
-type: `boolean | null`
+type: `boolean`
+
+Whether to insert a final newline at the end of the file.
 
-Whether to insert a final newline at the end of the file. (Default: `true`)
+- Default: `true`
+- Overrides `.editorconfig.insert_final_newline`
 
 ## jsxSingleQuote
 
-type: `boolean | null`
+type: `boolean`
 
-Use single quotes instead of double quotes in JSX. (Default: `false`)
+Use single quotes instead of double quotes in JSX.
+
+- Default: `false`
 
 ## objectWrap
 
-type: `"preserve" | "collapse" | null`
+type: `"preserve" | "collapse"`
+
+How to wrap object literals when they could fit on one line or span multiple lines.
+
+By default, formats objects as multi-line if there is a newline prior to the first property.
+Authors can use this heuristic to contextually improve readability, though it has some downsides.
+
+- Default: `"preserve"`
+
+## overrides
+
+type: `array`
+
+File-specific overrides.
+When a file matches multiple overrides, the later override takes precedence (array order matters).
+
+- Default: `[]`
+
+### overrides[n]
+
+type: `object`
+
+#### overrides[n].excludeFiles
+
+type: `string[]`
+
+Glob patterns to exclude from this override.
+
+#### overrides[n].files
+
+type: `string[]`
+
+Glob patterns to match files for this override.
+All patterns are relative to the Oxfmt configuration file.
+
+#### overrides[n].options
+
+type: `object`
+
+##### overrides[n].options.arrowParens
+
+type: `"always" | "avoid"`
+
+Include parentheses around a sole arrow function parameter.
+
+- Default: `"always"`
+
+##### overrides[n].options.bracketSameLine
+
+type: `boolean`
+
+Put the `>` of a multi-line HTML (HTML, JSX, Vue, Angular) element at the end of the last line,
+instead of being alone on the next line (does not apply to self closing elements).
+
+- Default: `false`
+
+##### overrides[n].options.bracketSpacing
+
+type: `boolean`
+
+Print spaces between brackets in object literals.
+
+- Default: `true`
+
+##### overrides[n].options.embeddedLanguageFormatting
+
+type: `"auto" | "off"`
+
+Control whether to format embedded parts (For example, CSS-in-JS, or JS-in-Vue, etc.) in the file.
+
+NOTE: XXX-in-JS support is incomplete.
+JS-in-XXX is fully supported but still be handled by Prettier.
+
+- Default: `"auto"`
+
+##### overrides[n].options.endOfLine
+
+type: `"lf" | "crlf" | "cr"`
+
+Which end of line characters to apply.
+
+NOTE: `"auto"` is not supported.
+
+- Default: `"lf"`
+- Overrides `.editorconfig.end_of_line`
+
+##### overrides[n].options.experimentalSortImports
+
+type: `object`
+
+Experimental: Sort import statements.
+
+Using the similar algorithm as [eslint-plugin-perfectionist/sort-imports](https://perfectionist.dev/rules/sort-imports).
+For details, see each field's documentation.
+
+- Default: Disabled
+
+###### overrides[n].options.experimentalSortImports.customGroups
+
+type: `array`
+
+Define your own groups for matching very specific imports.
+
+The `customGroups` list is ordered: The first definition that matches an element will be used.
+Custom groups have a higher priority than any predefined group.
+
+If you want a predefined group to take precedence over a custom group,
+you must write a custom group definition that does the same as what the predefined group does, and put it first in the list.
+
+- Default: `[]`
+
+####### overrides[n].options.experimentalSortImports.customGroups[n]
+
+type: `object`
+
+######## overrides[n].options.experimentalSortImports.customGroups[n].elementNamePattern
+
+type: `string[]`
+
+default: `[]`
+
+List of import name prefixes to match for this group.
+
+######## overrides[n].options.experimentalSortImports.customGroups[n].groupName
+
+type: `string`
+
+default: `""`
+
+Name of the custom group, used in the `groups` option.
+
+###### overrides[n].options.experimentalSortImports.groups
+
+type: `array`
+
+Specifies a list of predefined import groups for sorting.
+
+Each import will be assigned a single group specified in the groups option (or the `unknown` group if no match is found).
+The order of items in the `groups` option determines how groups are ordered.
+
+Within a given group, members will be sorted according to the type, order, ignoreCase, etc. options.
+
+Individual groups can be combined together by placing them in an array.
+The order of groups in that array does not matter.
+All members of the groups in the array will be sorted together as if they were part of a single group.
+
+Predefined groups are characterized by a single selector and potentially multiple modifiers.
+You may enter modifiers in any order, but the selector must always come at the end.
+
+The list of selectors is sorted from most to least important:
+
+- `type` — TypeScript type imports.
+- `side-effect-style` — Side effect style imports.
+- `side-effect` — Side effect imports.
+- `style` — Style imports.
+- `index` — Main file from the current directory.
+- `sibling` — Modules from the same directory.
+- `parent` — Modules from the parent directory.
+- `subpath` — Node.js subpath imports.
+- `internal` — Your internal modules.
+- `builtin` — Node.js Built-in Modules.
+- `external` — External modules installed in the project.
+- `import` — Any import.
+
+The list of modifiers is sorted from most to least important:
+
+- `side-effect` — Side effect imports.
+- `type` — TypeScript type imports.
+- `value` — Value imports.
+- `default` — Imports containing the default specifier.
+- `wildcard` — Imports containing the wildcard (`* as`) specifier.
+- `named` — Imports containing at least one named specifier.
+- `multiline` — Imports on multiple lines.
+- `singleline` — Imports on a single line.
+
+See also <https://perfectionist.dev/rules/sort-imports#groups> for details.
+
+- Default: See below
+
+```json
+[
+  "type-import",
+  ["value-builtin", "value-external"],
+  "type-internal",
+  "value-internal",
+  ["type-parent", "type-sibling", "type-index"],
+  ["value-parent", "value-sibling", "value-index"],
+  "unknown"
+]
+```
+
+####### overrides[n].options.experimentalSortImports.groups[n]
+
+type: `array | string`
+
+######## overrides[n].options.experimentalSortImports.groups[n][n]
+
+type: `string`
+
+###### overrides[n].options.experimentalSortImports.ignoreCase
+
+type: `boolean`
+
+Specifies whether sorting should be case-sensitive.
+
+- Default: `true`
+
+###### overrides[n].options.experimentalSortImports.internalPattern
+
+type: `string[]`
+
+Specifies a prefix for identifying internal imports.
 
-How to wrap object literals when they could fit on one line or span multiple lines. (Default: `"preserve"`)
+This is useful for distinguishing your own modules from external dependencies.
+
+- Default: `["~/", "@/"]`
+
+###### overrides[n].options.experimentalSortImports.newlinesBetween
+
+type: `boolean`
+
+Specifies whether to add newlines between groups.
+
+When `false`, no newlines are added between groups.
+
+- Default: `true`
+
+###### overrides[n].options.experimentalSortImports.order
+
+type: `"asc" | "desc"`
+
+Specifies whether to sort items in ascending or descending order.
+
+- Default: `"asc"`
+
+###### overrides[n].options.experimentalSortImports.partitionByComment
+
+type: `boolean`
+
+Enables the use of comments to separate imports into logical groups.
+
+When `true`, all comments will be treated as delimiters, creating partitions.
+
+```js
+import { b1, b2 } from "b";
+// PARTITION
+import { a } from "a";
+import { c } from "c";
+```
+
+- Default: `false`
+
+###### overrides[n].options.experimentalSortImports.partitionByNewline
+
+type: `boolean`
+
+Enables the empty line to separate imports into logical groups.
+
+When `true`, formatter will not sort imports if there is an empty line between them.
+This helps maintain the defined order of logically separated groups of members.
+
+```js
+import { b1, b2 } from "b";
+
+import { a } from "a";
+import { c } from "c";
+```
+
+- Default: `false`
+
+###### overrides[n].options.experimentalSortImports.sortSideEffects
+
+type: `boolean`
+
+Specifies whether side effect imports should be sorted.
+
+By default, sorting side-effect imports is disabled for security reasons.
+
+- Default: `false`
+
+##### overrides[n].options.experimentalSortPackageJson
+
+type: `object | boolean`
+
+Experimental: Sort `package.json` keys.
+
+The algorithm is NOT compatible with [prettier-plugin-sort-packagejson](https://github.com/matzkoh/prettier-plugin-packagejson).
+But we believe it is clearer and easier to navigate.
+For details, see each field's documentation.
+
+- Default: `true`
+
+###### overrides[n].options.experimentalSortPackageJson.sortScripts
+
+type: `boolean`
+
+Sort the `scripts` field alphabetically.
+
+- Default: `false`
+
+##### overrides[n].options.experimentalTailwindcss
+
+type: `object`
+
+Experimental: Sort Tailwind CSS classes.
+
+Using the same algorithm as [prettier-plugin-tailwindcss](https://github.com/tailwindlabs/prettier-plugin-tailwindcss).
+Option names omit the `tailwind` prefix used in the original plugin (e.g., `config` instead of `tailwindConfig`).
+For details, see each field's documentation.
+
+- Default: Disabled
+
+###### overrides[n].options.experimentalTailwindcss.attributes
+
+type: `string[]`
+
+List of attribute prefixes that contain Tailwind CSS classes.
+
+NOTE: Regex patterns are not yet supported.
+
+- Default: `["class", "className"]`
+- Example: `["myClassProp", ":class"]`
+
+###### overrides[n].options.experimentalTailwindcss.config
+
+type: `string`
+
+Path to your Tailwind CSS configuration file (v3).
+
+NOTE: Paths are resolved relative to the Oxfmt configuration file.
+
+- Default: Automatically find `"tailwind.config.js"`
+
+###### overrides[n].options.experimentalTailwindcss.functions
+
+type: `string[]`
+
+List of custom function name prefixes that contain Tailwind CSS classes.
+
+NOTE: Regex patterns are not yet supported.
+
+- Default: `[]`
+- Example: `["clsx", "cn", "cva", "tw"]`
+
+###### overrides[n].options.experimentalTailwindcss.preserveDuplicates
+
+type: `boolean`
+
+Preserve duplicate classes.
+
+- Default: `false`
+
+###### overrides[n].options.experimentalTailwindcss.preserveWhitespace
+
+type: `boolean`
+
+Preserve whitespace around classes.
+
+- Default: `false`
+
+###### overrides[n].options.experimentalTailwindcss.stylesheet
+
+type: `string`
+
+Path to your Tailwind CSS stylesheet (v4).
+
+NOTE: Paths are resolved relative to the Oxfmt configuration file.
+
+- Default: Installed Tailwind CSS's `theme.css`
+
+##### overrides[n].options.htmlWhitespaceSensitivity
+
+type: `"css" | "strict" | "ignore"`
+
+Specify the global whitespace sensitivity for HTML, Vue, Angular, and Handlebars.
+
+- Default: `"css"`
+
+##### overrides[n].options.insertFinalNewline
+
+type: `boolean`
+
+Whether to insert a final newline at the end of the file.
+
+- Default: `true`
+- Overrides `.editorconfig.insert_final_newline`
+
+##### overrides[n].options.jsxSingleQuote
+
+type: `boolean`
+
+Use single quotes instead of double quotes in JSX.
+
+- Default: `false`
+
+##### overrides[n].options.objectWrap
+
+type: `"preserve" | "collapse"`
+
+How to wrap object literals when they could fit on one line or span multiple lines.
+
+By default, formats objects as multi-line if there is a newline prior to the first property.
+Authors can use this heuristic to contextually improve readability, though it has some downsides.
+
+- Default: `"preserve"`
+
+##### overrides[n].options.printWidth
+
+type: `integer`
+
+Specify the line length that the printer will wrap on.
+
+If you don't want line wrapping when formatting Markdown, you can set the `proseWrap` option to disable it.
+
+- Default: `100`
+- Overrides `.editorconfig.max_line_length`
+
+##### overrides[n].options.proseWrap
+
+type: `"always" | "never" | "preserve"`
+
+How to wrap prose.
+
+By default, formatter will not change wrapping in markdown text since some services use a linebreak-sensitive renderer, e.g. GitHub comments and BitBucket.
+To wrap prose to the print width, change this option to "always".
+If you want to force all prose blocks to be on a single line and rely on editor/viewer soft wrapping instead, you can use "never".
+
+- Default: `"preserve"`
+
+##### overrides[n].options.quoteProps
+
+type: `"as-needed" | "consistent" | "preserve"`
+
+Change when properties in objects are quoted.
+
+- Default: `"as-needed"`
+
+##### overrides[n].options.semi
+
+type: `boolean`
+
+Print semicolons at the ends of statements.
+
+- Default: `true`
+
+##### overrides[n].options.singleAttributePerLine
+
+type: `boolean`
+
+Enforce single attribute per line in HTML, Vue, and JSX.
+
+- Default: `false`
+
+##### overrides[n].options.singleQuote
+
+type: `boolean`
+
+Use single quotes instead of double quotes.
+
+For JSX, you can set the `jsxSingleQuote` option.
+
+- Default: `false`
+
+##### overrides[n].options.tabWidth
+
+type: `integer`
+
+Specify the number of spaces per indentation-level.
+
+- Default: `2`
+- Overrides `.editorconfig.indent_size`
+
+##### overrides[n].options.trailingComma
+
+type: `"all" | "es5" | "none"`
+
+Print trailing commas wherever possible in multi-line comma-separated syntactic structures.
+
+A single-line array, for example, never gets trailing commas.
+
+- Default: `"all"`
+
+##### overrides[n].options.useTabs
+
+type: `boolean`
+
+Indent lines with tabs instead of spaces.
+
+- Default: `false`
+- Overrides `.editorconfig.indent_style`
+
+##### overrides[n].options.vueIndentScriptAndStyle
+
+type: `boolean`
+
+Whether or not to indent the code inside `<script>` and `<style>` tags in Vue files.
+
+- Default: `false`
 
 ## printWidth
 
-type: `integer | null`
+type: `integer`
+
+Specify the line length that the printer will wrap on.
 
-The line length that the printer will wrap on. (Default: `100`)
+If you don't want line wrapping when formatting Markdown, you can set the `proseWrap` option to disable it.
+
+- Default: `100`
+- Overrides `.editorconfig.max_line_length`
+
+## proseWrap
+
+type: `"always" | "never" | "preserve"`
+
+How to wrap prose.
+
+By default, formatter will not change wrapping in markdown text since some services use a linebreak-sensitive renderer, e.g. GitHub comments and BitBucket.
+To wrap prose to the print width, change this option to "always".
+If you want to force all prose blocks to be on a single line and rely on editor/viewer soft wrapping instead, you can use "never".
+
+- Default: `"preserve"`
 
 ## quoteProps
 
-type: `"as-needed" | "consistent" | "preserve" | null`
+type: `"as-needed" | "consistent" | "preserve"`
+
+Change when properties in objects are quoted.
 
-Change when properties in objects are quoted. (Default: `"as-needed"`)
+- Default: `"as-needed"`
 
 ## semi
 
-type: `boolean | null`
+type: `boolean`
+
+Print semicolons at the ends of statements.
 
-Print semicolons at the ends of statements. (Default: `true`)
+- Default: `true`
 
 ## singleAttributePerLine
 
-type: `boolean | null`
+type: `boolean`
 
-Put each attribute on a new line in JSX. (Default: `false`)
+Enforce single attribute per line in HTML, Vue, and JSX.
+
+- Default: `false`
 
 ## singleQuote
 
-type: `boolean | null`
+type: `boolean`
+
+Use single quotes instead of double quotes.
 
-Use single quotes instead of double quotes. (Default: `false`)
+For JSX, you can set the `jsxSingleQuote` option.
+
+- Default: `false`
 
 ## tabWidth
 
-type: `integer | null`
+type: `integer`
+
+Specify the number of spaces per indentation-level.
 
-Number of spaces per indentation level. (Default: `2`)
+- Default: `2`
+- Overrides `.editorconfig.indent_size`
 
 ## trailingComma
 
-type: `"all" | "es5" | "none" | null`
+type: `"all" | "es5" | "none"`
+
+Print trailing commas wherever possible in multi-line comma-separated syntactic structures.
 
-Print trailing commas wherever possible. (Default: `"all"`)
+A single-line array, for example, never gets trailing commas.
+
+- Default: `"all"`
 
 ## useTabs
 
-type: `boolean | null`
+type: `boolean`
+
+Indent lines with tabs instead of spaces.
+
+- Default: `false`
+- Overrides `.editorconfig.indent_style`
+
+## vueIndentScriptAndStyle
+
+type: `boolean`
+
+Whether or not to indent the code inside `<script>` and `<style>` tags in Vue files.
 
-Use tabs for indentation or spaces. (Default: `false`)
+- Default: `false`
diff --git a/src/docs/guide/usage/linter/generated-config.md b/src/docs/guide/usage/linter/generated-config.md
index e07392fb8d6..9b94c4474c2 100644
--- a/src/docs/guide/usage/linter/generated-config.md
+++ b/src/docs/guide/usage/linter/generated-config.md
@@ -52,7 +52,7 @@ Example
 
 ## $schema
 
-type: `string | null`
+type: `string`
 
 Schema URI for editor tooling.
 
@@ -149,7 +149,7 @@ Globs to ignore during linting. These are resolved from the configuration file p
 
 ## jsPlugins
 
-type: `array | null`
+type: `array`
 
 JS plugins, allows usage of ESLint plugins with Oxlint.
 
@@ -205,7 +205,7 @@ type: `object`
 
 #### overrides[n].env
 
-type: `object | null`
+type: `object`
 
 Environments enable and disable collections of global variables.
 
@@ -217,13 +217,13 @@ A set of glob patterns.
 
 #### overrides[n].globals
 
-type: `object | null`
+type: `object`
 
 Enabled or disabled specific global variables.
 
 #### overrides[n].jsPlugins
 
-type: `array | null`
+type: `array`
 
 JS plugins for this override, allows usage of ESLint plugins with Oxlint.
 
@@ -271,7 +271,7 @@ Path or package name of the plugin
 
 #### overrides[n].plugins
 
-type: `array | null`
+type: `array`
 
 default: `null`
 
@@ -290,7 +290,7 @@ See [Oxlint Rules](https://oxc.rs/docs/guide/usage/linter/rules.html)
 
 ## plugins
 
-type: `array | null`
+type: `array`
 
 default: `null`
 
@@ -468,7 +468,7 @@ Example:
 
 #### settings.jsx-a11y.polymorphicPropName
 
-type: `string | null`
+type: `string`
 
 An optional setting that define the prop your code uses to create polymorphic components.
 This setting will be used to determine the element type in rules that
@@ -584,7 +584,7 @@ type: `string`
 
 #### settings.react.version
 
-type: `string | null`
+type: `string`
 
 default: `null`
 
diff --git a/src/docs/guide/usage/linter/rules/eslint/capitalized-comments.md b/src/docs/guide/usage/linter/rules/eslint/capitalized-comments.md
index 7839d209057..965346dce73 100644
--- a/src/docs/guide/usage/linter/rules/eslint/capitalized-comments.md
+++ b/src/docs/guide/usage/linter/rules/eslint/capitalized-comments.md
@@ -47,47 +47,47 @@ This rule accepts a configuration object with the following properties:
 
 ### block
 
-type: `object | null`
+type: `object`
 
 #### block.ignoreConsecutiveComments
 
-type: `boolean | null`
+type: `boolean`
 
 #### block.ignoreInlineComments
 
-type: `boolean | null`
+type: `boolean`
 
 #### block.ignorePattern
 
-type: `string | null`
+type: `string`
 
 ### ignoreConsecutiveComments
 
-type: `boolean | null`
+type: `boolean`
 
 ### ignoreInlineComments
 
-type: `boolean | null`
+type: `boolean`
 
 ### ignorePattern
 
-type: `string | null`
+type: `string`
 
 ### line
 
-type: `object | null`
+type: `object`
 
 #### line.ignoreConsecutiveComments
 
-type: `boolean | null`
+type: `boolean`
 
 #### line.ignoreInlineComments
 
-type: `boolean | null`
+type: `boolean`
 
 #### line.ignorePattern
 
-type: `string | null`
+type: `string`
 
 ## How to use
 
diff --git a/src/docs/guide/usage/linter/rules/eslint/default-case.md b/src/docs/guide/usage/linter/rules/eslint/default-case.md
index f5e16f7cbd5..d7fad598faa 100644
--- a/src/docs/guide/usage/linter/rules/eslint/default-case.md
+++ b/src/docs/guide/usage/linter/rules/eslint/default-case.md
@@ -73,7 +73,7 @@ This rule accepts a configuration object with the following properties:
 
 ### commentPattern
 
-type: `string | null`
+type: `string`
 
 A regex pattern used to detect comments that mark the absence
 of a `default` case as intentional.
diff --git a/src/docs/guide/usage/linter/rules/eslint/eqeqeq.md b/src/docs/guide/usage/linter/rules/eslint/eqeqeq.md
index ce553dbe3ed..824b5899b86 100644
--- a/src/docs/guide/usage/linter/rules/eslint/eqeqeq.md
+++ b/src/docs/guide/usage/linter/rules/eslint/eqeqeq.md
@@ -62,7 +62,7 @@ Example JSON configuration:
 Examples of **incorrect** code for this rule:
 
 ```js
-/* eslint eqeqeq: "error" */
+/* eqeqeq: "error" */
 
 if (x == 42) {
 }
@@ -75,7 +75,7 @@ if (obj.getStuff() != undefined) {
 Examples of **correct** code for this rule:
 
 ```js
-/* eslint eqeqeq: "error" */
+/* eqeqeq: "error" */
 
 if (x === 42) {
 }
@@ -90,7 +90,7 @@ if (obj.getStuff() !== undefined) {
 Examples of **incorrect** code for this rule with the `"smart"` option:
 
 ```js
-/* eslint eqeqeq: ["error", "smart"] */
+/* eqeqeq: ["error", "smart"] */
 
 if (x == 42) {
 }
@@ -101,7 +101,7 @@ if ("" == text) {
 Examples of **correct** code for this rule with the `"smart"` option:
 
 ```js
-/* eslint eqeqeq: ["error", "smart"] */
+/* eqeqeq: ["error", "smart"] */
 
 if (typeof foo == "undefined") {
 }
@@ -116,7 +116,7 @@ if (foo != null) {
 Examples of **incorrect** code for this rule with the `{ "null": "ignore" }` option:
 
 ```js
-/* eslint eqeqeq: ["error", "always", { "null": "ignore" }] */
+/* eqeqeq: ["error", "always", { "null": "ignore" }] */
 if (x == 42) {
 }
 if ("" == text) {
@@ -126,7 +126,7 @@ if ("" == text) {
 Examples of **correct** code for this rule with the `{ "null": "ignore" }` option:
 
 ```js
-/* eslint eqeqeq: ["error", "always", { "null": "ignore" }] */
+/* eqeqeq: ["error", "always", { "null": "ignore" }] */
 if (foo == null) {
 }
 if (foo != null) {
@@ -138,7 +138,7 @@ if (foo != null) {
 Examples of **incorrect** code for this rule with the `{ "null": "always" }` option:
 
 ```js
-/* eslint eqeqeq: ["error", "always", { "null": "always" }] */
+/* eqeqeq: ["error", "always", { "null": "always" }] */
 
 if (foo == null) {
 }
@@ -149,7 +149,7 @@ if (foo != null) {
 Examples of **correct** code for this rule with the `{ "null": "always" }` option:
 
 ```js
-/* eslint eqeqeq: ["error", "always", { "null": "always" }] */
+/* eqeqeq: ["error", "always", { "null": "always" }] */
 
 if (foo === null) {
 }
@@ -162,7 +162,7 @@ if (foo !== null) {
 Examples of **incorrect** code for this rule with the `{ "null": "never" }` option:
 
 ```js
-/* eslint eqeqeq: ["error", "always", { "null": "never" }] */
+/* eqeqeq: ["error", "always", { "null": "never" }] */
 
 if (x == 42) {
 }
@@ -177,7 +177,7 @@ if (foo !== null) {
 Examples of **correct** code for this rule with the `{ "null": "never" }` option:
 
 ```js
-/* eslint eqeqeq: ["error", "always", { "null": "never" }] */
+/* eqeqeq: ["error", "always", { "null": "never" }] */
 
 if (x === 42) {
 }
diff --git a/src/docs/guide/usage/linter/rules/eslint/func-style.md b/src/docs/guide/usage/linter/rules/eslint/func-style.md
index b50f28074ea..d4d45c656c4 100644
--- a/src/docs/guide/usage/linter/rules/eslint/func-style.md
+++ b/src/docs/guide/usage/linter/rules/eslint/func-style.md
@@ -17,7 +17,7 @@ const source = `https://github.com/oxc-project/oxc/blob/${ data }/crates/oxc_lin
 
 ### What it does
 
-Enforce the consistent use of either function declarations or expressions assigned to variables
+Enforce the consistent use of either function declarations or expressions assigned to variables.
 
 ### Why is this bad?
 
@@ -43,20 +43,20 @@ const doSomethingAgain = function () {
 };
 ```
 
-Examples of incorrect code for this rule with the default "expression" option:
+Examples of **incorrect** code for this rule with the default `"expression"` option:
 
 ```js
-/*eslint func-style: ["error", "expression"]*/
+/* func-style: ["error", "expression"] */
 
 function foo() {
   // ...
 }
 ```
 
-Examples of incorrect code for this rule with the "declaration" option:
+Examples of **incorrect** code for this rule with the `"declaration"` option:
 
 ```js
-/*eslint func-style: ["error", "declaration"]*/
+/* func-style: ["error", "declaration"] */
 var foo = function () {
   // ...
 };
@@ -64,19 +64,19 @@ var foo = function () {
 var foo = () => {};
 ```
 
-Examples of incorrect code for this rule with the "declaration" and {"overrides": { "namedExports": "expression" }} option:
+Examples of **incorrect** code for this rule with the `"declaration"` and `{"overrides": { "namedExports": "expression" }}` option:
 
 ```js
-/*eslint func-style: ["error", "declaration", { "overrides": { "namedExports": "expression" } }]*/
+/* func-style: ["error", "declaration", { "overrides": { "namedExports": "expression" } }] */
 export function foo() {
   // ...
 }
 ```
 
-Examples of incorrect code for this rule with the "expression" and {"overrides": { "namedExports": "declaration" }} option:
+Examples of **incorrect** code for this rule with the `"expression"` and `{"overrides": { "namedExports": "declaration" }}` option:
 
 ```js
-/*eslint func-style: ["error", "expression", { "overrides": { "namedExports": "declaration" } }]*/
+/* func-style: ["error", "expression", { "overrides": { "namedExports": "declaration" } }] */
 export var foo = function () {
   // ...
 };
@@ -84,19 +84,19 @@ export var foo = function () {
 export var bar = () => {};
 ```
 
-Examples of correct code for this rule with the default "expression" option:
+Examples of **correct** code for this rule with the default `"expression"` option:
 
 ```js
-/*eslint func-style: ["error", "expression"]*/
+/* func-style: ["error", "expression"] */
 var foo = function () {
   // ...
 };
 ```
 
-Examples of correct code for this rule with the "declaration" option:
+Examples of **correct** code for this rule with the `"declaration"` option:
 
 ```js
-/*eslint func-style: ["error", "declaration"]*/
+/* func-style: ["error", "declaration"] */
 function foo() {
   // ...
 }
@@ -106,36 +106,36 @@ SomeObject.foo = function () {
 };
 ```
 
-Examples of additional correct code for this rule with the "declaration", { "allowArrowFunctions": true } options:
+Examples of additional correct code for this rule with the `"declaration"`, `{ "allowArrowFunctions": true }` options:
 
 ```js
-/*eslint func-style: ["error", "declaration", { "allowArrowFunctions": true }]*/
+/* func-style: ["error", "declaration", { "allowArrowFunctions": true }] */
 var foo = () => {};
 ```
 
-Examples of correct code for this rule with the "declaration" and {"overrides": { "namedExports": "expression" }} option:
+Examples of **correct** code for this rule with the `"declaration"` and `{"overrides": { "namedExports": "expression" }}` option:
 
 ```js
-/*eslint func-style: ["error", "declaration", { "overrides": { "namedExports": "expression" } }]*/
+/* func-style: ["error", "declaration", { "overrides": { "namedExports": "expression" } }] */
 export var foo = function () {
   // ...
 };
 export var bar = () => {};
 ```
 
-Examples of correct code for this rule with the "expression" and {"overrides": { "namedExports": "declaration" }} option:
+Examples of **correct** code for this rule with the `"expression"` and `{"overrides": { "namedExports": "declaration" }}` option:
 
 ```js
-/*eslint func-style: ["error", "expression", { "overrides": { "namedExports": "declaration" } }]*/
+/* func-style: ["error", "expression", { "overrides": { "namedExports": "declaration" } }] */
 export function foo() {
   // ...
 }
 ```
 
-Examples of correct code for this rule with the {"overrides": { "namedExports": "ignore" }} option:
+Examples of **correct** code for this rule with the `{"overrides": { "namedExports": "ignore" }}` option:
 
 ```js
-/*eslint func-style: ["error", "expression", { "overrides": { "namedExports": "ignore" } }]*/
+/* func-style: ["error", "expression", { "overrides": { "namedExports": "ignore" } }] */
 export var foo = function () {
   // ...
 };
@@ -168,7 +168,7 @@ When true, functions with type annotations are allowed regardless of the style s
 
 ### namedExports
 
-type: `"ignore" | "expression" | "declaration" | null`
+type: `"ignore" | "expression" | "declaration"`
 
 default: `null`
 
diff --git a/src/docs/guide/usage/linter/rules/eslint/id-length.md b/src/docs/guide/usage/linter/rules/eslint/id-length.md
index 30615755ed2..2a3d5a620ce 100644
--- a/src/docs/guide/usage/linter/rules/eslint/id-length.md
+++ b/src/docs/guide/usage/linter/rules/eslint/id-length.md
@@ -31,7 +31,7 @@ maintainable. To prevent this, one may enforce a minimum and/or maximum identifi
 Examples of **incorrect** code for this rule:
 
 ```js
-/*eslint id-length: "error"*/ // default is minimum 2-chars ({ "min": 2 })
+/* id-length: "error" */ // default is minimum 2-chars ({ "min": 2 })
 
 const x = 5;
 obj.e = document.body;
@@ -73,7 +73,7 @@ const { prop: a } = {};
 Examples of **correct** code for this rule:
 
 ```js
-/*eslint id-length: "error"*/ // default is minimum 2-chars ({ "min": 2 })
+/* id-length: "error" */ // default is minimum 2-chars ({ "min": 2 })
 
 const num = 5;
 function _f() {
diff --git a/src/docs/guide/usage/linter/rules/eslint/init-declarations.md b/src/docs/guide/usage/linter/rules/eslint/init-declarations.md
index bfeaeb33dce..200ef47793f 100644
--- a/src/docs/guide/usage/linter/rules/eslint/init-declarations.md
+++ b/src/docs/guide/usage/linter/rules/eslint/init-declarations.md
@@ -22,32 +22,34 @@ Require or disallow initialization in variable declarations
 ### Why is this bad?
 
 In JavaScript, variables can be assigned during declaration, or at any point afterwards using an assignment statement.
-For example, in the following code, foo is initialized during declaration, while bar is initialized later.
-
-### Examples
+For example, in the following code, `foo` is initialized during declaration, while `bar` is initialized later.
 
+```js
 var foo = 1;
 var bar;
 if (foo) {
-bar = 1;
+  bar = 1;
 } else {
-bar = 2;
+  bar = 2;
 }
+```
+
+### Examples
 
-Examples of incorrect code for the default "always" option:
+Examples of incorrect code for the default `"always"` option:
 
 ```js
-/*eslint init-declarations: ["error", "always"]*/
+/* init-declarations: ["error", "always"] */
 function foo() {
   var bar;
   let baz;
 }
 ```
 
-Examples of incorrect code for the "never" option:
+Examples of incorrect code for the `"never"` option:
 
 ```js
-/*eslint init-declarations: ["error", "never"]*/
+/* init-declarations: ["error", "never"] */
 function foo() {
   var bar = 1;
   let baz = 2;
@@ -55,10 +57,10 @@ function foo() {
 }
 ```
 
-Examples of correct code for the default "always" option:
+Examples of correct code for the default `"always"` option:
 
 ```js
-/*eslint init-declarations: ["error", "always"]*/
+/* init-declarations: ["error", "always"] */
 
 function foo() {
   var bar = 1;
@@ -67,10 +69,10 @@ function foo() {
 }
 ```
 
-Examples of correct code for the "never" option:
+Examples of correct code for the `"never"` option:
 
 ```js
-/*eslint init-declarations: ["error", "never"]*/
+/* init-declarations: ["error", "never"] */
 
 function foo() {
   var bar;
@@ -79,10 +81,10 @@ function foo() {
 }
 ```
 
-Examples of correct code for the "never", { "ignoreForLoopInit": true } options:
+Examples of correct code for the `"never", { "ignoreForLoopInit": true }` options:
 
 ```js
-/*eslint init-declarations: ["error", "never", { "ignoreForLoopInit": true }]*/
+/* init-declarations: ["error", "never", { "ignoreForLoopInit": true }] */
 for (var i = 0; i < 1; i++) {}
 ```
 
diff --git a/src/docs/guide/usage/linter/rules/eslint/new-cap.md b/src/docs/guide/usage/linter/rules/eslint/new-cap.md
index 3c72a3ec148..717453cbf1e 100644
--- a/src/docs/guide/usage/linter/rules/eslint/new-cap.md
+++ b/src/docs/guide/usage/linter/rules/eslint/new-cap.md
@@ -48,7 +48,7 @@ function foo(arg) {
 Examples of **incorrect** code for this rule with the default `{ "newIsCap": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCap": true }]*/
+/* new-cap: ["error", { "newIsCap": true }] */
 
 var friend = new person();
 ```
@@ -56,7 +56,7 @@ var friend = new person();
 Examples of **correct** code for this rule with the default `{ "newIsCap": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCap": true }]*/
+/* new-cap: ["error", { "newIsCap": true }] */
 
 var friend = new Person();
 ```
@@ -64,7 +64,7 @@ var friend = new Person();
 Examples of **correct** code for this rule with the `{ "newIsCap": false }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCap": false }]*/
+/* new-cap: ["error", { "newIsCap": false }] */
 
 var friend = new person();
 ```
@@ -72,7 +72,7 @@ var friend = new person();
 Examples of **incorrect** code for this rule with the default `{ "capIsNew": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNew": true }]*/
+/* new-cap: ["error", { "capIsNew": true }] */
 
 var colleague = Person();
 ```
@@ -80,7 +80,7 @@ var colleague = Person();
 Examples of **correct** code for this rule with the default `{ "capIsNew": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNew": true }]*/
+/* new-cap: ["error", { "capIsNew": true }] */
 
 var colleague = new Person();
 ```
@@ -88,7 +88,7 @@ var colleague = new Person();
 Examples of **correct** code for this rule with the `{ "capIsNew": false }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNew": false }]*/
+/* new-cap: ["error", { "capIsNew": false }] */
 
 var colleague = Person();
 ```
@@ -96,7 +96,7 @@ var colleague = Person();
 Examples of additional **correct** code for this rule with the `{ "newIsCapExceptions": ["events"] }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCapExceptions": ["events"] }]*/
+/* new-cap: ["error", { "newIsCapExceptions": ["events"] }] */
 
 var events = require("events");
 
@@ -106,7 +106,7 @@ var emitter = new events();
 Examples of additional **correct** code for this rule with the `{ "newIsCapExceptionPattern": "^person\\.." }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCapExceptionPattern": "^person\\.." }]*/
+/* new-cap: ["error", { "newIsCapExceptionPattern": "^person\\.." }] */
 
 var friend = new person.acquaintance();
 
@@ -116,7 +116,7 @@ var bestFriend = new person.friend();
 Examples of additional **correct** code for this rule with the `{ "newIsCapExceptionPattern": "\\.bar$" }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCapExceptionPattern": "\\.bar$" }]*/
+/* new-cap: ["error", { "newIsCapExceptionPattern": "\\.bar$" }] */
 
 var friend = new person.bar();
 ```
@@ -124,7 +124,7 @@ var friend = new person.bar();
 Examples of additional **correct** code for this rule with the `{ "capIsNewExceptions": ["Person"] }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNewExceptions": ["Person"] }]*/
+/* new-cap: ["error", { "capIsNewExceptions": ["Person"] }] */
 
 function foo(arg) {
   return Person(arg);
@@ -134,7 +134,7 @@ function foo(arg) {
 Examples of additional **correct** code for this rule with the `{ "capIsNewExceptionPattern": "^person\\.." }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNewExceptionPattern": "^person\\.." }]*/
+/* new-cap: ["error", { "capIsNewExceptionPattern": "^person\\.." }] */
 
 var friend = person.Acquaintance();
 var bestFriend = person.Friend();
@@ -143,7 +143,7 @@ var bestFriend = person.Friend();
 Examples of additional **correct** code for this rule with the `{ "capIsNewExceptionPattern": "\\.Bar$" }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNewExceptionPattern": "\\.Bar$" }]*/
+/* new-cap: ["error", { "capIsNewExceptionPattern": "\\.Bar$" }] */
 
 foo.Bar();
 ```
@@ -151,7 +151,7 @@ foo.Bar();
 Examples of additional **correct** code for this rule with the `{ "capIsNewExceptionPattern": "^Foo" }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNewExceptionPattern": "^Foo" }]*/
+/* new-cap: ["error", { "capIsNewExceptionPattern": "^Foo" }] */
 
 var x = Foo(42);
 
@@ -165,7 +165,7 @@ var z = Foo.Bar(42);
 Examples of **incorrect** code for this rule with the default `{ "properties": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "properties": true }]*/
+/* new-cap: ["error", { "properties": true }] */
 
 var friend = new person.acquaintance();
 ```
@@ -173,7 +173,7 @@ var friend = new person.acquaintance();
 Examples of **correct** code for this rule with the default `{ "properties": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "properties": true }]*/
+/* new-cap: ["error", { "properties": true }] */
 
 var friend = new person.Acquaintance();
 ```
@@ -181,7 +181,7 @@ var friend = new person.Acquaintance();
 Examples of **correct** code for this rule with the `{ "properties": false }` option:
 
 ```js
-/*eslint new-cap: ["error", { "properties": false }]*/
+/* new-cap: ["error", { "properties": false }] */
 
 var friend = new person.acquaintance();
 ```
@@ -189,7 +189,7 @@ var friend = new person.acquaintance();
 Examples of **incorrect** code for this rule with the default `{ "newIsCap": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCap": true }]*/
+/* new-cap: ["error", { "newIsCap": true }] */
 
 var friend = new person();
 ```
@@ -197,7 +197,7 @@ var friend = new person();
 Examples of **correct** code for this rule with the default `{ "newIsCap": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCap": true }]*/
+/* new-cap: ["error", { "newIsCap": true }] */
 
 var friend = new Person();
 ```
@@ -205,7 +205,7 @@ var friend = new Person();
 Examples of **correct** code for this rule with the `{ "newIsCap": false }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCap": false }]*/
+/* new-cap: ["error", { "newIsCap": false }] */
 
 var friend = new person();
 ```
@@ -213,7 +213,7 @@ var friend = new person();
 Examples of **incorrect** code for this rule with the default `{ "capIsNew": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNew": true }]*/
+/* new-cap: ["error", { "capIsNew": true }] */
 
 var colleague = Person();
 ```
@@ -221,7 +221,7 @@ var colleague = Person();
 Examples of **correct** code for this rule with the default `{ "capIsNew": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNew": true }]*/
+/* new-cap: ["error", { "capIsNew": true }] */
 
 var colleague = new Person();
 ```
@@ -229,7 +229,7 @@ var colleague = new Person();
 Examples of **correct** code for this rule with the `{ "capIsNew": false }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNew": false }]*/
+/* new-cap: ["error", { "capIsNew": false }] */
 
 var colleague = Person();
 ```
@@ -237,7 +237,7 @@ var colleague = Person();
 Examples of additional **correct** code for this rule with the `{ "newIsCapExceptions": ["events"] }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCapExceptions": ["events"] }]*/
+/* new-cap: ["error", { "newIsCapExceptions": ["events"] }] */
 
 var events = require("events");
 
@@ -247,7 +247,7 @@ var emitter = new events();
 Examples of additional **correct** code for this rule with the `{ "newIsCapExceptionPattern": "^person\\.." }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCapExceptionPattern": "^person\\.." }]*/
+/* new-cap: ["error", { "newIsCapExceptionPattern": "^person\\.." }] */
 
 var friend = new person.acquaintance();
 
@@ -257,7 +257,7 @@ var bestFriend = new person.friend();
 Examples of additional **correct** code for this rule with the `{ "newIsCapExceptionPattern": "\\.bar$" }` option:
 
 ```js
-/*eslint new-cap: ["error", { "newIsCapExceptionPattern": "\\.bar$" }]*/
+/* new-cap: ["error", { "newIsCapExceptionPattern": "\\.bar$" }] */
 
 var friend = new person.bar();
 ```
@@ -267,7 +267,7 @@ Examples of additional **correct** code for this rule with the `{ "capIsNewExcep
 ::: correct
 
 ```js
-/*eslint new-cap: ["error", { "capIsNewExceptions": ["Person"] }]*/
+/* new-cap: ["error", { "capIsNewExceptions": ["Person"] }] */
 
 function foo(arg) {
   return Person(arg);
@@ -277,7 +277,7 @@ function foo(arg) {
 Examples of additional **correct** code for this rule with the `{ "capIsNewExceptionPattern": "^person\\.." }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNewExceptionPattern": "^person\\.." }]*/
+/* new-cap: ["error", { "capIsNewExceptionPattern": "^person\\.." }] */
 
 var friend = person.Acquaintance();
 var bestFriend = person.Friend();
@@ -286,7 +286,7 @@ var bestFriend = person.Friend();
 Examples of additional **correct** code for this rule with the `{ "capIsNewExceptionPattern": "\\.Bar$" }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNewExceptionPattern": "\\.Bar$" }]*/
+/* new-cap: ["error", { "capIsNewExceptionPattern": "\\.Bar$" }] */
 
 foo.Bar();
 ```
@@ -294,7 +294,7 @@ foo.Bar();
 Examples of additional **correct** code for this rule with the `{ "capIsNewExceptionPattern": "^Foo" }` option:
 
 ```js
-/*eslint new-cap: ["error", { "capIsNewExceptionPattern": "^Foo" }]*/
+/* new-cap: ["error", { "capIsNewExceptionPattern": "^Foo" }] */
 
 var x = Foo(42);
 
@@ -306,7 +306,7 @@ var z = Foo.Bar(42);
 Examples of **incorrect** code for this rule with the default `{ "properties": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "properties": true }]*/
+/* new-cap: ["error", { "properties": true }] */
 
 var friend = new person.acquaintance();
 ```
@@ -314,7 +314,7 @@ var friend = new person.acquaintance();
 Examples of **correct** code for this rule with the default `{ "properties": true }` option:
 
 ```js
-/*eslint new-cap: ["error", { "properties": true }]*/
+/* new-cap: ["error", { "properties": true }] */
 
 var friend = new person.Acquaintance();
 ```
@@ -322,7 +322,7 @@ var friend = new person.Acquaintance();
 Examples of **correct** code for this rule with the `{ "properties": false }` option:
 
 ```js
-/*eslint new-cap: ["error", { "properties": false }]*/
+/* new-cap: ["error", { "properties": false }] */
 
 var friend = new person.acquaintance();
 ```
@@ -341,7 +341,7 @@ default: `true`
 
 ### capIsNewExceptionPattern
 
-type: `string | null`
+type: `string`
 
 A regex pattern to match exceptions for functions with names starting with an uppercase letter.
 
@@ -363,7 +363,7 @@ default: `true`
 
 ### newIsCapExceptionPattern
 
-type: `string | null`
+type: `string`
 
 A regex pattern to match exceptions for constructor names starting with an uppercase letter.
 
diff --git a/src/docs/guide/usage/linter/rules/eslint/no-empty-pattern.md b/src/docs/guide/usage/linter/rules/eslint/no-empty-pattern.md
index 3f7d0563236..b7b521c253b 100644
--- a/src/docs/guide/usage/linter/rules/eslint/no-empty-pattern.md
+++ b/src/docs/guide/usage/linter/rules/eslint/no-empty-pattern.md
@@ -17,7 +17,7 @@ const source = `https://github.com/oxc-project/oxc/blob/${ data }/crates/oxc_lin
 
 ### What it does
 
-Disallow empty destructuring patterns
+Disallow empty destructuring patterns.
 
 ### Why is this bad?
 
@@ -49,7 +49,7 @@ var {a = {}} = foo;
 The difference between these two patterns is subtle,
 especially because the problematic empty pattern looks just like an object literal.
 
-### Examples of incorrect code for this rule:
+### Examples of **incorrect** code for this rule:
 
 ```JavaScript
 var {} = foo;
@@ -62,7 +62,7 @@ function foo({a: {}}) {}
 function foo({a: []}) {}
 ```
 
-### Examples of correct code for this rule:
+### Examples of **correct** code for this rule:
 
 ```JavaScript
 var {a = {}} = foo;
diff --git a/src/docs/guide/usage/linter/rules/eslint/no-fallthrough.md b/src/docs/guide/usage/linter/rules/eslint/no-fallthrough.md
index 8f162ae1dcf..b3000b3f37a 100644
--- a/src/docs/guide/usage/linter/rules/eslint/no-fallthrough.md
+++ b/src/docs/guide/usage/linter/rules/eslint/no-fallthrough.md
@@ -200,7 +200,7 @@ Whether to allow empty case clauses to fall through.
 
 ### commentPattern
 
-type: `string | null`
+type: `string`
 
 Custom regex pattern to match fallthrough comments.
 
diff --git a/src/docs/guide/usage/linter/rules/eslint/no-inline-comments.md b/src/docs/guide/usage/linter/rules/eslint/no-inline-comments.md
index 836a5435846..bcda7da07d0 100644
--- a/src/docs/guide/usage/linter/rules/eslint/no-inline-comments.md
+++ b/src/docs/guide/usage/linter/rules/eslint/no-inline-comments.md
@@ -50,7 +50,7 @@ This rule accepts a configuration object with the following properties:
 
 ### ignorePattern
 
-type: `string | null`
+type: `string`
 
 A regex pattern to ignore certain inline comments.
 
diff --git a/src/docs/guide/usage/linter/rules/eslint/no-proto.md b/src/docs/guide/usage/linter/rules/eslint/no-proto.md
index c9bd26ed14f..e91c28ac8d6 100644
--- a/src/docs/guide/usage/linter/rules/eslint/no-proto.md
+++ b/src/docs/guide/usage/linter/rules/eslint/no-proto.md
@@ -33,8 +33,6 @@ For more information, see
 Examples of **incorrect** code for this rule:
 
 ```javascript
-/*eslint no-proto: "error"*/
-
 var a = obj.__proto__;
 
 var a = obj["__proto__"];
diff --git a/src/docs/guide/usage/linter/rules/eslint/no-script-url.md b/src/docs/guide/usage/linter/rules/eslint/no-script-url.md
index 033dc1ba6a0..1de6f94e1c1 100644
--- a/src/docs/guide/usage/linter/rules/eslint/no-script-url.md
+++ b/src/docs/guide/usage/linter/rules/eslint/no-script-url.md
@@ -28,11 +28,9 @@ performance issues.
 
 ### Examples
 
-Examples of **incorrect** code for this rule
+Examples of **incorrect** code for this rule:
 
 ```javascript
-/*eslint no-script-url: "error"*/
-
 location.href = "javascript:void(0)";
 
 location.href = `javascript:void(0)`;
diff --git a/src/docs/guide/usage/linter/rules/eslint/no-unused-vars.md b/src/docs/guide/usage/linter/rules/eslint/no-unused-vars.md
index beaf72825d3..c85c68f1566 100644
--- a/src/docs/guide/usage/linter/rules/eslint/no-unused-vars.md
+++ b/src/docs/guide/usage/linter/rules/eslint/no-unused-vars.md
@@ -87,8 +87,8 @@ standard, Oxlint does not support this feature.
 Examples of **incorrect** code for this rule:
 
 ```javascript
-/*eslint no-unused-vars: "error"*/
-/*global some_unused_var*/
+/* no-unused-vars: "error" */
+/* if you have `some_unused_var` defined as a global in .oxlintrc.json */
 
 // It checks variables you have defined as global
 some_unused_var = 42;
@@ -134,7 +134,7 @@ enum Color {
 Examples of **correct** code for this rule:
 
 ```js
-/*eslint no-unused-vars: "error"*/
+/* no-unused-vars: "error" */
 
 var x = 10;
 alert(x);
@@ -194,15 +194,6 @@ default: `"after-used"`
 
 Controls how unused arguments are checked.
 
-This option has three settings:
-
-1. `after-used` - Unused positional arguments that occur before the last
-   used argument will not be checked, but all named arguments and all
-   positional arguments after the last used argument will be checked.
-   This is the default setting.
-2. `all` - All named arguments must be used.
-3. `none` - Do not check arguments.
-
 #### `"after-used"`
 
 Unused positional arguments that occur before the last used argument
@@ -244,12 +235,13 @@ type: `"all" | "none"`
 
 Used for `catch` block validation.
 
-It has two settings:
+#### `"all"`
 
-- `none` - do not check error objects. This is the default setting.
-- `all` - all named arguments must be used.
+All named arguments must be used.
 
-`none` corresponds to `false`, while `all` corresponds to `true`.
+#### `"none"`
+
+Do not check error objects.
 
 ### caughtErrorsIgnorePattern
 
@@ -467,13 +459,6 @@ default: `"all"`
 
 Controls how usage of a variable in the global scope is checked.
 
-This option has two settings:
-
-1. `all` checks all variables for usage, including those in the global
-   scope. This is the default setting.
-2. `local` checks only that locally-declared variables are used but will
-   allow global variables to be unused.
-
 #### `"all"`
 
 All variables are checked for usage, including those in the global scope.
diff --git a/src/docs/guide/usage/linter/rules/eslint/prefer-spread.md b/src/docs/guide/usage/linter/rules/eslint/prefer-spread.md
index 36a35235366..93a14bd9a0e 100644
--- a/src/docs/guide/usage/linter/rules/eslint/prefer-spread.md
+++ b/src/docs/guide/usage/linter/rules/eslint/prefer-spread.md
@@ -15,15 +15,13 @@ const source = `https://github.com/oxc-project/oxc/blob/${ data }/crates/oxc_lin
 
 <RuleHeader />
 
-This rule is combined 2 rules from `eslint:prefer-spread` and `unicorn:prefer-spread`.
-
 ### What it does
 
-Require spread operators instead of .apply()
+Require spread operators instead of `.apply()`
 
 ### Why is this bad?
 
-Before ES2015, one must use Function.prototype.apply() to call variadic functions.
+Before ES2015, one must use `Function.prototype.apply()` to call variadic functions.
 
 ```javascript
 var args = [1, 2, 3, 4];
diff --git a/src/docs/guide/usage/linter/rules/import/no-absolute-path.md b/src/docs/guide/usage/linter/rules/import/no-absolute-path.md
index 66e10be2a8e..5be7ddef64b 100644
--- a/src/docs/guide/usage/linter/rules/import/no-absolute-path.md
+++ b/src/docs/guide/usage/linter/rules/import/no-absolute-path.md
@@ -75,7 +75,7 @@ default: `false`
 If set to `true`, dependency paths for AMD-style define and require calls will be resolved:
 
 ```js
-/* eslint import/no-absolute-path: ['error', { commonjs: false, amd: true }] */
+/* import/no-absolute-path: ["error", { "commonjs": false, "amd": true }] */
 define(["/foo"], function (foo) {
   /*...*/
 }); // reported
diff --git a/src/docs/guide/usage/linter/rules/import/no-anonymous-default-export.md b/src/docs/guide/usage/linter/rules/import/no-anonymous-default-export.md
index a1ea74ff694..948a6a8032c 100644
--- a/src/docs/guide/usage/linter/rules/import/no-anonymous-default-export.md
+++ b/src/docs/guide/usage/linter/rules/import/no-anonymous-default-export.md
@@ -54,21 +54,21 @@ export default function foo() {};
 export default class MyClass {};
 export default function foo() {};
 export default foo(bar);
-/* eslint import/no-anonymous-default-export: ['error', {"allowLiteral": true}] */
+/* import/no-anonymous-default-export: ["error", { "allowLiteral": true }] */
 export default 123;
-/* eslint import/no-anonymous-default-export: ['error, {"allowArray": true}] */
+/* import/no-anonymous-default-export: ["error", { "allowArray": true }] */
 export default []
-/* eslint import/no-anonymous-default-export: ['error, {"allowArrowFunction": true}] */
+/* import/no-anonymous-default-export: ["error", { "allowArrowFunction": true }] */
 export default () => {};
-/* eslint import/no-anonymous-default-export: ['error, {"allowAnonymousClass": true}] */
+/* import/no-anonymous-default-export: ["error", { "allowAnonymousClass": true }] */
 export default class {};
-/* eslint import/no-anonymous-default-export: ['error, {"allowAnonymousFunction": true}] */
+/* import/no-anonymous-default-export: ["error", { "allowAnonymousFunction": true }] */
 export default function() {};
-/* eslint import/no-anonymous-default-export: ['error, {"allowObject": true}] */
+/* import/no-anonymous-default-export: ["error", { "allowObject": true }] */
 export default {};
-/* eslint import/no-anonymous-default-export: ['error, {"allowNew": true}] */
+/* import/no-anonymous-default-export: ["error", { "allowNew": true }] */
 export default new Foo();
-/* eslint import/no-anonymous-default-export: ['error, {"allowCallExpression": true}] */
+/* import/no-anonymous-default-export: ["error", { "allowCallExpression": true }] */
 export default foo(bar);
 ```
 
diff --git a/src/docs/guide/usage/linter/rules/jest/consistent-test-it.md b/src/docs/guide/usage/linter/rules/jest/consistent-test-it.md
index dd082d7d865..3e7190bcc64 100644
--- a/src/docs/guide/usage/linter/rules/jest/consistent-test-it.md
+++ b/src/docs/guide/usage/linter/rules/jest/consistent-test-it.md
@@ -30,7 +30,7 @@ It's a good practice to be consistent in your test suite, so that all tests are
 ### Examples
 
 ```javascript
-/*eslint jest/consistent-test-it: ["error", {"fn": "test"}]*/
+/* jest/consistent-test-it: ["error", {"fn": "test"}] */
 test("foo"); // valid
 test.only("foo"); // valid
 
@@ -39,7 +39,7 @@ it.only("foo"); // invalid
 ```
 
 ```javascript
-/*eslint jest/consistent-test-it: ["error", {"fn": "it"}]*/
+/* jest/consistent-test-it: ["error", {"fn": "it"}] */
 it("foo"); // valid
 it.only("foo"); // valid
 test("foo"); // invalid
@@ -47,7 +47,7 @@ test.only("foo"); // invalid
 ```
 
 ```javascript
-/*eslint jest/consistent-test-it: ["error", {"fn": "it", "withinDescribe": "test"}]*/
+/* jest/consistent-test-it: ["error", {"fn": "it", "withinDescribe": "test"}] */
 it("foo"); // valid
 describe("foo", function () {
   test("bar"); // valid
diff --git a/src/docs/guide/usage/linter/rules/nextjs/no-duplicate-head.md b/src/docs/guide/usage/linter/rules/nextjs/no-duplicate-head.md
index 9f0d3421477..d4fa7e03241 100644
--- a/src/docs/guide/usage/linter/rules/nextjs/no-duplicate-head.md
+++ b/src/docs/guide/usage/linter/rules/nextjs/no-duplicate-head.md
@@ -17,7 +17,7 @@ const source = `https://github.com/oxc-project/oxc/blob/${ data }/crates/oxc_lin
 
 ### What it does
 
-Prevent duplicate usage of `<Head>` in `pages/\_document.js``.
+Prevent duplicate usage of `<Head>` in `pages/_document.js`.
 
 ### Why is this bad?
 
diff --git a/src/docs/guide/usage/linter/rules/nextjs/no-styled-jsx-in-document.md b/src/docs/guide/usage/linter/rules/nextjs/no-styled-jsx-in-document.md
index 4f34ccdbaba..23c2d5ee3bc 100644
--- a/src/docs/guide/usage/linter/rules/nextjs/no-styled-jsx-in-document.md
+++ b/src/docs/guide/usage/linter/rules/nextjs/no-styled-jsx-in-document.md
@@ -17,7 +17,7 @@ const source = `https://github.com/oxc-project/oxc/blob/${ data }/crates/oxc_lin
 
 ### What it does
 
-Prevent usage of styled-jsx in pages/\_document.js.
+Prevent usage of styled-jsx in `pages/_document.js`.
 
 ### Why is this bad?
 
diff --git a/src/docs/guide/usage/linter/rules/promise/always-return.md b/src/docs/guide/usage/linter/rules/promise/always-return.md
index 67cde9a5101..a82400b3767 100644
--- a/src/docs/guide/usage/linter/rules/promise/always-return.md
+++ b/src/docs/guide/usage/linter/rules/promise/always-return.md
@@ -77,7 +77,7 @@ chain does not warn if it does an assignment to a global variable. Default is
 `["globalThis"]`.
 
 ```javascript
-/* eslint promise/always-return: ["error", { ignoreAssignmentVariable: ["globalThis"] }] */
+/* promise/always-return: ["error", { ignoreAssignmentVariable: ["globalThis"] }] */
 
 // OK
 promise.then((x) => {
diff --git a/src/docs/guide/usage/linter/rules/promise/param-names.md b/src/docs/guide/usage/linter/rules/promise/param-names.md
index 0db31a3a85b..11782ca0abe 100644
--- a/src/docs/guide/usage/linter/rules/promise/param-names.md
+++ b/src/docs/guide/usage/linter/rules/promise/param-names.md
@@ -51,14 +51,14 @@ This rule accepts a configuration object with the following properties:
 
 ### rejectPattern
 
-type: `string | null`
+type: `string`
 
 Regex pattern used to validate the `reject` parameter name. If provided, this pattern
 is used instead of the default `^_?reject$` check.
 
 ### resolvePattern
 
-type: `string | null`
+type: `string`
 
 Regex pattern used to validate the `resolve` parameter name. If provided, this pattern
 is used instead of the default `^_?resolve$` check.
diff --git a/src/docs/guide/usage/linter/rules/react/exhaustive-deps.md b/src/docs/guide/usage/linter/rules/react/exhaustive-deps.md
index bbdd9cf0d87..197b5a0eb3e 100644
--- a/src/docs/guide/usage/linter/rules/react/exhaustive-deps.md
+++ b/src/docs/guide/usage/linter/rules/react/exhaustive-deps.md
@@ -54,7 +54,7 @@ This rule accepts a configuration object with the following properties:
 
 ### additionalHooks
 
-type: `string | null`
+type: `string`
 
 default: `null`
 
diff --git a/src/docs/guide/usage/linter/rules/react/jsx-handler-names.md b/src/docs/guide/usage/linter/rules/react/jsx-handler-names.md
index 5ffe860eb44..e7a1ed679c2 100644
--- a/src/docs/guide/usage/linter/rules/react/jsx-handler-names.md
+++ b/src/docs/guide/usage/linter/rules/react/jsx-handler-names.md
@@ -77,13 +77,13 @@ Event handler prop prefixes to check against.
 
 ### eventHandlerPropRegex
 
-type: `string | null`
+type: `string`
 
 Compiled regex for event handler prop prefixes.
 
 ### eventHandlerRegex
 
-type: `string | null`
+type: `string`
 
 Compiled regex for event handler prefixes.
 
diff --git a/src/docs/guide/usage/linter/rules/react/jsx-max-depth.md b/src/docs/guide/usage/linter/rules/react/jsx-max-depth.md
index 97768cf6d81..45545d69dac 100644
--- a/src/docs/guide/usage/linter/rules/react/jsx-max-depth.md
+++ b/src/docs/guide/usage/linter/rules/react/jsx-max-depth.md
@@ -61,6 +61,8 @@ type: `integer`
 
 default: `2`
 
+The maximum allowed depth of nested JSX elements and fragments.
+
 ## How to use
 
 To **enable** this rule using the config file or in the CLI, you can use:
diff --git a/src/docs/guide/usage/linter/rules/react/only-export-components.md b/src/docs/guide/usage/linter/rules/react/only-export-components.md
index 89cc5d10000..955383f464f 100644
--- a/src/docs/guide/usage/linter/rules/react/only-export-components.md
+++ b/src/docs/guide/usage/linter/rules/react/only-export-components.md
@@ -95,7 +95,7 @@ This rule accepts a configuration object with the following properties:
 
 ### allowConstantExport
 
-type: `boolean | null`
+type: `boolean`
 
 default: `null`
 
@@ -122,7 +122,7 @@ certain exports). For example, in Remix:
 
 ### checkJS
 
-type: `boolean | null`
+type: `boolean`
 
 default: `null`
 
diff --git a/src/docs/guide/usage/linter/rules/typescript/no-empty-object-type.md b/src/docs/guide/usage/linter/rules/typescript/no-empty-object-type.md
index 50a74b5141b..807cbad850e 100644
--- a/src/docs/guide/usage/linter/rules/typescript/no-empty-object-type.md
+++ b/src/docs/guide/usage/linter/rules/typescript/no-empty-object-type.md
@@ -104,7 +104,7 @@ Allowed values are:
 
 ### allowWithName
 
-type: `string | null`
+type: `string`
 
 A stringified regular expression to allow interfaces and object type aliases with the configured name.
 
diff --git a/src/docs/guide/usage/linter/rules/typescript/prefer-optional-chain.md b/src/docs/guide/usage/linter/rules/typescript/prefer-optional-chain.md
index 59514504fb5..0624faaa03a 100644
--- a/src/docs/guide/usage/linter/rules/typescript/prefer-optional-chain.md
+++ b/src/docs/guide/usage/linter/rules/typescript/prefer-optional-chain.md
@@ -1,6 +1,6 @@
 ---
 title: "typescript/prefer-optional-chain"
-category: "Style"
+category: "Nursery"
 default: false
 type_aware: true
 fix: "fixable_fix"
@@ -21,6 +21,10 @@ const tsgolintSource = `https://github.com/oxc-project/tsgolint/blob/main/intern
 Enforce using concise optional chain expressions instead of chained logical AND
 operators, negated logical OR operators, or empty objects.
 
+Note that this rule is in the nursery category while we ensure it is working
+correctly in as many edge-case scenarios as possible. The logic for this is
+complex and the autofix may cause logic changes in some edge-cases.
+
 ### Why is this bad?
 
 TypeScript 3.7 introduced optional chaining (`?.`) which provides a more concise
diff --git a/src/docs/guide/usage/linter/rules/typescript/prefer-ts-expect-error.md b/src/docs/guide/usage/linter/rules/typescript/prefer-ts-expect-error.md
index 24e83fc1c5b..51a8f497275 100644
--- a/src/docs/guide/usage/linter/rules/typescript/prefer-ts-expect-error.md
+++ b/src/docs/guide/usage/linter/rules/typescript/prefer-ts-expect-error.md
@@ -42,7 +42,7 @@ const str: string = 1;
 const multiLine: number = "value";
 ```
 
-Examples of **incorrect** code for this rule:
+Examples of **correct** code for this rule:
 
 ```ts
 /**
diff --git a/src/docs/guide/usage/linter/rules/typescript/switch-exhaustiveness-check.md b/src/docs/guide/usage/linter/rules/typescript/switch-exhaustiveness-check.md
index bae18e8b21d..c400699c664 100644
--- a/src/docs/guide/usage/linter/rules/typescript/switch-exhaustiveness-check.md
+++ b/src/docs/guide/usage/linter/rules/typescript/switch-exhaustiveness-check.md
@@ -135,7 +135,7 @@ even if not all union members are handled explicitly.
 
 ### defaultCaseCommentPattern
 
-type: `string | null`
+type: `string`
 
 Regular expression pattern that when matched in a default case comment,
 will suppress the exhaustiveness check.
diff --git a/src/docs/guide/usage/linter/rules/unicorn/empty-brace-spaces.md b/src/docs/guide/usage/linter/rules/unicorn/empty-brace-spaces.md
index c45b933a861..3e54a330fc3 100644
--- a/src/docs/guide/usage/linter/rules/unicorn/empty-brace-spaces.md
+++ b/src/docs/guide/usage/linter/rules/unicorn/empty-brace-spaces.md
@@ -29,13 +29,16 @@ makes the code easier to understand and maintain.
 
 ### Examples
 
+<!-- prettier-ignore-start -->
 Examples of **incorrect** code for this rule:
-
 ```javascript
-const a = {};
-class A {}
+const a = {  };
+class A {
+}
 ```
 
+<!-- prettier-ignore-end -->
+
 Examples of **correct** code for this rule:
 
 ```javascript
diff --git a/src/docs/guide/usage/linter/rules/unicorn/filename-case.md b/src/docs/guide/usage/linter/rules/unicorn/filename-case.md
index 0594e2d43c1..fe9dd362a49 100644
--- a/src/docs/guide/usage/linter/rules/unicorn/filename-case.md
+++ b/src/docs/guide/usage/linter/rules/unicorn/filename-case.md
@@ -72,12 +72,14 @@ The case style to enforce for filenames.
 You can set the `case` option like this:
 
 ```json
-"unicorn/filename-case": [
-"error",
 {
-"case": "kebabCase"
+  "unicorn/filename-case": [
+    "error",
+    {
+      "case": "kebabCase"
+    }
+  ]
 }
-]
 ```
 
 ### cases
@@ -91,15 +93,17 @@ The case style(s) to allow/enforce for filenames. `true` means the case style is
 You can set the `cases` option like this:
 
 ```json
-"unicorn/filename-case": [
-"error",
 {
-"cases": {
-"camelCase": true,
-"pascalCase": true
+  "unicorn/filename-case": [
+    "error",
+    {
+      "cases": {
+        "camelCase": true,
+        "pascalCase": true
+      }
+    }
+  ]
 }
-}
-]
 ```
 
 #### cases.camelCase
@@ -136,19 +140,21 @@ Whether snake case is allowed, e.g. `some_file_name.js`.
 
 ### ignore
 
-type: `string | null`
+type: `string`
 
 A regular expression pattern for filenames to ignore.
 
 You can set the `ignore` option like this:
 
 ```json
-"unicorn/filename-case": [
-"error",
 {
-"ignore": "^foo.*$"
+  "unicorn/filename-case": [
+    "error",
+    {
+      "ignore": "^foo.*$"
+    }
+  ]
 }
-]
 ```
 
 ### multipleFileExtensions
diff --git a/src/docs/guide/usage/linter/rules/version.data.js b/src/docs/guide/usage/linter/rules/version.data.js
index 21262a4473f..19803256a6b 100644
--- a/src/docs/guide/usage/linter/rules/version.data.js
+++ b/src/docs/guide/usage/linter/rules/version.data.js
@@ -1,5 +1,5 @@
 export default {
   load() {
-    return "49cf66ecfbf14b7511f62f7a22e1df6c74735fa9";
+    return "8a1cbbdbec47fdf9ea1f7099c3dfd83bd52f3c82";
   },
 };
diff --git a/src/docs/guide/usage/linter/rules/vitest/consistent-each-for.md b/src/docs/guide/usage/linter/rules/vitest/consistent-each-for.md
index 3cb35645998..72ac0eef82e 100644
--- a/src/docs/guide/usage/linter/rules/vitest/consistent-each-for.md
+++ b/src/docs/guide/usage/linter/rules/vitest/consistent-each-for.md
@@ -61,19 +61,19 @@ This rule accepts a configuration object with the following properties:
 
 ### describe
 
-type: `"for" | "each" | null`
+type: `"for" | "each"`
 
 ### it
 
-type: `"for" | "each" | null`
+type: `"for" | "each"`
 
 ### suite
 
-type: `"for" | "each" | null`
+type: `"for" | "each"`
 
 ### test
 
-type: `"for" | "each" | null`
+type: `"for" | "each"`
 
 ## How to use