Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix grammar, and formatting issues in CODE_OF_CONDUCT.md #2353

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 8 additions & 10 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@

## Preamble

The Nethermind Community was created to foster an open, innovative and inclusive community around open source development.
To clarify expected behaviour in our communities we have adopted the Contributor Covenant. This code of conduct
has been adopted by many other open source communities and we feel it expresses our values well.
The Nethermind Community was created to foster an open, innovative, and inclusive community around open source development.
To clarify expected behavior in our communities we have adopted the Contributor Covenant. This code of conduct
has been adopted by many other open source communities, and we feel it expresses our values well.

## Our Pledge

Expand Down Expand Up @@ -66,18 +66,16 @@ representative at an online or offline event.
## Contributing

Read carefully our Contributing Guidelines to know how to contribute properly in our
project. Members and maintainers must adhere to some rules regarding to pull requests
project. Members and maintainers must adhere to some rules regarding pull requests
reviews and creation of issues and pull requests:

* During code reviews do not comment on coding standards and styles -focus on algorithmical,
structural or naming issues-, help to solve problem.
* During code reviews do not comment on coding standards and styles - focus on algorithmic,
structural or naming issues - help to solve problems.
* When creating an issue or a pull request, follow the templates provided by the repository and
fill in the indicated items correctly. If you do not want to use a template, open a blank issue/PR
and make sure that in its description is not missing any information requested by the templates. Help
and make sure that in its description it is not missing any information requested by the templates. Help
the community to get to know your work better.

make sure your description is not missing any information requested by the templates

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
Expand Down Expand Up @@ -128,7 +126,7 @@ Violating these terms may lead to a permanent ban.
### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within
Expand Down