You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Contributing Guidelines
2
2
3
-
Thank you for your interest in contributing the project. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
3
+
Thank you for your interest in contributing to the project. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.
4
4
5
5
Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.
6
6
@@ -19,7 +19,7 @@ Please try to include detailed descriptions in issues. Details like these are in
19
19
20
20
Note to keep things tidy and moving along, the maintainers may close issues that appear to be duplicates, are incomplete, or have no discussion for a period of time.
21
21
22
-
If an issue is closed and you feel like it needs to be open, we are always open to discussion.
22
+
If an issue is closed, and you feel like it needs to be open, we are always open to discussion.
23
23
24
24
25
25
## Contributing via Pull Requests
@@ -47,12 +47,12 @@ GitHub provides nice documentation on [forking a repository](https://help.github
47
47
48
48
As with issues above, to keep things tidy and moving along, the maintainers may close PRs that appear to be duplicates, are incomplete and have no discussion for a period of time, or that don't follow the process in spirit.
49
49
50
-
If a PR is closed and you feel like it needs to be open, we are always open to discussion.
50
+
If a PR is closed, and you feel like it needs to be open, we are always open to discussion.
51
51
52
52
53
53
## Development setup
54
54
55
-
Setup the [local enviroment](docs/developer-getting-started.md) to build and test the code locally.
55
+
Setup the [local environment](docs/developer-getting-started.md) to build and test the code locally.
56
56
57
57
## Finding contributions to work on
58
58
Looking at the existing issues is a great way to find something to work on. As the project uses the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
@@ -65,7 +65,7 @@ This project has adopted the [CNCF Code of Conduct](https://github.com/cncf/foun
65
65
66
66
## Security
67
67
68
-
If you discover a potential security issue in this project we ask that you notify project maintainers via email at [email protected]. _Please do not create a public GitHub issue._
68
+
If you discover a potential security issue in this project, we ask that you notify project maintainers via email at [email protected]. _Please do not create a public GitHub issue._
0 commit comments