Merge pull request #516 from VeliovGroup/dev

v1.9.1

.github/ISSUE_TEMPLATE

@@ -1,28 +1,18 @@
 ### I'm having an issue:
- 1. Search [issues](https://github.com/VeliovGroup/Meteor-Files/issues), maybe your issue is already solved
- 2. We have useful threads makred as [`In a case of the fire - Read This`](https://github.com/VeliovGroup/Meteor-Files/issues?utf8=✓&q=label%3A%22In%20a%20case%20of%20the%20fire%20-%20Read%20This%22), read them too
- 3. Before submitting an issue make sure it's only related to `Meteor-Files` package
- 4. If your issue not solved:
-     - Give expressive description
-     - Version of `Meteor-Files` you're experiencing this issue
-     - Version of `Meteor` you're experiencing this issue
-     - Is it *Client* or *Server* issue?
-     - Post *Client* and/or *Server* logs with enabled `debug` option, you can enable "debug" mode in [*Constructor*](https://github.com/VeliovGroup/Meteor-Files/wiki/Constructor)
+  - Give an expressive description
+  - Version of `Meteor-Files` you're experiencing this issue
+  - Version of `Meteor` you're experiencing this issue
+  - Is it *Client* or *Server* issue?
+  - Post *Client* and/or *Server* logs with enabled `debug` option, you can enable "debug" mode in [*Constructor*](https://github.com/VeliovGroup/Meteor-Files/wiki/Constructor)
 
 ### I have a suggestion:
- 1. PRs is always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-Files/compare)
-     - Always send PRs only to `dev` branch, thank you
- 2. If you you can not send a PR for some reason:
-     - Describe your feature / request
-     - How you going to use it? Give a usage example(s)
+  - Describe your feature / request
+  - How you going to use it? Give a usage example(s)
 
-### Documentation is missing something or incorrect (have typos, etc.)
- 1. PRs is always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-Files/compare)
-     - Always send PRs only to `dev` branch, thank you
- 2. If you you can not send a PR for some reason:
-     - Give a short description what you have changed/added and why
-     - Make sure you're using correct markdown markup
-     - Make sure all code blocks starts with tripple ``` (*backtick*) and have a syntax tag, for more read [this docs](https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting)
-     - Post your addition/changes in issue, we will manage it
+### Documentation is missing something or incorrect (have typos, etc.):
+  - Give an expressive description what you have changed/added and why
+  - Make sure you're using correct markdown markup
+  - Make sure all code blocks starts with tripple ``` (*backtick*) and have a syntax tag, for more read [this docs](https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting)
+  - Post your addition/changes in issue, we will manage it
 
 ## Thank you, and do not forget to get rid of this default message

.github/PULL_REQUEST_TEMPLATE

@@ -1,4 +1,11 @@
- 1. Make sure you're sending PR to `dev` branch
- 2. Give a short description what you have changed/added and why
-
-## Thank you for contribution, and do not forget to get rid of this default message
+Thank you for contribution. Before you go:
+  1. Make sure you're using `spaces` for indentation
+  2. Make sure all new code is documented in-code-docs
+  3. Make sure new features, or changes in behavior is documented in README.md
+  4. Make sure this PR was previously discussed, if not create new issue ticket for your PR
+  5. Make sure you're sending PR to `dev` branch
+  6. Give an expressive description what you have changed/added and why
+
+Thank you for making this package better :)
+
+## Do not forget to get rid of this default message