@@ -11,7 +11,7 @@ __Jump To:__
11
11
* [ Additional Resources] ( #additional-resources )
12
12
13
13
## Bug Reports
14
- Bug reports are accepted through the [ this] [ bug-report ] page.
14
+ Bug reports are accepted through [ this] [ bug-report ] page.
15
15
16
16
The following labels are used to track bug related issues: [ Bug] [ label-bug ] ,
17
17
[ Documentation Issue] [ label-doc-issue ] .
@@ -38,7 +38,7 @@ please ensure that your bug report has the following:
38
38
39
39
* A short, descriptive title. Ideally, other community members should be able
40
40
to get a good idea of the issue just from reading the title.
41
- * A succint , detailed description of the problem you're experiencing. This
41
+ * A succinct , detailed description of the problem you're experiencing. This
42
42
should include:
43
43
* Expected behavior of the SDK and the actual behavior exhibited.
44
44
* Any details of your application environment that may be relevant. At
@@ -51,7 +51,7 @@ please ensure that your bug report has the following:
51
51
stacktraces.
52
52
53
53
## Feature Requests
54
- Feature requests are submitted through the [ this] [ feature-request ] page.
54
+ Feature requests are submitted through [ this] [ feature-request ] page.
55
55
56
56
As with Bug Reports, please do a search of the open requests first before
57
57
submitting a new one to avoid duplicates. If you find an existing one, give it
@@ -71,7 +71,7 @@ Open an [issue][issues] with the following:
71
71
72
72
* A short, descriptive title. Ideally, other community members should be able
73
73
to get a good idea of the feature just from reading the title.
74
- * A detailed description of the the proposed feature. Include justification for
74
+ * A detailed description of the proposed feature. Include justification for
75
75
why it should be added to the SDK, and possibly example code to illustrate
76
76
how it should work.
77
77
* [ Markdown] [ markdown ] formatting as appropriate to make the request easier to
@@ -136,11 +136,11 @@ interfaces](https://github.com/reactive-streams/reactive-streams-jvm), the
136
136
change must also contain verification tests using the [ Reactive Streams
137
137
Technology Compatibility
138
138
Kit] ( https://github.com/reactive-streams/reactive-streams-jvm/tree/master/tck )
139
- to ensure specificiation compliance.
139
+ to ensure specification compliance.
140
140
141
141
### Getting Your Pull Request Merged
142
142
All Pull Requests must be approved by at least one member of the SDK team
143
- before it can be merged in. The members only have limited bandwitdth to review
143
+ before it can be merged in. The members only have limited bandwidth to review
144
144
Pull Requests so it's not unusual for a Pull Request to go unreviewed for a few
145
145
days, especially if it's a large or complex one. If, after a week, your Pull
146
146
Request has not had any engagement from the SDK team, feel free to ping a
0 commit comments