[Savannah-cvs] [578] fix markup

[ineiev]

Revision: 578
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=578
Author:   ineiev
Date:     2023-02-13 05:03:05 -0500 (Mon, 13 Feb 2023)
Log Message:
-----------
fix markup

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

Modified: trunk/sviki/UserAuthentication.mdwn
===================================================================
--- trunk/sviki/UserAuthentication.mdwn 2023-02-13 10:00:44 UTC (rev 577)
+++ trunk/sviki/UserAuthentication.mdwn 2023-02-13 10:03:05 UTC (rev 578)
@@ -7,7 +7,7 @@
 2. These accounts are used across all Savannah systems.
 3. Users can upload ssh public keys using the web interface at:
    <https://savannah.gnu.org/my/admin/editsshkeys.php>
-4. ssh public keys are stored in the MySQL database on
+4. ssh public keys are stored in the database on
    `internal0.savannah.gnu.org` (see [[SavannahServices]]).
 
 User information can be viewed by anyone on Savannah website.
@@ -15,7 +15,7 @@
 
 ### Database access
 
-In the MySQL database, currently `internal0.savannah.gnu.org` but
+In the database, currently `internal0.savannah.gnu.org` but
 accessible from a set of hosts, the following SQL commands
 can be used to examine accounts:
 
@@ -94,7 +94,7 @@
 least one record in the `user_group` table.  Maybe someday this will be
 changed.
 
-These servers use the MySQL database in two ways:
+These servers use the database in two ways:
 
 * Unix user management, using
   [nsswitch](http://en.wikipedia.org/wiki/Name_Service_Switch) and
@@ -148,6 +148,7 @@
 ### ssh authentication
 
 The file `/etc/ssh/sshd_config` on `download0:` and `vcs0:` servers have the 
line:
+
     ...
     AuthorizedKeysCommand      /root/bin/sv_get_authorized_keys
     ...