From 2203ad9a9b59ede876cbe24c4094a2b3867b5968 Mon Sep 17 00:00:00 2001
From: micro-pixel <56903899+micro-pixel@users.noreply.github.com>
Date: Wed, 23 Oct 2019 11:02:32 +0800
Subject: [PATCH] docs: fix link to name style

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 6e16fae4..463f95ae 100644
--- a/README.md
+++ b/README.md
@@ -465,8 +465,8 @@ We have setup [this repository](https://github.com/gnes-ai/benchmark) to track t
 
 1. Create a new branch, say `fix-gnes-typo-1`
 2. Fix/improve the codebase
-3. Commit the changes. Note the **commit message must follow [the naming style]((#commit-message-naming))**, say `fix(readme): improve the readability and move sections`
-4. Make a pull request. Note the **pull request must follow [the naming style]((#commit-message-naming))**. It can simply be one of your commit messages, just copy paste it, e.g. `fix(readme): improve the readability and move sections`
+3. Commit the changes. Note the **commit message must follow [the naming style](./CONTRIBUTING.md#commit-message-naming)**, say `fix(readme): improve the readability and move sections`
+4. Make a pull request. Note the **pull request must follow [the naming style](./CONTRIBUTING.md#commit-message-naming)**. It can simply be one of your commit messages, just copy paste it, e.g. `fix(readme): improve the readability and move sections`
 5. Submit your pull request and wait for all checks passed (usually 10 minutes)
     - Coding style
     - Commit and PR styles check