573df1a8ffa8167e29a8e403a0a0caedac84c972

Author
ncanceill <nicolas.canceill@ens-cachan.org>
Committer
Marc Cornellà <marc.cornella@live.com>
Date

Message

contributing: "eg" -> "e.g." because oxford
see http://www.oxforddictionaries.com/definition/english/e.g.

Diff

 1diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
 2index f86acd66ec0c014b8156eb7f3668cc8d2d77b47e..c1778704118bf6f2bb7cc0bdb69ca35ce56aad7c 100644
 3--- a/CONTRIBUTING.md
 4+++ b/CONTRIBUTING.md
 5@@ -39,7 +39,7 @@ It should include the data gathered as indicated above, along with:
 6 2. What the expected behavior should be
 7 3. What the actual behavior is
 8 
 9-Please copy to anyone relevant (_eg_ plugin maintainers) by mentioning their GitHub handle
10+Please copy to anyone relevant (e.g. plugin maintainers) by mentioning their GitHub handle
11 (starting with `@`) in your message.
12 
13 We will do our very best to help you.
14@@ -51,7 +51,7 @@ your suggestion.
15 
16 If you find one, comment on it so we can know there are more people supporting it.
17 
18-If not, you can go ahead and create an issue. Please copy to anyone relevant (_eg_ plugin
19+If not, you can go ahead and create an issue. Please copy to anyone relevant (e.g. plugin
20 maintainers) by mentioning their GitHub handle (starting with `@`) in your message.
21 
22 ## Submitting Pull Requests
23@@ -78,7 +78,7 @@ If the solution is already reported, try it out and +1 the pull request if the
24 solution works ok. On the other hand, if you think your solution is better, post
25 it with a reference to the other one so we can have both solutions to compare.
26 
27-If not, then go ahead and submit a PR. Please copy to anyone relevant (_eg_ plugin
28+If not, then go ahead and submit a PR. Please copy to anyone relevant (e.g. plugin
29 maintainers) by mentioning their GitHub handle (starting with `@`) in your message.
30 
31 ### You have an addition
32@@ -91,10 +91,10 @@ related to what you want to add.
33 
34 If you find one, try it out and work with the author on a common solution.
35 
36-If not, then go ahead and submit a PR. Please copy to anyone relevant (_eg_ plugin
37+If not, then go ahead and submit a PR. Please copy to anyone relevant (e.g. plugin
38 maintainers) by mentioning their GitHub handle (starting with `@`) in your message.
39 
40-For any extensive change, _eg_ a new plugin, you will have to find testers to +1 your PR.
41+For any extensive change, e.g. a new plugin, you will have to find testers to +1 your PR.
42 
43 ----
44