diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..a17719c5
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,42 @@
+# Contributor Covenant Code of Conduct
+ 
+## Our Pledge
+ 
+ In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+ 
+## Our Standards
+ 
+ Examples of behavior that contributes to creating a positive environment include:
+ 
+ Using welcoming and inclusive language
+ Being respectful of differing viewpoints and experiences
+ Gracefully accepting constructive criticism
+ Focusing on what is best for the community
+ Showing empathy towards other community members
+ Examples of unacceptable behavior by participants include:
+ 
+ The use of sexualized language or imagery and unwelcome sexual attention or advances
+ Trolling, insulting/derogatory comments, and personal or political attacks
+ Public or private harassment
+ Publishing others' private information, such as a physical or electronic address, without explicit permission
+ Other conduct which could reasonably be considered inappropriate in a professional setting
+ 
+## Our Responsibilities
+ 
+ Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+ 
+ Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+ 
+## Scope
+ 
+ This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+ 
+## Enforcement
+ 
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at **score-community@googlegroups.com**. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+ 
+ Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+ 
+## Attribution
+ 
+ This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4).
\ No newline at end of file
diff --git a/README.md b/README.md
index 34788296..5ece716d 100644
--- a/README.md
+++ b/README.md
@@ -224,7 +224,7 @@ const ncProviders = nodeCloud.getProviders(options);
 
 NodeCloud relies on the passionate members of its community to keep delivering impactful tools to people all over the world. Contributions of any kind are welcome!
 
-You can help us in many ways. Including new features, bug fixing, error reporting and documentation. Before contributing, be sure to consult NodeClouds's contribution guidelines. As a member of our community, you must abide by our Code Of Conduct.
+You can help us in many ways. Including new features, bug fixing, error reporting and documentation. Before contributing, be sure to consult NodeClouds's contribution guidelines. As a member of our community, you must abide by our [Code Of Conduct](./CODE_OF_CONDUCT.md).
 
 ### 💻 Development setup
 
@@ -250,7 +250,7 @@ yarn
 
 ### Important Notes for Developers 😎
 
-❇️ This project is based on [Lerna](https://lerna.js.org/) and Yarn workspaces where there are multiple projects in the same repository. It's better to get some background knowledge about these before making any changes in the code. Check the `lerna.json` for the current configuration.
+❇️ This project is based on [Lerna](https://lerna.js.org/) and [Yarn](https://classic.yarnpkg.com/lang/en/) workspaces where there are multiple projects in the same repository. It's better to get some background knowledge about these before making any changes in the code. Check the `lerna.json` for the current configuration.
 
 ❇️ `@nodecloud/aws-plugin` , `@nodecloud/gcp-plugin` , `@nodecloud/azure-plugin` and `@nodecloud/common` are `Lerna` managed yarn workspaces where the `generator` is another standalone yarn workspace.
 
@@ -284,7 +284,7 @@ _Adding the -W flag makes it explicit that we’re adding the dependency to the
 lerna exec -- yarn remove dep-name
 ```
 
-❇️ Use symlinks when you want to make changes while testing them out in a demo project.** Do not use npm link** instead use yarn linking
+❇️ Use symlinks when you want to make changes while testing them out in a demo project. **Do not use npm link** instead use yarn linking
 
 ```
 yarn link