diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 0000000000000000000000000000000000000000..84a3f18af5c276a38801cf50d343ef781cd69c31
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,5 @@
+# KubeEdge Community Code of Conduct
+
+KubeEdge follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at kubeedge@gmail.com.
diff --git a/community-membership.md b/community-membership.md
index 86520bf8c5e7bff1a3f720fb249750d5a2b21b15..92f643c5f909b131caa0624e1d7da67cb2efae5a 100644
--- a/community-membership.md
+++ b/community-membership.md
@@ -17,7 +17,7 @@ This document gives a brief overview of the KubeEdge community roles with the re
 ## Member
 
 Members are active participants in the community who contribute by authoring PRs,
-reviewing issues/PRs or participate in community discussions on slack/mailing list. 
+reviewing issues/PRs or participate in community discussions on slack/mailing list.
 
 
 ### Requirements
@@ -44,7 +44,7 @@ reviewing issues/PRs or participate in community discussions on slack/mailing li
 ## Approver
 
 Approvers are active members who have good experience and knowledge of the domain.
-They have actively participated in the issue/PR reviews and have identified relevant issues during review. 
+They have actively participated in the issue/PR reviews and have identified relevant issues during review.
 
 
 ### Requirements
@@ -114,5 +114,5 @@ Has deep understanding of KubeEdge and related domain and facilitates major agre
 
 **Note :** These roles are applicable only for KubeEdge github organization and repositories. Currently KubeEdge doesn't have a formal process for review and acceptance into these roles. We will come-up with a process soon.
 
-[Code of Conduct]: https://github.com/kubeedge/kubeedge/blob/master/CODE_OF_CONDUCT.md
+[Code of Conduct]: https://github.com/kubeedge/community/blob/master/CODE_OF_CONDUCT.md
 [two-factor authentication]: https://help.github.com/articles/about-two-factor-authentication
diff --git a/contribute.md b/contribute.md
index c47f2c740ce4f523d9d4548b2425a4a897c83d8f..d8c621000d9d18c62f8619c1f2cc8934eafe8591 100644
--- a/contribute.md
+++ b/contribute.md
@@ -20,7 +20,7 @@ Welcome to KubeEdge!
 
 ## Code of Conduct
 
-Please make sure to read and observe our [Code of Conduct](../../CODE_OF_CONDUCT.md).
+Please make sure to read and observe our [Code of Conduct](./CODE_OF_CONDUCT.md).
 
 ## Community Expectations
 
@@ -33,7 +33,7 @@ The goal of the community is to develop a cloud native edge computing platform b
 # Getting started
 
 - Fork the repository on GitHub
-- Read the [setup](../setup/setup.md) for build instructions.
+- Read the [setup](https://github.com/kubeedge/kubeedge/tree/master/docs/setup/setup.md) for build instructions.
 
 
 # Your First Contribution
@@ -140,4 +140,4 @@ The location of the test code varies with type, as do the specifics of the envir
 * Integration: These tests cover interactions of package components or interactions between KubeEdge components and Kubernetes control plane components like API server.  An example would be testing whether the device controller is able to create config maps when device CRDs are created in the API server.
 * End-to-end ("e2e"): These are broad tests of overall system behavior and coherence. The e2e tests are in [kubeedge e2e](https://github.com/kubeedge/kubeedge/tree/master/tests/e2e).
 
-Continuous integration will run these tests on PRs.
\ No newline at end of file
+Continuous integration will run these tests on PRs.
diff --git a/support.md b/support.md
index 99538ecca949bd02ef3fc824424b6bee9c265b45..13edc7c7082af0554aed21848ea14b81722982c9 100644
--- a/support.md
+++ b/support.md
@@ -1,11 +1,11 @@
 
 # Support
 
-If you need support, start with the [troubleshooting guide](../troubleshooting/troubleshooting.md), and work your way through the process that we've outlined.
+If you need support, start with the [troubleshooting guide](https://github.com/kubeedge/kubeedge/tree/master/docs/troubleshooting/troubleshooting.md), and work your way through the process that we've outlined.
 
 ## Community
 
-**Slack channel:** 
+**Slack channel:**
 
 We use Slack for public discussions. To chat with us or the rest of the community, join us in the [KubeEdge Slack](https://kubeedge.slack.com) team channel #general. To sign up, use our Slack inviter link [here](https://join.slack.com/t/kubeedge/shared_invite/enQtNDg1MjAwMDI0MTgyLTQ1NzliNzYwNWU5MWYxOTdmNDZjZjI2YWE2NDRlYjdiZGYxZGUwYzkzZWI2NGZjZWRkZDVlZDQwZWI0MzM1Yzc).