Repository: logging-log4j2 Updated Branches: refs/heads/master 4c3459d79 -> 54ee74c6d
Fix grammar in CONTRIBUTING.md Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/54ee74c6 Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/54ee74c6 Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/54ee74c6 Branch: refs/heads/master Commit: 54ee74c6d698df67776c9143f47c939c88c52531 Parents: 4c3459d Author: Matt Sicker <boa...@gmail.com> Authored: Sun Jan 29 11:26:27 2017 -0600 Committer: Matt Sicker <boa...@gmail.com> Committed: Sun Jan 29 11:26:27 2017 -0600 ---------------------------------------------------------------------- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/54ee74c6/CONTRIBUTING.md ---------------------------------------------------------------------- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b3b5da3..526d871 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -28,7 +28,7 @@ follow so that we can have a chance of keeping on top of things. + Make sure you have a [JIRA account](https://issues.apache.org/jira/). + Make sure you have a [GitHub account](https://github.com/signup/free). -+ If you're planning to implement a new feature it makes sense to discuss you're changes on the [dev list](https://logging.apache.org/log4j/2.x/mail-lists.html) first. This way you can make sure you're not wasting your time on something that isn't considered to be in Apache Log4j's scope. ++ If you're planning to implement a new feature it makes sense to discuss your changes on the [dev list](https://logging.apache.org/log4j/2.x/mail-lists.html) first. This way you can make sure you're not wasting your time on something that isn't considered to be in Apache Log4j's scope. + Submit a ticket for your issue, assuming one does not already exist. + Clearly describe the issue including steps to reproduce when it is a bug. + Make sure you fill in the earliest version that you know has the issue.
