[Savannah-cvs] [561] fix typos, drop dead links, minor refinements

[ineiev]

Revision: 561
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=561
Author:   ineiev
Date:     2023-02-09 03:23:29 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
fix typos, drop dead links, minor refinements

Modified Paths:
--------------
    trunk/sviki/ShellAccess.mdwn

Modified: trunk/sviki/ShellAccess.mdwn
===================================================================
--- trunk/sviki/ShellAccess.mdwn        2023-02-09 08:21:51 UTC (rev 560)
+++ trunk/sviki/ShellAccess.mdwn        2023-02-09 08:23:29 UTC (rev 561)
@@ -9,15 +9,13 @@
 
 Savane distributes `sv_membersh`, a simple Perl script, that loads
 another Perl script in /etc for configuration. Using a Perl script as a
-login shell may yeld some efficiency concerns.  However, this is what we
+login shell may yield some efficiency concerns.  However, this is what we
 currently do on Savannah; efficiency here has not been a problem.
 
-Another tool is `rssh`
-(<http://packages.debian.org/stable/net/rssh>).
+Another tool is [rssh](//packages.debian.org/stable/net/rssh).
 This package does not check the command line arguments to `cvs` (in
 util.c), though it faced some security issues that `sv_membersh` was also
-vulnerable to
-(<https://gna.org/bugs/?func=detailitem&item_id=4824>).
+vulnerable to.
 It is interesting to check upon that tool even if we do not use it for
 that reason. This package is in C but looks somewhat bloated, so maybe
 it is not a good idea to use it (plus we'd have to patch the CVS
@@ -27,7 +25,7 @@
 Shell access (as root) for Savannah workers
 -------------------------------------------
 
-For those working on savannah itself (support requests, development,
+For those working on Savannah itself (support requests, development,
 etc.), shell and root access may be needed.  (It is not needed to handle
 new project submissions, and it's a good idea to do those for a while
 before worrying about things at the shell level.)  Generally, the idea
@@ -36,10 +34,10 @@
 through fencepost.gnu.org or another known location, as they are not
 open to the whole Internet.
 
-So, the first step is to get ssh access to fencepost.  If you don't
-have that already, see
-<http://www.gnu.org/software/README.accounts.html>.  After that, an
-existing savannah worker can enable your access to savannah.  (By adding
+So, the first step is to get SSH access to fencepost.  If you don't
+have that already, see [GNU accounts
+README](//www.gnu.org/software/README.accounts.html).  After that, an
+existing Savannah worker can enable your access to Savannah.  (By adding
 the key to `mgt0:/root/.ssh/authorized_keys` (in the right section,
 please).  See comments in those files.)
 
@@ -64,7 +62,7 @@
 
 Some sv workers like to have personal accounts on the servers.  The best
 approach for this is to have it be completely separate from normal
-user-level savannah access.  Here was the process for `luca` in April
+user-level Savannah access.  Here was the process for `luca` in April
 2014:
 
 0. Set up a normal account in the web interface to avoid someone later
@@ -77,7 +75,7 @@
     ... 130932 ...
 
 This number is different from the user_id field which shows up in the
-savannah profile as the "Id:" <https://savannah.gnu.org/users/luca>.
+Savannah profile as the "Id:" <https://savannah.gnu.org/users/luca>.
 
 0. On mgt0, add the obvious passwd entry using that uid.  It's not
 technically necessary that the uid's match, but it seems cleaner to
@@ -96,7 +94,7 @@
 
 Bitter truth: the above is the clean way to do it.  However, previous sv
 shell accounts that have been set up (karl, rdoyle, mjflick) conflated
-shell access and savannah web access.  Obviously this can work and be a
+shell access and Savannah web access.  Obviously this can work and be a
 bit more convenient, and equally obviously it makes the default VC
 checkout paths and other things fail.  I (Karl) am not going to explain
 all that here.  If you don't know what I'm talking about or can't figure