textrules mdgen

MANUAL.md

@@ -107,8 +107,8 @@ Svlint supports plugin rules, an example of which is available
 
 A plugin rule is one which is compiled separately to the main svlint binary,
 and is loaded at runtime.
-In the same way as integrated rules, a plugin rule must implement the `Rule`
-trait, i.e. `check`, `name`, `hint`, and `reason`.
+In the same way as integrated rules, a plugin rule must implement the
+`SyntaxRule` trait, i.e. `check`, `name`, `hint`, and `reason`.
 The `hint` and `reason` methods allow plugin rules to provide information back
 to the user on the terminal, but they do not require testcases or an
 explanation.
@@ -236,7 +236,7 @@ You are welcome to suggest a new rule through
 [Pull Requests](https://github.com/dalance/svlint/pulls).
 
 
-# Functional Rules
+# Functional Syntax Rules
 
 
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
@@ -3964,7 +3964,7 @@ The most relevant clauses of IEEE1800-2017 are:
 - 12.7 Loop statements
 
 
-# Naming Convention Rules
+# Naming Convention Syntax Rules
 
 Rules for checking against naming conventions are named with either the suffix
 `_with_label` or one of these prefixes:
@@ -7490,7 +7490,7 @@ See also:
 - **uppercamelcase_module** - Potential companion rule.
 
 
-# Style/Whitespace Convention Rules
+# Style/Whitespace Convention Syntax Rules
 
 Most rules for checking style/whitespace are named with the prefix `style_`,
 but `tab_character` is also in this class.