diff --git a/crates/oxc_linter/src/rules/eslint/func_names.rs b/crates/oxc_linter/src/rules/eslint/func_names.rs
index 0ea77a934a5bd..5353c23c6a90b 100644
--- a/crates/oxc_linter/src/rules/eslint/func_names.rs
+++ b/crates/oxc_linter/src/rules/eslint/func_names.rs
@@ -51,8 +51,8 @@ declare_oxc_lint!(
     ///
     /// ### Why is this bad?
     ///
-    /// Leaving the name off a function will cause <anonymous> to appear
-    /// in stack traces of errorsthrown in it or any function called within it.
+    /// Leaving the name off a function will cause `<anonymous>` to appear
+    /// in stack traces of errors thrown in it or any function called within it.
     /// This makes it more difficult to find where an error is thrown.
     /// If you provide the optional name for a function expression
     /// then you will get the name of the function expression in the stack trace.
diff --git a/crates/oxc_linter/src/rules/jsx_a11y/anchor_is_valid.rs b/crates/oxc_linter/src/rules/jsx_a11y/anchor_is_valid.rs
index 2a8ceea64c638..858e5d7c2ae63 100644
--- a/crates/oxc_linter/src/rules/jsx_a11y/anchor_is_valid.rs
+++ b/crates/oxc_linter/src/rules/jsx_a11y/anchor_is_valid.rs
@@ -41,7 +41,7 @@ struct AnchorIsValidConfig {
 
 declare_oxc_lint!(
     /// ### What it does
-    /// The HTML <a> element, with a valid href attribute, is formally defined as representing a **hyperlink**.
+    /// The HTML `<a>` element, with a valid href attribute, is formally defined as representing a **hyperlink**.
     /// That is, a link between one HTML document and another, or between one location inside an HTML document and another location inside the same document.
     ///
     /// While before it was possible to attach logic to an anchor element, with the advent of JSX libraries,