fakeinetd: attempted ipv6-ization (and it's done)

[oweals/busybox.git] / docs / contributing.txt

diff --git a/docs/contributing.txt b/docs/contributing.txt
index ae4ec3ef78bdbd8d69f528832275b0249858a05a..aad43035c65a94aa740a1eeda630bd208a60e016 100644 (file)
--- a/docs/contributing.txt
+++ b/docs/contributing.txt
@@ -73,7 +73,7 @@ Areas Where You Can Help
 ------------------------
 
 Busybox can always use improvement! If you're looking for ways to help, there
-there are a variety of areas where you could help.
+are a variety of areas where you could help.
 
 
 What Busybox Doesn't Need
@@ -214,7 +214,7 @@ These are dirty jobs, but somebody's gotta do 'em.
    is very Perl-specific, but the advice given in here applies equally well to
    C.
 
- - C library funciton use audits: Verifying that functions are being used
+ - C library function use audits: Verifying that functions are being used
    properly (called with the right args), replacing unsafe library functions
    with safer versions, making sure return codes are being checked, etc.
 
@@ -400,7 +400,7 @@ coder, you may be invited to become a committer, thus enabling you to commit
 changes directly to CVS. This is nice because you don't have to wait for
 someone else to commit your change for you, you can just do it yourself.
 
-But note that this is a priviledge that comes with some responsibilities. You
+But note that this is a privilege that comes with some responsibilities. You
 should test your changes before you commit them. You should also talk to an
 applet maintainer before you make any kind of sweeping changes to somebody
 else's code. Big changes should still go to the mailing list first. Remember,