Apply suggestions from code review

Co-authored-by: Alan Dooley <[email protected]>
Signed-off-by: Luca Comellini <[email protected]>

Author: lucacome

CONTRIBUTING.md

@@ -22,7 +22,7 @@ To ask a question please use [Github Discussions](https://github.com/nginxinc/ku
 
 You can also join our [Community Slack channel](https://community.nginx.org/joinslack) which has a wider NGINX audience.
 
-Please reserve Github issues for feature requests and bugs rather than general questions.
+Please reserve GitHub issues for feature requests and bugs rather than general questions.
 
 ## Getting Started
 

ISSUE_LIFECYCLE.md

@@ -10,7 +10,7 @@ To ensure a balance between work carried out by the NGINX engineering team while
 
 3. Determine issue type: This is done with automation where possible, and manually by the owner where necessary. The associated label is applied to the issue.
    #### Possible Issue Types
-   `needs more info`: The owner should use the issue to request information from the creator. If we don't receive the needed information within 7 days automation closes the issue.
+   `needs more info`: The owner should use the issue to request information from the creator. If we don't receive the needed information within 7 days, automation closes the issue.
 
    `bug`: The implementation of a feature is not correct.