X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=docs%2Fcontributing.txt;h=aad43035c65a94aa740a1eeda630bd208a60e016;hb=0d602e9386cc651ca0ba534b309fce0582fa8e99;hp=0d2f553ed9fd5f479ee83520249d3b2a9e8ada20;hpb=4636aa9dcd500398344b17208f00d2abb098e260;p=oweals%2Fbusybox.git diff --git a/docs/contributing.txt b/docs/contributing.txt index 0d2f553ed..aad43035c 100644 --- 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 @@ -116,7 +116,7 @@ Bug Reporting If you find bugs, please submit a detailed bug report to the busybox mailing list at busybox@busybox.net. A well-written bug report should include a transcript of a shell session that demonstrates the bad behavior and enables -anyone else to duplicate the bug on their own machine. The following is such +anyone else to duplicate the bug on their own machine. The following is such an example: To: busybox@busybox.net @@ -137,7 +137,7 @@ an example: $ date llegal instruction - I am using Debian unstable, kernel version 2.4.19-rmk1 on an Netwinder, + I am using Debian unstable, kernel version 2.4.19-rmk1 on an Netwinder, and the latest uClibc from CVS. Thanks for the wonderful program! -Diligent @@ -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. @@ -231,7 +231,7 @@ These are dirty jobs, but somebody's gotta do 'em. - "Ten Commandments" compliance: (this is a "maybe", certainly not as important as any of the previous items.) - http://www.lysator.liu.se/c/ten-commandments.html + http://www.lysator.liu.se/c/ten-commandments.html Other useful links: @@ -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,