[Docs] Update CONTRIBUTING.md (#905)

* [Docs] Update CONTRIBUTING.md

* [Docs] Update CONTRIBUTING.md

* fix case

.github/CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to mmocr
+# Contributing to MMOCR
 
 All kinds of contributions are welcome, including but not limited to the following.
 
@@ -7,35 +7,39 @@ All kinds of contributions are welcome, including but not limited to the followi
 
 Contents
 
-- [Workflow](#workflow)
+- [Contributing to MMOCR](#contributing-to-mmocr)
+  - [Workflow](#workflow)
     - [Main Steps](#main-steps)
     - [Detailed Steps](#detailed-steps)
-        - [Step 1: Create a Fork](#step-1-create-a-fork)
-        - [Step 2: Develop a new feature](#step-2-develop-a-new-feature)
-            - [Step 2.1: Keep your fork up to date](#step-21-keep-your-fork-up-to-date)
-            - [Step 2.2: Create a feature branch](#step-22-create-a-feature-branch)
-        - [Step 3: Commit your changes](#step-3-commit-your-changes)
-        - [Step 4: Prepare to Pull Request](#step-4-prepare-to-pull-request)
-            - [Step 4.1: Merge official repo updates to your fork](#step-41-merge-official-repo-updates-to-your-fork)
-            - [Step 4.2: Push <your_feature_branch> branch to your remote forked repo,](#step-42-push-your_feature_branch-branch-to-your-remote-forked-repo)
-            - [Step 4.3: Create a Pull Request](#step-43-create-a-pull-request)
-            - [Step 4.4: Review code](#step-44-review-code)
-            - [Step 4.5: Revise <your_feature_branch>  (optional)](#step-45-revise-your_feature_branch--optional)
-            - [Step 4.6: Delete <your_feature_branch> branch if your PR is accepted.](#step-46-delete-your_feature_branch-branch-if-your-pr-is-accepted)
-- [Code style](#code-style)
+      - [Step 1: Create a Fork](#step-1-create-a-fork)
+      - [Step 2: Develop a new feature](#step-2-develop-a-new-feature)
+        - [Step 2.1: Keep your fork up to date](#step-21-keep-your-fork-up-to-date)
+        - [Step 2.2: Create a feature branch](#step-22-create-a-feature-branch)
+      - [Step 3: Commit your changes](#step-3-commit-your-changes)
+      - [Step 4: Prepare to Pull Request](#step-4-prepare-to-pull-request)
+        - [Step 4.1: Merge official repo updates to your fork](#step-41-merge-official-repo-updates-to-your-fork)
+        - [Step 4.2: Push <your_feature_branch> branch to your remote forked repo,](#step-42-push-your_feature_branch-branch-to-your-remote-forked-repo)
+        - [Step 4.3: Create a Pull Request](#step-43-create-a-pull-request)
+        - [Step 4.4: Review code](#step-44-review-code)
+        - [Step 4.5: Revise <your_feature_branch>  (optional)](#step-45-revise-your_feature_branch--optional)
+        - [Step 4.6: Delete <your_feature_branch> branch if your PR is accepted.](#step-46-delete-your_feature_branch-branch-if-your-pr-is-accepted)
+  - [Code style](#code-style)
     - [Python](#python)
+      - [Installing pre-commit hooks](#installing-pre-commit-hooks)
     - [C++ and CUDA](#c-and-cuda)
 
 ## Workflow
 ### Main Steps
-1. fork and pull the latest mmocr
-2. checkout a new branch (do not use main branch for PRs)
-3. commit your changes
-4. create a PR
+
+1. Fork and pull the latest MMOCR
+2. Checkout a new branch (do not use main branch for PRs)
+3. Commit your changes
+4. Create a PR
 
 **Note**
+
 - If you plan to add some new features that involve large changes, it is encouraged to open an issue for discussion first.
-- If you are the author of some papers and would like to include your method to mmocr, please let us know (open an issue or contact the maintainers). We will much appreciate your contribution.
+- If you are the author of some papers and would like to include your method to MMOCR, please let us know (open an issue or contact the maintainers). We will much appreciate your contribution.
 - For new features and new modules, unit tests are required to improve the code's robustness.
 
 ### Detailed Steps
@@ -46,7 +50,6 @@ The *main* branch is the main branch where the source code of **HEAD** always re
 
 Feature branches are used to develop new features for the upcoming or a distant future release.
 
-
 All new developers to **MMOCR** need to follow the following steps:
 
 #### Step 1: Create a Fork
@@ -82,7 +85,8 @@ git push origin main
 - Create an issue on [github](https://github.com/open-mmlab/mmocr)
 
 - Create a feature branch
-- ```
+-
+  ```bash
   git checkout -b feature/iss_<index> main
   # index is the issue index on github above
   ```
@@ -91,17 +95,25 @@ git push origin main
 
 Develop your new feature and test it to make sure it works well, then commit.
 
-Please run
-```
-pre-commit run --all-files
-pytest tests
-```
-and fix all failures before every git commit.
-```
+If you have not configured pre-commit hooks for MMOCR, please [install pre-commit hooks](#installing-pre-commit-hooks) before your first commit.
+
+The commit message is suggested to be clear. Here is an example:
+
+```bash
 git commit -m "fix #<issue_index>: <commit_message>"
 ```
 
 #### Step 4: Prepare to Pull Request
+
+- Before creating an PR, please run
+
+  ```bash
+  pre-commit run --all-files
+  pytest tests
+  ```
+
+  and fix all failures.
+
 - Make sure to link your pull request to the related issue. Please refer to the [instructon](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)
 
 
@@ -160,6 +172,8 @@ We use [pre-commit hook](https://pre-commit.com/) that checks and formats for `f
  fixes `end-of-files`, sorts `requirments.txt` automatically on every commit.
 The config for a pre-commit hook is stored in [.pre-commit-config](../.pre-commit-config.yaml).
 
+#### Installing pre-commit hooks
+
 After you clone the repository, you will need to install initialize pre-commit hook.
 
 ```shell