typos in multiple files (#730)

This commit is contained in:
Shivam Agarwal 2018-10-15 12:55:35 +05:30 committed by Shahidh K Muhammed
parent b91704e3ca
commit ddcd3dc9ae
3 changed files with 5 additions and 5 deletions

View File

@ -3,7 +3,7 @@
*First*: if you're unsure or afraid of anything, just ask or submit the issue or *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 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 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. the way of that.
However, for those individuals who want a bit more guidance on the best way to However, for those individuals who want a bit more guidance on the best way to

View File

@ -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 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 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. - You want to report any other security risk that could potentially harm Hasrua GraphQL Engine users.
### When Should I NOT Report a Vulnerability? ### 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 ## 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). The reporter will be kept updated at every stage of the issue's analysis and resolution (triage -> fix -> release).

View File

@ -3,7 +3,7 @@
## Our Pledge ## Our Pledge
In the interest of fostering an open and welcoming environment, we as 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 our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and expression, size, disability, ethnicity, sex characteristics, gender identity and expression,
level of experience, education, socio-economic status, nationality, personal 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, 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 available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[homepage]: https://www.contributor-covenant.org [homepage]: https://www.contributor-covenant.org