From 801476f78b702be863f7d6b0035064b9ed6872fa Mon Sep 17 00:00:00 2001 From: "dr.dimitru" Date: Sat, 27 Jan 2018 05:28:00 +0300 Subject: [PATCH] Package's meta update --- CONTRIBUTING.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5cda21e..993aa9e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,7 +1,7 @@ ### I'm having an issue: 1. Search [issues](https://github.com/VeliovGroup/Meteor-logger-file/issues?utf8=✓&q=is%3Aissue), maybe your issue is already solved 2. Before submitting an issue make sure it's only related to `ostrio:loggerfile` package - 3. If your issue not solved: + 3. If your issue is not solved: - Give an expressive description of what is went wrong - Version of `ostrio:loggerfile` you're experiencing this issue - Version of `Meteor` you're experiencing this issue @@ -11,17 +11,17 @@ - If you're getting an error or exception, please provide its full stack-trace as plain-text or screenshot ### I have a suggestion: - 1. PRs is always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-logger-file/pulls) - 2. If you you can not send a PR for some reason: + 1. PRs are always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-logger-file/pulls) + 2. If you're can not send a PR for some reason: - Create a new issue ticket - 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-logger-file/pulls) - 2. If you you can not send a PR for some reason: + 1. PRs are always welcome - [send a PR](https://github.com/VeliovGroup/Meteor-logger-file/pulls) + 2. If you're can not send a PR to docs for some reason: - Create a new issue ticket - 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 as issue ticket, we will manage it \ No newline at end of file + - Make sure all code blocks starts with triple ``` (*backtick*) and have a syntax tag, for more read [this docs](https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting) + - Post addition/changes as issue ticket, we will manage it \ No newline at end of file