summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Darqui <andrew.darqui@gmail.com>2016-04-26 14:33:37 -0400
committerAndrew Darqui <andrew.darqui@gmail.com>2016-04-26 14:43:12 -0400
commitd0aeb773c2d01cd5ef69a20be919e74f26f2e799 (patch)
tree7d2ccd95733a1fcc3cdf2f118eab14496db0b56b
parent549aab217331360430aad4b7de68a9916f9e8495 (diff)
downloadtcpdump-d0aeb773c2d01cd5ef69a20be919e74f26f2e799.tar.gz
Just fixes a few typos and grammatical issues:
- informations/Information - the the - usefull/useful - optionnal/optional - your/you
-rw-r--r--CONTRIBUTING18
1 files changed, 9 insertions, 9 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING
index 152d5993..5d3b46e0 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -1,14 +1,14 @@
-Some informations for Contributors
-----------------------------------
-Your want to contribute to Tcpdump, Thanks!
+Some Information for Contributors
+---------------------------------
+You want to contribute to Tcpdump, Thanks!
Please, read these lines.
1) Fork the Tcpdump repository on GitHub from
https://github.com/the-tcpdump-group/tcpdump
(See https://help.github.com/articles/fork-a-repo/)
-2) Setup an optionnal Travis-CI build
- You can setup a travis build for your fork. So, your can test your changes
+2) Setup an optional Travis-CI build
+ You can setup a travis build for your fork. So, you can test your changes
on Linux and OSX before sending pull requests.
(See http://docs.travis-ci.com/user/getting-started/)
@@ -55,11 +55,11 @@ Please, read these lines.
Some remarks
------------
-a) A thorough reading of some other printers code is usefull.
+a) A thorough reading of some other printers code is useful.
-b) Put the the normative reference if any as comments (RFC, etc.).
+b) Put the normative reference if any as comments (RFC, etc.).
-c) Put the the format of packets/headers/options as comments.
+c) Put the format of packets/headers/options as comments.
d) The printer may receive incomplete packet in the buffer, truncated at any
random position, for example by capturing with '-s size' option.
@@ -87,7 +87,7 @@ g) Avoid empty lines in output of printers.
h) A commit message must have:
First line: Capitalized short summary in the imperative (70 chars or less)
- Body: Detailed explanatory text, if necessary. Fold up it to approximately
+ Body: Detailed explanatory text, if necessary. Fold it to approximately
72 characters. There must be an empty line separating the summary from
the body.