[Savannah-cvs] [123] downcasing, wording

[karl]

Revision: 123
          
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=123
Author:   karl
Date:     2014-12-07 19:09:05 +0000 (Sun, 07 Dec 2014)
Log Message:
-----------
downcasing, wording

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

Modified: trunk/sviki/SavannahServices.mdwn
===================================================================
--- trunk/sviki/SavannahServices.mdwn   2014-12-06 23:12:33 UTC (rev 122)
+++ trunk/sviki/SavannahServices.mdwn   2014-12-07 19:09:05 UTC (rev 123)
@@ -1,7 +1,7 @@
 # Services hosted on GNU Savannah servers
 
-The following is the list of Savannah's public servers, organized by the
-VM they run on.
+The following is the list of various network services related to
+Savannah, organized by the VM they run on.
 
 When restarting/reload/reboot a service or a VM, please check the following
 services are working as expected.
@@ -30,7 +30,7 @@
 
 ## frontend
 
-The `frontend.sv.gnu.org` VM runs the Savannah website (the PHP code).
+The `frontend.sv.gnu.org` VM runs the Savannah website (PHP code).
 
 - Main page: <http://savannah.gnu.org> and <http://savannah.nongnu.org>
 
@@ -48,17 +48,17 @@
 The `vcs.sv.gnu.org` VM holds the source code (bzr,cvs,hg,git,svn) and
 webpages (cvs only) repositories, providing various access methods.
 
-(The old GNU arch version control program is still present on the
-server, but perhaps no one is still using it.  In any case, we very
-strongly not recommend using it for any new development, and we won't
-mention it further on this page.  We hope to remove it completely in due
-course.)
+(The old GNU `arch` version control program and repositories are still
+present on the server, but perhaps no one is still using it.  In any
+case, we very strongly not recommend using it for any new development,
+and we won't mention it further on this page.  We hope to remove it
+completely in due course.)
 
 
 ### vcs - project member access (commits)
 
-- SSH: used for read/write access to the repositories by members
-    of a project.  Before using SSH, the Savannah user must upload a
+- ssh: used for read/write access to the repositories by members
+    of a project.  Before using ssh, the Savannah user must upload a
     public ssh key through the Savannah web interface. Upon attempted
     login, this user key is checked against the Savannah MySQL database,
     using the `AuthorizedKeysExec` command defined in
@@ -75,7 +75,7 @@
 
 ### vcs - public anonymous access (read-only)
 
-- RSYNC - read-only anonymous access to the raw repository files.
+- rsync - read-only anonymous access to the raw repository files.
     configuration in `vcs:/etc/rsync.conf`, started with `xinetd` in
     `vcs:/etc/xinetd.d/rsync`.
     - bzr: `rsync://svn.savannah.gnu.org/bzr/<PROJECT>`
@@ -85,22 +85,22 @@
     - svn: `rsync://svn.savannah.gnu.org/svn/<PROJECT>`
     - webcvs: `rsync://svn.savannah.gnu.org/web/<PROJECT>`
 
-- BZR-daemon - read-only anonymous access to BZR repositories.
+- bzr-daemon - read-only anonymous access to bzr repositories.
     configured with `xinetd` in `vcs:/etc/xinetd.d/bzr-hpss`.
     - bzr: `bzr branch bzr://bzr.savannah.nongnu.org/gnewsense/branch`
 
-- CVS-pserver - read-only anonymous access to CVS repositories.
+- cvs-pserver - read-only anonymous access to cvs repositories.
     configured with `xinetd` in `vcs:/etc/xinetd.d/cvs`.
     - cvs: `cvs -d:pserver:address@hidden:/sources/<PROJECT> co <modulename>`
     - webcvs: `cvs -d:pserver:address@hidden:/web/<PROJECT> co <modulename>`
 
-- GIT-daemon - read-only anonymous access to GIT repositories.
+- git-daemon - read-only anonymous access to git repositories.
     configured with `xinetd` in `vcs:/etc/xinetd.d/git`.
     - git: `git clone git://git.savannah.gnu.org/<PROJECT>.git`
 
-- HG - not defined.
+- hg - not defined.
 
-- SVN-daemon - read-only anonymous access to SVN repositories.
+- svn-daemon - read-only anonymous access to svn repositories.
     configured with `xinetd` in `vcs:/etc/xinetd.d/svn`.
     - svn: `svn co svn://svn.savannah.gnu.org/texinfo/modulename`
 
@@ -111,28 +111,28 @@
 - bzr
     - Apache config file: `vcs:/etc/apache2/sites-available/bzr`
     - static welcome page: <http://bzr.savannah.gnu.org/>
