Address the comments in the PR

Improve wording
Add code-blocks to improve readability

.github/ISSUE_TEMPLATE.md

@@ -1,33 +1,30 @@
-Welcome dear friend! We, the rest of the NativeScript community really
+Dear friend, we, the rest of the NativeScript community really
 appreciate your feedback! While we are doing all we can to take care of every
 issue, sometimes we get overwhelmed. Because of that, we will consider issues
-that are not constructive or report problems that cannot be reproduced "dead".
-In accordance, we will treat feature requests or bug reports with unanswered
+that are not constructive or problems that cannot be reproduced "dead".
+Additionally, we will treat feature requests or bug reports with unanswered
 questions regarding the behavior/reproduction for more than 20 days "dead". All
 "dead" issues will get closed.
 
-## Please, help the others with the details below:
+## Please, provide the details below:
 
-### Did you verify this is a real problem with a search in
-[StackOverflow](http://stackoverflow.com/questions/tagged/nativescript)
-and the other issues here?
+### Did you verify this is a real problem by searching [Stack Overflow](http://stackoverflow.com/questions/tagged/nativescript) and the [other open issues in this repo](https://github.com/NativeScript/nativescript/issues)?
 
 ### Tell us about the problem
-Please, ensure your title is less than 50 characters and starts with a capital
-letter. We strive to follow the guidelines in the
-[How to Write a Git Commit Message] (http://chris.beams.io/posts/git-commit/)
-article for PR titles.
+Please, ensure your title is less than 63 characters long and starts with a capital
+letter.
 
-### Which platform does it happen on?
+### Which platform(s) does your issue occur on?
 iOS/Android/Both
 
-### Which versions of the NativeScript elements did you use?
-CLI: (run tns --version to fetch it)
+### Please provide the following version numbers that your issue occurs with:
+CLI: (run `tns --version` to fetch it)
 Cross-platform modules: (check the 'version' attribute in the
 `node_modules/tns-core-modules/package.json` file in your project)
-Runtime: (check the entries in the package.json file of your project)
+Runtime(s): (look for the `"tns-android"` and `"tns-ios"` properties in your
+project’s `package.json` file)
 
-### Try to recall what were you doing
+### Please tell us how to recreate the issue in as much detail as possible.
 
-### Is there code involved? Can you share the minimum of it to get the problem?
+### Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,12 +1,18 @@
 Dear friend, we, the rest of the NativeScript community thank you for your
-contribution! As we want to present a really nice, readable changelog with each
-release, we ask you to fill the following information:
+contribution! Because we want to present a really nice, readable changelog with each
+release, please provide the following information:
 
-### Inform what relation and with which issue does it have (in other words, delete the unnecessary):
+### Create a meaningful title
+Please, ensure your title is less than 50 characters and starts with a capital
+letter. We strive to follow the guidelines in the
+[How to Write a Git Commit Message] (http://chris.beams.io/posts/git-commit/)
+article for PR titles.
+
+### Does your commit message include the wording below to reference a specific issue in this repo?
 Fixes/Implements #[Issue Number].
 
-### Does it have [unit tests](https://github.com/NativeScript/NativeScript/blob/master/running-tests.md)?
+### Does your pull request have [unit tests](https://github.com/NativeScript/NativeScript/blob/master/running-tests.md)?
 If not, why?
-If not, can you list any steps to test it manually?
+If not, please tell us why tests are not included, and list all steps needed to test your pull request manually.