[Devil-linux-commit] docs/developer new-developer.txt,1.2,1.3

[<fr...@pr...>]

Update of /cvsroot/devil-linux/docs/developer
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19956

Modified Files:
	new-developer.txt 
Log Message:
typos and small corrections

Index: new-developer.txt
===================================================================
RCS file: /cvsroot/devil-linux/docs/developer/new-developer.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- new-developer.txt	28 Jan 2004 22:24:56 -0000	1.2
+++ new-developer.txt	28 Jan 2004 22:42:46 -0000	1.3
@@ -1,25 +1,25 @@
-You've just become a new Devil-Linux Developer. So what is there
-that is different from before? Let me give you a short getting 
-started guide:
+You've just become a new Devil-Linux Developer. So what is there that is
+different from before? Let me give you a short getting-started guide:
 
   * If you have not done so before run "ssh-keygen -t rsa" from the 
-    account you will be doing you development at. Hit enter till you 
+    account you will be doing your development at. Hit enter till you 
     are back at the prompt.
 
   * Go to http://sourceforge.net/account/editsshkeys.php (might need
     to log in to SF first if you are not prompted for your password)
 
-  * Run "cat ~/.ssh/id_rsa.pub" and copy and paste this into the text 
+  * Run "cat ~/.ssh/id_rsa.pub" and copy-and-paste this into the text 
     box on the page referenced above and click "Update" below the box.
 
-    The output is actually _one_ line like the following (folded for readability):
+    The output is actually _one_ line like the following (folded for
+    readability):
 
        ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAp1gM1XLESnStKjFd4zpxxVgA4aZqa
        DPVufJJUnVYwU0FBiMWJbDXXXSn4tY/KbWWKhYBbnRVZzSY0YmhGdKQoYyrQqJy7S
        sOdFkWGkay9FOgub526r2mxjnn/0fnripE6NMHaaUjLHldR4WtYvwb1tpQSiQPqWZ
        8f0a7KMVjsFM= user@host
 
-    It takes some hours (maybe up to 24 or so) till your ssh private key is
+    It takes some hours (maybe up to 24 or so) till your ssh public key is
     installed on the CVS server. In the meantime you have to enter your SF
     password everytime you run the cvs command.
 
@@ -35,9 +35,9 @@
       alias cvs_sf='cvs -z3 -d:ext:${SFUSER}@cvs.sourceforge.net:/cvsroot/devil-linux'
 
   * Let's test this right aways. So either login again or open a new
-    "konsole" (if you use KDE), or a new shell. 
+    "konsole" (if you use KDE) or a new shell. 
     
-    Check with "alias cvs_sf" that the alias exists and the run "cvs_sf
+    Check with "alias cvs_sf" that the alias exists and then run "cvs_sf
     checkout -c" which should show you the modules that you can check out,
     eg.
     
@@ -47,9 +47,8 @@
       scripts      scripts
       web          web
 
-  * You possibly already checked out the build module before you 
-    became a developer. Now you need to check out everything again.
-    So run eg.
+  * You possibly already checked out the build module before you became a
+    developer. Now you need to check out everything again. So run eg.
       cvs_sf checkout build    # note: need to specify 'cvs_sf'
     to get the up to date build system.
     
@@ -58,7 +57,8 @@
       cd build
       cvs update -d -P         # note: no need to specify 'cvs_sf' here
       
-    If you don't do that you always have to use 'cvs_sf' !!!
+    If you don't do the checkout with 'cvs_sf' you always have to use
+    'cvs_sf' !!!
 
   * Last but not least you might want to sign up on the CVS commit
     mailinglist so you see immediately when change you sent in to one of the
@@ -70,7 +70,7 @@
 
 Hope that should get you going as fast as possible. If I have forgotten
 something it's because it has been such a long time since when I had to do
-all this ;-)
+all this for myself ;-)
 
 Friedrich Lobenstock <fl...@fl...>
 $Id$