-    - BZR CGI Viewer: <http://bzr.savannah.gnu.org/lh/>
-- cvs (the CVS **source code** repositories, not webpages)
+    - bzr cgi Viewer: <http://bzr.savannah.gnu.org/lh/>
+- cvs (the cvs source code repositories, not webpages)
     - Apache config file: `vcs:/etc/apache2/sites-available/cvs`
     - static welcome page: <http://cvs.savannah.gnu.org/>
-    - ViewVC CGI: <http://cvs.savannah.gnu.org/viewvc/>
+    - ViewVC cgi: <http://cvs.savannah.gnu.org/viewvc/>
 - git
     - Apache config file: `vcs:/etc/apache2/sites-available/git`
     - static welcome page: <http://git.savannah.gnu.org/>
-    - CGIT viewer: <http://git.savannah.gnu.org/cgit/>
+    - cgit viewer: <http://git.savannah.gnu.org/cgit/>
     - WebGit viwer: <http://git.savannah.gnu.org/gitweb/>
 - hg
     - Apache config file: `vcs:/etc/apache2/sites-available/hg`
     - static welcome page: <http://hg.savannah.gnu.org/>
-    - HGWEB Viewer: <http://hg.savannah.gnu.org/hgweb/>
+    - hgweb Viewer: <http://hg.savannah.gnu.org/hgweb/>
 - svn
     - Apache config file: `vcs:/etc/apache2/sites-available/svn`
     - static welcome page: <http://svn.savannah.gnu.org/>
-    - ViewVC CGI: <http://svn.savannah.gnu.org/viewvc/>
+    - ViewVC cgi: <http://svn.savannah.gnu.org/viewvc/>
 
 Webpages repositories:
 
