diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2003-08-18 15:27:26 +0000 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2003-08-18 15:27:26 +0000 |
| commit | c16dd085f1e86b287394ab55372c56ee6080b1e7 (patch) | |
| tree | df712e38511bac544d201584873eec1ad539c1fb /docs | |
| parent | a7349a48ff66fed29c855e9d46a27e2ced82e8a1 (diff) | |
minor edit
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/CONTRIBUTE | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/CONTRIBUTE b/docs/CONTRIBUTE index 6bd21d9c3..be2d8e320 100644 --- a/docs/CONTRIBUTE +++ b/docs/CONTRIBUTE @@ -58,9 +58,9 @@ Commenting Comment your source code extensively using C comments (/* comment */), DO NOT use C++ comments (// this style). Commented code is quality code and enables - future modifications much more. Uncommented code much more risk being - completely replaced when someone wants to extend things, since other persons' - source code can get quite hard to read. + future modifications much more. Uncommented code risk having to be completely + replaced when someone wants to extend things, since other persons' source + code can get quite hard to read. General Style @@ -128,7 +128,7 @@ Test Cases improve it, all new features and functions that are added need to be tested in the test suite. Every feature that is added should get at least one valid test case that verifies that it works as documented. If every submitter also - post a few test cases, it won't end up as a heavy burden on a single person! + posts a few test cases, it won't end up as a heavy burden on a single person! How To Make a Patch |