Index: openacs-4/packages/new-portal/tcl/datasource-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/new-portal/tcl/datasource-procs.tcl,v
diff -u -N -r1.6.2.1 -r1.6.2.2
--- openacs-4/packages/new-portal/tcl/datasource-procs.tcl	22 Feb 2021 15:16:10 -0000	1.6.2.1
+++ openacs-4/packages/new-portal/tcl/datasource-procs.tcl	13 Sep 2022 13:58:15 -0000	1.6.2.2
@@ -31,33 +31,34 @@
         -spec:required
     } {
 
-        Create a new portal datasource from a specification.  Why use this to define
-        your portal datasources?  Because calling this procedure from your package's
-        post-install procedure is easier than writing PL/SQL for Oracle and PL/pgSQL
-        for Oracle.
+        Create a new portal datasource from a specification.  Why use
+        this to define your portal datasources?  Because calling this
+        procedure from your package's post-install procedure is easier
+        than writing PL/SQL for Oracle and PL/pgSQL for Oracle.
 
         @param spec The specification (format described below)
 
         @author Don Baccus (dhogaza@pacifier.com)
         @see acs_sc::impl::new_from_spec
 
-        The specification is a list of name-value pairs.  Possible names are
+        The specification is a list of name-value pairs. Possible
+        names are:
 
         name          The name of the new datasource
         owner         The package that owns this portlet
         description   A human-readable description (defaults to name)
         params        A list of param key/attributes and their values
         aliases       Service contract aliases clause for acs_sc::impl::new_from_spec
 
-        Each parameter key can be followed by a comma-separated list of attributes
-        in the familiar style of ad_page_contract or ad_form.  Do not include spaces
-        in the list of attributes.  Only two attributes are allowed - "config_required_p"
-        and "configured_p".
+        Each parameter key can be followed by a comma-separated list
+        of attributes in the familiar style of ad_page_contract or
+        ad_form.  Do not include spaces in the list of attributes.
+        Only two attributes are allowed - "config_required_p" and
+        "configured_p".
 
-        See the portal package documentation for the meaning of these two attributes.
-
+        See the portal package documentation for the meaning of these
+        two attributes.
     } {
-
         array set datasource $spec
 
         # Default datasource description to its name
@@ -111,9 +112,9 @@
         {-name:required}
         {-description:required}
     } {
+        Add a new datasource
 
         @author Simon Carstensen (simon@bcuni.net)
-
     } {
         return [db_exec_plsql new_datasource {}]
     }
@@ -125,19 +126,19 @@
         {-key:required}
         {-value:required}
     } {
+        Set def. parameter
 
         @author Simon Carstensen (simon@bcuni.net)
-
     } {
         db_exec_plsql set_def_param {}
     }
 
     ad_proc -public delete {
         {-name:required}
     } {
+        Delete a datasource
 
         @author Don Baccus (dhogaza@pacifier.com)
-
     } {
 
         if { ![db_0or1row get_datasource_id {}] } {