r415 - website

[Thomas Schmidt]

Author: tschmidt
Date: 2005-04-09 22:16:19 +0000 (Sat, 09 Apr 2005)
New Revision: 415

Modified:
   website/index.html
Log:
website: Applied patch from Darren Salt


Modified: website/index.html
===================================================================
--- website/index.html	2005-04-09 22:01:02 UTC (rev 414)
+++ website/index.html	2005-04-09 22:16:19 UTC (rev 415)
@@ -14,7 +14,7 @@
      
      <h3>ssh</h3>
      
-	Now let's configure ssh to use allways the right username when 
+	Now let's configure ssh to allways use the right username when 
 	logging into svn.debian.org (<strong>Note:</strong> You only need this step if 
 	have commit access to svn.debian.org in the pkg-vdr-dvb project,
 	if you just have read-only access, you can skip this step.)
@@ -32,20 +32,20 @@
 	authentication, but believe me, it is much more comfortable 
 	this way.) ;-)
 	<br><br>
-        You have to place the public key into you homedirectory on 
-	svn.debian.org manually by copying it to via scp to 
-	svn.debian.org and appending it to ~/.ssh/authorized_keys:
+        You have to manually place the public key into your home directory
+        on svn.debian.org by copying it via scp and appending it to
+        <tt>~/.ssh/authorized_keys</tt>:
 	<br><br>
 	<code>
 		scp /home/&#060;your_local_username&#062;/.ssh/&#060;name_of_you_sshkey&#062;.pub svn.debian.org:<br>
 		ssh svn.debian.org<br>
 		mkdir ~/.ssh<br>
-		cat &#060;name_of_you_sshkey&#062;.pub >> ~/.ssh/authorized_keys<br>
+		cat &#060;name_of_your_ssh_key&#062;.pub >> ~/.ssh/authorized_keys<br>
 	</code>
 	<br>
 	<strong>Another note:</strong> I can only recommend that you use a 
 	ssh-key with passphrase together with the ssh-agent (ssh-add), but 
-	it is up to you, to decide this.
+	it is up to you to decide this.
      
     <h3>Directory layout</h3>
      
@@ -72,21 +72,21 @@
 	Every package directory in the repository contains 3 subdirectories,
 	trunk, branches and tags. Normal development will be done in the 
 	trunk directory, branches should contain branches of the package 
-	(For example it is planned to add a sarge branch for packages in 
-	sarge soon.), the tags directory contains copies of all uploaded 
-	version of the package (You should not edit anything inside the 
-	tags directory, it should be used to get a specific version of a 
-	package from the repository.)
-     
+        (for example, it is planned to add a sarge branch for packages in 
+        sarge soon), the tags directory contains copies of all uploaded 
+        version of the package (you should not edit anything inside the 
+        tags directory: it should be used to get a specific version of a 
+        package from the repository).
+
      <h3>checking out and building</h3>
      
-	The next step is to checkout the necessary files from the subversion 
-	repository (<strong>Note:</strong> It is recommended that you checkout 
-	only the trunk-directories of the packages, because checking out every 
+        The next step is to checkout the necessary files from the subversion
+        repository (<strong>Note:</strong> It is recommended that you check out 
+        only the trunk directories of the packages, because checking out every
 	module with the trunk, branches and tags directories would consume a 
 	lot of space on your disk.)
 	<br><br>
-	OK, lets checkout and build the vdr package as an example:
+	OK, let's check out and build the vdr package as an example:
 	<br><br>
 	<code>
 		cd basedir<br>