Tiny text changes to clarify how enhancement requests should be raised in GH issues (#2100)

.github/ISSUE_TEMPLATE.md

@@ -6,9 +6,13 @@ fits the defect you are reporting.
 If you open an issue and realize later it is a duplicate of a pre-existing
 open issue, please close yours and add a comment to the other.
 
+Issues can be created for either defects or enhancement requests. If you are a committer than please add the labels "bug" or "feature". If you are not a committer please make clear in the comments which one it is, so that committers can add these labels later.
+
 If you are reporting a defect, please edit the issue description to include the
 information shown below.
 
+If you are reporting an enhancement request, please include information on what you are trying to achieve and why that enhancement would help you.
+
 For more information about reporting issues, see
 https://github.com/openwhisk/openwhisk/blob/master/CONTRIBUTING.md#raising-issues
 

CONTRIBUTING.md

@@ -44,12 +44,14 @@ We look forward to your contributions!
 
 ## Raising issues
 
-Please raise any bug reports on the respective project repository's GitHub issue tracker. Be sure to search the 
+Please raise any bug reports or enhancement requests on the respective project repository's GitHub issue tracker. Be sure to search the 
 list to see if your issue has already been raised.
 
 A good bug report is one that make it easy for us to understand what you were trying to do and what went wrong. 
 Provide as much context as possible so we can try to recreate the issue.
 
+A good enhancement request comes with an explanation of what you are trying to do and how that enhancement would help you.
+
 ### Discussion
 
 Please use the project's developer email list to engage our community: