fix alioth discription in narrative doc

git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@16970 e39458fd-73e7-0310-bf30-c45bca0a0e42

1 files changed, 11 insertions, 10 deletions

diff --git a/doc/narrative_introduction b/doc/narrative_introduction
index 30fb81c5e3..4c831e3b3a 100644
--- a/doc/narrative_introduction
+++ b/doc/narrative_introduction
@@ -23,19 +23,20 @@ structured and how we do our work tracking issues.
 
 The best way to understand is to check out our repository from
 subversion so you have the files on your computer and can follow along
-at home. To do this, you need an Alioth account, and then you just
-need to do the following:
+at home. To do this you just need to do the following:
 
 svn co svn+ssh://<alioth user name>@svn.debian.org/svn/secure-testing
 
-This will check out our working repository after asking for your alioth
-password twice. This is normal and to be expected. After successfully
-downloading, you will have a new directory called secure-testing. Inside
-this directory are a number of subdirectories. The name of the Subversion
-repository is historical, the tracker is not specially related to
-testing-security, but for Debian security at large.
-The data directory is where we do most of our work. If you don't have
-an Alioth account, you can create one at:
+This will check out the working repository (given that you already have
+an alioth account and public key authentication already set up, see
+http://wiki.debian.org/Alioth/SSH).  After successfully downloading,
+you will have a new directory called secure-testing.  Inside this directory
+are a number of subdirectories.  The data directory is where we do most of
+our work.  Note that the name of the Subversion repository is historical;
+the tracker is not specially related to testing-security, but for Debian
+security at large.
+
+If you don't have an Alioth account, you can create one at:
 
 https://alioth.debian.org/account/register.php