Minor docs fixes

Author: Rel1cx

apps/website/content/docs/rules/overview.mdx

@@ -223,8 +223,8 @@ full: true
     | [`no-forward-ref`](no-forward-ref)                                                 | 1️⃣ 1️⃣ |    `🔄`   | Replaces usage of `forwardRef` with passing `ref` as a prop                                                                   | >=19.0.0 |
     | [`no-implicit-key`](no-implicit-key)                                               | 1️⃣ 1️⃣ |    `🧪`   | Prevents `key` from not being explicitly specified (e.g., spreading `key` from objects)                                       |          |
     | [`no-leaked-conditional-rendering`](no-leaked-conditional-rendering)               | 0️⃣ 0️⃣ |    `💭`   | Prevents problematic leaked values from being rendered                                                                        |          |
-    | [`no-missing-component-display-name`](no-missing-component-display-name)           | 0️⃣ 0️⃣ |           | Enforces that all components have a `displayName` that can be used in devtools                                                |          |
-    | [`no-missing-context-display-name`](no-missing-context-display-name)               | 0️⃣ 0️⃣ |    `🔧`   | Enforces that all contexts have a `displayName` that can be used in devtools                                                  |          |
+    | [`no-missing-component-display-name`](no-missing-component-display-name)           | 0️⃣ 0️⃣ |           | Enforces that all components have a `displayName` that can be used in DevTools                                                |          |
+    | [`no-missing-context-display-name`](no-missing-context-display-name)               | 0️⃣ 0️⃣ |    `🔧`   | Enforces that all contexts have a `displayName` that can be used in DevTools                                                  |          |
     | [`no-missing-key`](no-missing-key)                                                 | 2️⃣ 2️⃣ |           | Disallows missing `key` on items in list rendering                                                                            |          |
     | [`no-misused-capture-owner-stack`](no-misused-capture-owner-stack)                 | 0️⃣ 2️⃣ |    `🧪`   | Prevents incorrect usage of `captureOwnerStack`                                                                               |          |
     | [`no-nested-component-definitions`](no-nested-component-definitions)               | 2️⃣ 2️⃣ |           | Disallows nesting component definitions inside other components                                                               |          |

packages/plugins/eslint-plugin-react-debug/src/rules/class-component.mdx

@@ -14,7 +14,7 @@ react-debug/class-component
 
 ## Description
 
-Reports all class components in JSON format. Useful for debugging. This rule should only be used for debugging purposes; otherwise, leave it off.
+Reports all class components in JSON format. Useful for debugging. This rule should only be used for debugging purposes; otherwise leave it off.
 
 ## Examples
 

packages/plugins/eslint-plugin-react-debug/src/rules/function-component.mdx

@@ -14,7 +14,7 @@ react-debug/function-component
 
 ## Description
 
-Reports all function components in JSON format. Useful for debugging. This rule should only be used for debugging purposes; otherwise, leave it off.
+Reports all function components in JSON format. Useful for debugging. This rule should only be used for debugging purposes; otherwise leave it off.
 
 ## Examples
 

packages/plugins/eslint-plugin-react-debug/src/rules/hook.mdx

@@ -14,7 +14,7 @@ react-debug/hook
 
 ## Description
 
-Reports all React Hooks in JSON format. Useful for debugging. This rule should be used only for debugging purposes. Otherwise, leave it off.
+Reports all React Hooks in JSON format. Useful for debugging. This rule should be used only for debugging purposes; otherwise, leave it off.
 
 ## Examples
 

packages/plugins/eslint-plugin-react-debug/src/rules/is-from-react.mdx

@@ -14,7 +14,7 @@ react-debug/is-from-react
 
 ## Description
 
-Reports all identifiers initialized from React in JSON format. Useful for debugging. This rule should only be used for debugging purposes. Otherwise, leave it off.
+Reports all identifiers initialized from React in JSON format. Useful for debugging. This rule should only be used for debugging purposes; otherwise, leave it off.
 
 ## Examples
 

packages/plugins/eslint-plugin-react-debug/src/rules/is-from-ref.mdx

@@ -14,7 +14,7 @@ react-debug/is-from-ref
 
 ## Description
 
-Reports all identifiers initialized or derived from ref in JSON format. Useful for debugging. This rule should only be used for debugging purposes. Otherwise, leave it off.
+Reports all identifiers initialized or derived from refs in JSON format. Useful for debugging. This rule should only be used for debugging purposes; otherwise, leave it off.
 
 ## Examples
 

packages/plugins/eslint-plugin-react-debug/src/rules/is-from-ref.ts

@@ -20,7 +20,7 @@ export default createRule<[], MessageID>({
   meta: {
     type: "problem",
     docs: {
-      description: "Reports all identifiers initialized or derived from ref in JSON format.",
+      description: "Reports all identifiers initialized or derived from refs in JSON format.",
     },
     messages: {
       isFromRef: "{{json}}",

packages/plugins/eslint-plugin-react-debug/src/rules/jsx.mdx

@@ -14,7 +14,7 @@ react-debug/jsx
 
 ## Description
 
-Reports all JSX elements and fragments in JSON format. Useful for debugging. This rule should be used only for debugging purposes; otherwise, leave it off.
+Reports all JSX elements and fragments in JSON format. Useful for debugging. This rule should be used only for debugging purposes; otherwise leave it off.
 
 ## Examples
 

packages/plugins/eslint-plugin-react-dom/src/rules/no-missing-iframe-sandbox.mdx

@@ -28,11 +28,11 @@ react-dom/no-missing-iframe-sandbox
 
 Enforces an explicit `sandbox` attribute for `iframe` elements.
 
-The sandbox attribute enables an extra set of restrictions for the content in the iframe. Using sandbox attribute is considered a good security practice.
+The sandbox attribute enables an extra set of restrictions for the content in the iframe. Using the sandbox attribute is considered a good security practice.
 
 ## Examples
 
-This rule checks all React iframe elements and verifies that there is sandbox attribute and that it's value is valid.
+This rule checks all React iframe elements and verifies that there is a `sandbox` attribute and that its value is valid.
 
 ### Failing
 
@@ -72,4 +72,4 @@ function MyComponent() {
 - [`no-missing-button-type`](./dom-no-missing-button-type)\
   Enforces an explicit `type` attribute for `button` elements.
 - [`no-unsafe-iframe-sandbox`](./dom-no-unsafe-iframe-sandbox)\
-  Enforces `sandbox` attribute for `iframe` elements is not set to unsafe combinations.
+  Enforces the `sandbox` attribute for `iframe` elements is not set to unsafe combinations.

packages/plugins/eslint-plugin-react-dom/src/rules/no-namespace.mdx

@@ -28,7 +28,7 @@ react-dom/no-namespace
 
 Enforces the absence of a `namespace` in React elements.
 
-Namespaces, such as with `svg:circle` are not supported in React.
+Namespaces, such as `svg:circle`, are not supported in React.
 
 ## Examples