diff options
| author | Christian Zeller <chrizel@posteo.de> | 2019-05-15 16:10:48 +0200 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2019-05-15 17:52:30 +0200 |
| commit | 1cac9b4bf2331f82f84e1c8cbc15fe38a18cc4ac (patch) | |
| tree | 2d2daaf38b5e0c35638200d0db98818e4622bdf0 | |
| parent | f63c5c7bfecd9fb4b4f5da088a84968fa2929a50 (diff) | |
| download | redis-1cac9b4bf2331f82f84e1c8cbc15fe38a18cc4ac.tar.gz | |
Typo fixes in CONTRIBUTING
| -rw-r--r-- | CONTRIBUTING | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING index 5fb038e49..000edbeaf 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -14,7 +14,7 @@ each source file that you contribute. PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected bugs in the Github issues system. We'll be very happy to help you and provide - all the support in the mainling list. + all the support in the mailing list. There is also an active community of Redis users at Stack Overflow: @@ -25,7 +25,7 @@ each source file that you contribute. 1. If it is a major feature or a semantical change, please don't start coding straight away: if your feature is not a conceptual fit you'll lose a lot of time writing the code without any reason. Start by posting in the mailing list -and creating an issue at Github with the description of, excatly, what you want +and creating an issue at Github with the description of, exactly, what you want to accomplish and why. Use cases are important for features to be accepted. Here you'll see if there is consensus about your idea. |