Skip to content

Commit e52fd67

Browse files
authored
nermina changes from NRedisStack (#2736)
1 parent a7857e1 commit e52fd67

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

CONTRIBUTING.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22

33
## Introduction
44

5-
First off, thank you for considering contributing to redis-py. We value
6-
community contributions!
5+
We appreciate your interest in considering contributing to redis-py.
6+
Community contributions mean a lot to us.
77

8-
## Contributions We Need
8+
## Contributions we need
99

10-
You may already know what you want to contribute \-- a fix for a bug you
10+
You may already know how you'd like to contribute, whether it's a fix for a bug you
1111
encountered, or a new feature your team wants to use.
1212

13-
If you don't know what to contribute, keep an open mind! Improving
13+
If you don't know where to start, consider improving
1414
documentation, bug triaging, and writing tutorials are all examples of
1515
helpful contributions that mean less work for you.
1616

@@ -166,19 +166,19 @@ When filing an issue, make sure to answer these five questions:
166166
4. What did you expect to see?
167167
5. What did you see instead?
168168

169-
## How to Suggest a Feature or Enhancement
169+
## Suggest a feature or enhancement
170170

171171
If you'd like to contribute a new feature, make sure you check our
172172
issue list to see if someone has already proposed it. Work may already
173-
be under way on the feature you want -- or we may have rejected a
173+
be underway on the feature you want or we may have rejected a
174174
feature like it already.
175175

176176
If you don't see anything, open a new issue that describes the feature
177177
you would like and how it should work.
178178

179-
## Code Review Process
179+
## Code review process
180180

181-
The core team looks at Pull Requests on a regular basis. We will give
182-
feedback as as soon as possible. After feedback, we expect a response
181+
The core team regularly looks at pull requests. We will provide
182+
feedback as as soon as possible. After receiving our feedback, please respond
183183
within two weeks. After that time, we may close your PR if it isn't
184184
showing any activity.

0 commit comments

Comments
 (0)