Refactor docs

Author: wooorm

.github/contribute.md

@@ -1,6 +1,7 @@
 # Contribute
 
-> 👉 **Important**: this project has a [code of conduct][coc].
+> 👉 **Important**:
+> this project has a [code of conduct][coc].
 > By interacting with this repository and community you agree to abide by its
 > terms.
 
@@ -37,27 +38,27 @@ See [Project][] for more info.
 
 ## Submitting an issue
 
-*   the issue tracker is for issues, discussions are for questions
-*   search the issue tracker (including closed issues) before opening a new
-    issue
-*   ensure you’re using the latest versions of packages and other tools
-*   use a clear and descriptive title
-*   include as much information as possible: steps to reproduce the issue,
-    error message, version, operating system, etcetera
-*   the more time you put into an issue, the better help you can get
-*   the best issue report is a failing test] proving it
+* the issue tracker is for issues, discussions are for questions
+* search the issue tracker (including closed issues) before opening a new
+  issue
+* ensure you’re using the latest versions of packages and other tools
+* use a clear and descriptive title
+* include as much information as possible: steps to reproduce the issue,
+  error message, version, operating system, etcetera
+* the more time you put into an issue, the better help you can get
+* the best issue report is a failing test] proving it
 
 ## Submitting a pull request
 
-*   run `cargo fmt` and `cargo test` locally to format and test your changes
-*   non-trivial changes are often best discussed in an issue first, to prevent
-    you from doing unnecessary work
-*   for ambitious tasks, you should try to get your work in front of the
-    community for feedback as soon as possible
-*   new features should be accompanied by tests and documentation
-*   don’t include unrelated changes
-*   write a convincing description of why your pull request should land:
-    it’s your job to be convincing
+* run `cargo fmt` and `cargo test` locally to format and test your changes
+* non-trivial changes are often best discussed in an issue first, to prevent
+  you from doing unnecessary work
+* for ambitious tasks, you should try to get your work in front of the
+  community for feedback as soon as possible
+* new features should be accompanied by tests and documentation
+* don’t include unrelated changes
+* write a convincing description of why your pull request should land:
+  it’s your job to be convincing
 
 ## Project (for maintainers)
 
@@ -66,19 +67,19 @@ and how to run useful scripts.
 
 ### Release
 
-*   update the `version` field in `Cargo.toml`
-*   search for the previous version in `readme.md`, replace with new one
-*   `git commit --all --message 1.2.3 && git tag 1.2.3 && git push && git push --tags`
-*   `cargo publish`
+* update the `version` field in `Cargo.toml`
+* search for the previous version in `readme.md`, replace with new one
+* `git commit --all --message 1.2.3 && git tag 1.2.3 && git push && git push --tags`
+* `cargo publish`
 
 (similar for `mdast_util_to_markdown`)
 
 ## Resources
 
-*   [how to contribute to open source](https://opensource.guide/how-to-contribute/)
-*   [making your first contribution](https://medium.com/@vadimdemedes/making-your-first-contribution-de6576ddb190)
-*   [using pull requests](https://help.github.com/articles/about-pull-requests/)
-*   [GitHub help](https://help.github.com)
+* [how to contribute to open source](https://opensource.guide/how-to-contribute/)
+* [making your first contribution](https://medium.com/@vadimdemedes/making-your-first-contribution-de6576ddb190)
+* [using pull requests](https://help.github.com/articles/about-pull-requests/)
+* [GitHub help](https://help.github.com)
 
 ## License
 

.github/support.md

@@ -16,20 +16,20 @@ Spend time framing questions and add links and resources.
 Spending the extra time up front helps save everyone time in the long run.
 Here are some tips:
 
-*   see [*How do I ask a good question* by `StackOverflow`][how-to-ask] for a
-    good guide
-*   [talk to a duck][rubberduck]!
-*   don’t fall for the [XY problem][xy]
-*   search to find out if a similar question has been asked
-*   try to define what you need help with:
-    *   is there something in particular you want to do?
-    *   what problem are you encountering and what steps have you taken to try
-        and fix it?
-    *   is there a concept you don’t understand?
-*   provide sample code, if possible
-*   screenshots can help, but if there’s important text such as code or error
-    messages in them, please also provide those as text
-*   the more time you put into asking your question, the better we can help you
+* see [*How do I ask a good question* by `StackOverflow`][how-to-ask] for a
+  good guide
+* [talk to a duck][rubberduck]!
+* don’t fall for the [XY problem][xy]
+* search to find out if a similar question has been asked
+* try to define what you need help with:
+  * is there something in particular you want to do?
+  * what problem are you encountering and what steps have you taken to try
+    and fix it?
+  * is there a concept you don’t understand?
+* provide sample code, if possible
+* screenshots can help, but if there’s important text such as code or error
+  messages in them, please also provide those as text
+* the more time you put into asking your question, the better we can help you
 
 ## Contributions
 

generate/src/main.rs

@@ -152,7 +152,7 @@ async fn punctuation() {
 ///
 /// ## References
 ///
-/// *   [*§ 2.1 Characters and lines* in `CommonMark`](https://spec.commonmark.org/0.31.2/#unicode-punctuation-character)
+/// * [*§ 2.1 Characters and lines* in `CommonMark`](https://spec.commonmark.org/0.31.2/#unicode-punctuation-character)
 pub static PUNCTUATION: [char; {}] = [
 {}
 ];