Remove broken "Other cool embedded software" link

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

diff --git a/docs/contributing.txt b/docs/contributing.txt
index abfd51684ca46e80116fe7c41361c1912ee3f6ea..c1e3f38031c01789a9a0f316bae5deb4797fbaeb 100644 (file)
--- a/docs/contributing.txt
+++ b/docs/contributing.txt
@@ -5,7 +5,7 @@ This document describes what you need to do to contribute to Busybox, where
 you can help, guidelines on testing, and how to submit a well-formed patch
 that is more likely to be accepted.
 
-The Busybox home page is at: http://busybox.lineo.com
+The Busybox home page is at: http://busybox.net/
 
 
 
@@ -28,8 +28,8 @@ Don't make your work obsolete before you start!
 For information on how to check out Busybox from CVS, please look at the
 following links:
 
-       http://oss.lineo.com/cvs_anon.html
-       http://oss.lineo.com/cvs_howto.html
+       http://busybox.net/cvs_anon.html
+       http://busybox.net/cvs_howto.html
 
 
 Read the Mailing List
@@ -43,15 +43,15 @@ know.
 
 Archives can be found here:
 
-       http://opensource.lineo.com/lists/busybox/
+       http://busybox.net/lists/busybox/
 
-If you have a serious interest in Busybox, i.e. you are using it day-to-day or
+If you have a serious interest in Busybox, i.e., you are using it day-to-day or
 as part of an embedded project, it would be a good idea to join the mailing
 list.
 
 A web-based sign-up form can be found here:
 
-       http://opensource.lineo.com/mailman/listinfo/busybox
+       http://busybox.net/mailman/listinfo/busybox
 
 
 Coordinate with the Applet Maintainer
@@ -294,7 +294,7 @@ are some guidelines on how to test your changes.
    behavior / output is identical between the two.
 
  - Try several different permutations and combinations of the features you're
-   adding (i.e. different combinations of command-line switches) and make sure
+   adding (i.e., different combinations of command-line switches) and make sure
    they all work; make sure one feature does not interfere with another.
 
  - Make sure you test compiling against the source both with the feature
@@ -456,7 +456,7 @@ mailing list if:
 
  - Your changes are broad and touch many different files
  - You are adding a feature
- - Your changes are speculative or experimental (i.e. trying a new algorithm)
+ - Your changes are speculative or experimental (i.e., trying a new algorithm)
  - You are not the maintainer and your changes make the maintainer cringe
 
 The more of the above are true, the better it is to post a patch to the