docs: replace htperlinks' URL with filename

Bogay · Lee-W · commit 4b7604ef4e48 · 2021-10-06T23:07:29.000+08:00
According to mkdoc documentation, link to another page in the same documentation can directly use file path. mkdoc documentation: https://www.mkdocs.org/user-guide/writing-your-docs/#linking-to-pages
diff --git a/docs/README.md b/docs/README.md
@@ -106,7 +106,7 @@ After the configuration is added, you'll need to run
 pre-commit install --hook-type commit-msg
 ```
 
-Read more about the `check` command [here](https://commitizen-tools.github.io/commitizen/check/).
+Read more about the `check` command [here](check.md).
 
 ### Help
 
@@ -175,7 +175,7 @@ See [Third-Party Commitizen Templates](third-party-commitizen.md).
 
 ## FAQ
 
-See [FAQ - commitizen](https://commitizen-tools.github.io/commitizen/faq/).
+See [FAQ](faq.md).
 
 ## Contributing
 
diff --git a/docs/config.md b/docs/config.md
@@ -134,9 +134,9 @@ commitizen:
 | `customize`      | `dict` | `None`                      | **This is only supported when config through `toml`.** Custom rules for committing and bumping. [See more](customization)                                     |
 | `use_shortcuts`  | `bool` | `false`                     | If enabled, commitizen will show keyboard shortcuts when selecting from a list. Define a `key` for each of your choices to set the key. [See more](shortcuts) |
 
-[version_files]: https://commitizen-tools.github.io/commitizen/bump/#version_files
-[tag_format]: https://commitizen-tools.github.io/commitizen/bump/#tag_format
-[bump_message]: https://commitizen-tools.github.io/commitizen/bump/#bump_message
+[version_files]: bump.md#version_files
+[tag_format]: bump.md#tag_format
+[bump_message]: bump.md#bump_message
 [additional-features]: https://github.com/tmbo/questionary#additional-features
-[customization]: https://commitizen-tools.github.io/commitizen/customization/
-[shortcuts]: https://commitizen-tools.github.io/commitizen/customization/#shortcut-keys
+[customization]: customization.md
+[shortcuts]: customization.md#shortcut-keys
diff --git a/docs/customization.md b/docs/customization.md
@@ -167,10 +167,10 @@ commitizen:
 
 #### Shortcut keys
 
-When the [`use_shortcuts`](https://commitizen-tools.github.io/commitizen/config/#settings) config option is enabled, commitizen can show and use keyboard shortcuts to select items from lists directly.
+When the [`use_shortcuts`](config.md#settings) config option is enabled, commitizen can show and use keyboard shortcuts to select items from lists directly.
 For example, when using the `cz_conventional_commits` commitizen template, shortcut keys are shown when selecting the commit type. Unless otherwise defined, keyboard shortcuts will be numbered automatically.
 To specify keyboard shortcuts for your custom choices, provide the shortcut using the `key` parameter in dictionary form for each choice you would like to customize.
- 
+
 ## 2. Customize through customizing a class
 
 The basic steps are:
diff --git a/docs/faq.md b/docs/faq.md
@@ -30,7 +30,7 @@ version_files = [
 ## Why are `revert` and `chore` valid types in the check pattern of cz conventional_commits but not types we can select?
 
 `revert` and `chore` are added to the "pattern" in `cz check` in order to prevent backward errors, but officially they are not part of conventional commits, we are using the latest [types from Angular](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#type) (they used to but were removed).
-However, you can create a customized `cz` with those extra types. (See [Customization](https://commitizen-tools.github.io/commitizen/customization/)
+However, you can create a customized `cz` with those extra types. (See [Customization](customization.md)
 
 See more discussion in issue [#142](https://github.com/commitizen-tools/commitizen/issues/142) and [#36](https://github.com/commitizen-tools/commitizen/issues/36)
 
diff --git a/docs/tutorials/gitlab_ci.md b/docs/tutorials/gitlab_ci.md
@@ -10,7 +10,7 @@ _Goal_: Bump a new version every time that a change occurs on the `master` branc
 2. A developer creates a merge request (MR) against `master` branch
 3. When the `MR` is merged into master, the 2 stages of the CI are executed
 4. For simplification, we store the software version in a file called `VERSION`. You can use any file that you want as `commitizen` supports it.
-5. The commit message executed automatically by the `CI` must include `[skip-ci]` in the message; otherwise, the process will generate a loop. You can define the message structure in [commitizen](https://commitizen-tools.github.io/commitizen/bump/) as well.
+5. The commit message executed automatically by the `CI` must include `[skip-ci]` in the message; otherwise, the process will generate a loop. You can define the message structure in [commitizen](../bump.md) as well.
 
 ### Gitlab Configuration
 
diff --git a/docs/tutorials/writing_commits.md b/docs/tutorials/writing_commits.md
@@ -38,5 +38,5 @@ understand what happened.
 | `fix(commands): bump error when no user provided` | `fix: stuff` |
 | `feat: add new commit command` | `feat: commit command introduced` |
 
-[customization]: https://commitizen-tools.github.io/commitizen/customization/
+[customization]: customization.md
 [conventional_commits]: https://www.conventionalcommits.org
