Just fixes a few typos and grammatical issues:

- informations/Information
- the the
- usefull/useful
- optionnal/optional
- your/you

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 152d59934547945150c82e79552af9ba51dd1113..5d3b46e0e5fdb266c00b73addf39716ad46efc5c 100644 (file)
--- 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/)
 
 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/)
 
    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
 ------------
 
 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.
 
 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)
 
 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.
 
    72 characters. There must be an empty line separating the summary from
    the body.