From ddcd3dc9aea7e0e1cf12e07a0d306d4ee08e0b61 Mon Sep 17 00:00:00 2001 From: Shivam Agarwal Date: Mon, 15 Oct 2018 12:55:35 +0530 Subject: [PATCH] typos in multiple files (#730) --- CONTRIBUTING.md | 2 +- SECURITY.md | 4 ++-- code-of-conduct.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a1491fdc8c0..7b9d355e730 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,7 +3,7 @@ *First*: if you're unsure or afraid of anything, just ask or submit the issue or pull request anyway. You won't be yelled at for giving your best effort. The worst that can happen is that you'll be politely asked to change something. We -appreciate any sort of contributions, and don't want a wall of rules to get in +appreciate any sort of contributions and don't want a wall of rules to get in the way of that. However, for those individuals who want a bit more guidance on the best way to diff --git a/SECURITY.md b/SECURITY.md index c8d6b846d5a..33ee674ebef 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -8,7 +8,7 @@ To report a security issue, please email us at [build@hasura.io](mailto:build@ha - You think you have discovered a potential security vulnerability in the Hasura GraphQL Engine or related components. - You are unsure how a vulnerability affects the Hasura GraphQL Engine. -- You think you discovered a vulnerability in another project that Hasura GraphQL Engine depends on (e.g. heroku, docker, etc) +- You think you discovered a vulnerability in another project that Hasura GraphQL Engine depends on (e.g. Heroku, Docker, etc) - You want to report any other security risk that could potentially harm Hasrua GraphQL Engine users. ### When Should I NOT Report a Vulnerability? @@ -19,7 +19,7 @@ To report a security issue, please email us at [build@hasura.io](mailto:build@ha ## Security Vulnerability Response -Each report is acknowledged and analyzed by project's maintianers and the security team within 3 working days. +Each report is acknowledged and analyzed by the project's maintainers and the security team within 3 working days. The reporter will be kept updated at every stage of the issue's analysis and resolution (triage -> fix -> release). diff --git a/code-of-conduct.md b/code-of-conduct.md index b990eb9e151..7d1c8d56c1f 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -3,7 +3,7 @@ ## 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 +contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal @@ -70,4 +70,4 @@ members of the project's leadership. This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html -[homepage]: https://www.contributor-covenant.org \ No newline at end of file +[homepage]: https://www.contributor-covenant.org