-- webcvs (the CVS webpages repositories, propagated to `www.gnu.org`
+- webcvs (the cvs webpages repositories, propagated to `www.gnu.org`
   and `www.nongnu.org`; not source code)
     - Apache config file: same as `cvs` (above)
     - static welcome page: <http://web.cvs.savannah.gnu.org/>
@@ -141,7 +141,7 @@
 - WebGit (experimental):
     - Apache config file: `vcs:/etc/apache2/sites-available/webgit`
     - static welcome page: <http://web.git.savannah.gnu.org/>
-    - CGIT viewer: <http://web.git.savannah.gnu.org/cgit/>
+    - cgit viewer: <http://web.git.savannah.gnu.org/cgit/>
     - WebGit viwer: <http://web.git.savannah.gnu.org/gitweb/>
 
 
@@ -159,66 +159,66 @@
 Configuration details:
 
 - Mirror multiplexor for `ftp.gnu.org`:
-  **NOTE:** The official `ftp.gnu.org` server is managed by the FSF,
-  and Savannah administrators have no access to it.
-    - Web access: <http://ftpmirror.gnu.org> (this url auto-redirects).
+  (The official `ftp.gnu.org` server is managed by the FSF,
+  and Savannah hackers have no access to it.)
+    - web access: <http://ftpmirror.gnu.org> (this url auto-redirects).
     - Apache conf: `dl:/etc/apache2/sites-available/download`
-    - Uses `Apache2::Geo::Mirror` to redirect based on GeoIP.
+    - uses `Apache2::Geo::Mirror` to redirect based on GeoIP.
 
 - Savannah-hosted downloads/releases:
-  **NOTE:** These are mostly intended for Non-GNU projects, as GNU
+  These are mostly intended for nongnu projects, as GNU
   projects are expected to put releases on `ftp.gnu.org`, as detailed in
   the GNU Maintainer Information
   <https://www.gnu.org/prep/maintain/html_node/Automated-FTP-Uploads.html>.
-    - Web Access: <http://download.savannah.gnu.org/releases/>,
+    - web access: <http://download.savannah.gnu.org/releases/>,
     - Apache conf: `dl:/etc/apache2/sites-available/download`
-    - Disk Location: `dl:/srv/download/`
+    - disk location: `dl:/srv/download/`
 
 - Mirrored downloads/releases:
-    - Web Access: <http://download.savannah.gnu.org/releases-redirect/>
+    - web access: <http://download.savannah.gnu.org/releases-redirect/>
     - Apache conf: `dl:/etc/apache2/sites-available/download`
     - Uses `Apache2::Geo::Mirror` to redirect based on GeoIP.
 
 - Savannah top-level download urls:
-    - **NOTE:** These are not especially useful for end-users.
+    - (These are not especially useful for end-users.)
     - <http://download-mirror.savannah.gnu.org>
     - <http://ctan-mirror.savannah.gnu.org>
     - Apache conf: `dl:/etc/apache2/sites-available/download`
 
 - GNU audio-video host:
-    - Web Access: <http://audio-video.gnu.org> and 
<https://audio-video.gnu.org>
-    - HTTP Apache conf: `dl:/etc/apache2/sites-available/audio-video`
-    - HTTPS apache conf: `dl:/etc/apache2/sites-available/audio-video-ssl`
+    - web access: <http://audio-video.gnu.org> and 
<https://audio-video.gnu.org>
+    - http Apache conf: `dl:/etc/apache2/sites-available/audio-video`
+    - https Apache conf: `dl:/etc/apache2/sites-available/audio-video-ssl`
 
 - GNU Arch repositories:
-    - **NOTE:** GNU Arch repositories are obsolete and should not be used.
-    - Web Access: <http://arch.gnu.org>, <http://arch.sv.gnu.org/>,
+    - GNU Arch repositories are obsolete and should not be used.
+    - web access: <http://arch.gnu.org>, <http://arch.sv.gnu.org/>,
       <http://arch.sv.nongnu.org/>.
-    - Apache Conf: `dl:/etc/apache2/sites-available/arch`
-    - Static Welcome Page: `dl:/var/www/arch`
-    - Disk location: `dl:/srv/arch`
+    - Apache conf: `dl:/etc/apache2/sites-available/arch`
+    - static welcome page: `dl:/var/www/arch`
+    - disk location: `dl:/srv/arch`
 
-- RSYNC Access
+- rsync Access
     - rsync start-up configuration file: `dl:/etc/default/rsync`. The
       configuration uses `xinetd`, and so all other options in this file are
       ignored. Instead, the parameters in `dl:/etc/xinetd.d/rsync` are used.
-    - RSYNC Configuration file: `dl:/etc/rsyncd.conf`.
+    - rsync configuration file: `dl:/etc/rsyncd.conf`.
       Available modules:
          - `releases` mapped to `dl:/srv/download`.
          - `audio-video` mapped to `dl:/srv/audio-video`.
-    - Anonymous access using RSYNC protcol:
+    - Anonymous access using rsync protcol:
       `rsync -avhP rsync://dl.sv.gnu.org/releases/<PROJECT>/<FILE>  LOCALFILE`
     - Listing content of a directory:
       `rsync rsync://dl.sv.gnu.org/releases/<PROJECT>/`
-    - All Savannah members can access RSYNC services, using the ssh public
+    - All Savannah members can access rsync services, using the ssh public
       key configured on Savannah website (see ssh section of VCS server,
       above).
-    - Download a file using ssh Public KEY + Savannah User:
+    - Download a file using ssh public key + Savannah User:
       `rsync -avhP <USER>@dl.sv.gnu.org:/releases/<PROJECT>/<FILE> LOCALFILE`
     - Uploading a file (only to projects in which USER is a member):
       `rsync -avhP LOCALFILE  
<USER>@dl.sv.gnu.org/srv/download/<PROJECT>/<FILE>`
 
-- SFTP Access
+- sftp Access
     - `sftp <USER>@dl.sv.gnu.org`
 
 
@@ -241,9 +241,9 @@
     * The server does *not* answer DNS queries directly. Instead, it propagates
       its DNS configuration to `ns1.gnu.org`, and only answers queries from
       `ns1.gnu.org` (enforced with `iptables` rules).
-    * Information about updating DNS is here: [[DNS]].
+    * More about DNS: [[DNS]].
 
-* Savannah Database - `mysql`
+* Savannah database - `mysql`
     * Used in two contexts:
         1. The database for the Savannah PHP code (based on old SourceForge
            code base). These are the registered users on Savannah, registered
@@ -252,8 +252,8 @@
            and those are also stored in the database.
         2. All VMs which allow ssh access based on public ssh keys connect to
            the mysql database, and query the user's ssh key. Users' keys are
-           not stored outside this database (with some exceptions for Savannah
-           administrators, and `fencepost.gnu.org` users).
+           not stored outside this database (with a few exceptions for Savannah
+           hackers and `fencepost.gnu.org` users).
     * MySQL tcp connections are accepted only from `sv.gnu.org`,
       `sv.nongnu.org`, `vcs.sv.gnu.org`, `dl.sv.gnu.org` (enforced with
       `iptables` rules).
@@ -268,7 +268,7 @@
 Configuration details:
 
 * DNS records: the server responds to `lists.gnu.org`, `lists.nongnu.org`
-  and few other FSF related sites.
+  and few other FSF-related sites.
 
 * web access:
     - multiple configuration files in `lists:/etc/apache2/sites-enabled`
@@ -299,9 +299,9 @@
 
 Spam handling is a whole subject in itself: [[ListHelperAntiSpam]].
 
-`lists.gnu.org` is administrated by FSF admins, not by savannah hackers,
+`lists.gnu.org` is administered by FSF admins, not by savannah hackers,
 though savannah hackers have non-root access to the machine.
-See [[ListServer]] for information about mailing-list management.
+See [[ListServer]] for more about mailing-list management.
 
 ## mgt - management