Format markdown

docs/git.md

@@ -2,12 +2,12 @@
 
 The Git plugin in release-it, by default, does the following:
 
-1.  [Prerequisite checks][1]
-2.  \[Files may be updated by other plugins and/or user commands/hooks]
-3.  `git add . --update`
-4.  `git commit -m "[git.commitMessage]"`
-5.  `git tag --annotate --message="[git.tagAnnotation]" [git.tagName]`
-6.  `git push [git.pushArgs] [git.pushRepo]`
+1. [Prerequisite checks][1]
+2. \[Files may be updated by other plugins and/or user commands/hooks]
+3. `git add . --update`
+4. `git commit -m "[git.commitMessage]"`
+5. `git tag --annotate --message="[git.tagAnnotation]" [git.tagName]`
+6. `git push [git.pushArgs] [git.pushRepo]`
 
 When not in CI mode, release-it will ask for confirmation before each of the commit, tag, and push steps.
 

docs/github-releases.md

@@ -11,8 +11,8 @@ See the screenshot on the right for an overview of what release-it automates.
 
 To add [GitHub releases][3] in your release-it flow, there are two options:
 
-1.  Automated. This requires a personal access token.
-2.  Manual. The GitHub web interface will be opened with pre-populated fields.
+1. Automated. This requires a personal access token.
+2. Manual. The GitHub web interface will be opened with pre-populated fields.
 
 ## Automated
 
@@ -168,8 +168,8 @@ release-it --no-increment --no-git --github.release --github.update --github.ass
 
 ## Comments
 
-To submit a comment to each merged pull requests and closed issue that is part of the release, set `github.comments.submit` to
-`true`. Here are the default settings:
+To submit a comment to each merged pull requests and closed issue that is part of the release, set
+`github.comments.submit` to `true`. Here are the default settings:
 
 ```json
 {