Merge pull request #282 from blaggacao/patch-2

typo: no issue is too small

doc/dev/reporting_bugs.md

@@ -6,7 +6,7 @@ To make the bug report accurate and easy to understand, please try to create bug
 
 - Specific. Include as much details as possible: which version, what environment, what configuration, etc. 
 
-- Reproducible. Include the steps to reproduce the problem. We understand some issues might be hard to reproduce, please includes the steps that might lead to the problem. 
+- Reproducible. Include the steps to reproduce the problem. We understand some issues might be hard to reproduce, please include the steps that might lead to the problem. 
 
 - Isolated. Please try to isolate and reproduce the bug with minimum dependencies. It would significantly slow down the speed to fix a bug if too many dependencies are involved in a bug report. Debugging external systems that rely on operator-sdk is out of scope, but we are happy to provide guidance in the right direction or help with using operator-sdk itself.
 
@@ -19,4 +19,4 @@ It may be worthwhile to read [Elika Etemad’s article on filing good bug report
 We might ask for further information to locate a bug. A duplicated bug report will be closed.
 
 [operator-sdk-issue]: https://github.com/operator-framework/operator-sdk/issues/new
-[filing-good-bugs]: http://fantasai.inkedblade.net/style/talks/filing-good-bugs/
+[filing-good-bugs]: http://fantasai.inkedblade.net/style/talks/filing-good-bugs/