Index: openacs-4/packages/acs-templating/www/doc/TclDocs/publish.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/TclDocs/publish.html,v
diff -u -r1.5 -r1.6
--- openacs-4/packages/acs-templating/www/doc/TclDocs/publish.html	3 Jul 2018 18:19:14 -0000	1.5
+++ openacs-4/packages/acs-templating/www/doc/TclDocs/publish.html	3 Sep 2024 15:37:35 -0000	1.6
@@ -242,7 +242,7 @@
   <font color=red>*</font></td>
        <td align="left">
     
-  The name of the variable in the calling frame that will receive the relative URL of the file in the file system which contains the content blob</td></tr>
+  The name of the variable in the calling frame that will receive the relative URL of the file in the filesystem which contains the content blob</td></tr>
   
   <tr>
   <td align="right"><code>error_ref</code>
@@ -607,7 +607,7 @@
 </tr>
 <tr><td>
 <blockquote>
-Write the content (blob) of a revision into a binary file in the filesystem. The file will be published at the relative URL under each publish root listed under the PublishRoots parameter in the server's INI file (the value returnded by publish::get_page_root is used as the default). The file extension will be based on the revision's mime-type. <br> For example, an revision whose mime-type is { image/jpeg} for an item at { Sitemap/foo/bar} may be written as /web/your_server_name/www/foo/bar.jpg
+Write the content (blob) of a revision into a binary file in the filesystem. The file will be published at the relative URL under each publish root listed under the PublishRoots parameter in the server's INI file (the value returnded by publish::get_page_root is used as the default). The file extension will be based on the revision's mime-type. <br> For example, a revision whose mime-type is { image/jpeg} for an item at { Sitemap/foo/bar} may be written as /web/your_server_name/www/foo/bar.jpg
 </blockquote>
 <dl>
 
@@ -874,7 +874,7 @@
 </tr>
 <tr><td>
 <blockquote>
-Concatenate a list of name-value pairs as returned by <kbd>set_to_pairs</kbd> into a list of { name=value} pairs
+Concatenate a list of name-value pairs as a list of { name=value} pairs
 </blockquote>
 <dl>
 
@@ -893,10 +893,6 @@
   <dt><strong>Returns:</strong>
   <dd>
   An HTML string in format " name=value name=value ..."  
-
-  <dt><strong>See Also:</strong>
-  
-    <dd>proc - <a href="publish.html#publish::set_to_pairs">publish::set_to_pairs</a></br>
 </dl>
 </td>
 </tr>
@@ -1144,46 +1140,6 @@
 
 <p>
 <table width="100%"><tr><td width="100%" bgcolor="#CCCCFF">
-  <a name="publish::set_to_pairs"><font size="+1" weight=bold>publish::set_to_pairs</font></a>
-  
-</td>
-</tr>
-<tr><td>
-<blockquote>
-Convert an ns_set into a list of name-value pairs, in form {name value name value ...}
-</blockquote>
-<dl>
-
-  <strong>Parameters:</strong>
-  <table>
-  
-  <tr>
-  <td align="right"><code>params</code>
-  <font color=red>*</font></td>
-       <td align="left">
-    
-  The ns_set id</td></tr>
-  
-  <tr>
-  <td align="right"><code>exclusion_list</code>
-  <font color=red>*</font></td>
-       <td align="left">
-    
-  {} A list of keys to be ignored</td></tr>
-  
-   </table>
-
-  <dt><strong>Returns:</strong>
-  <dd>
-  A list of name-value pairs representing the data in the ns_set
-
-</dl>
-</td>
-</tr>
-</table>
-
-<p>
-<table width="100%"><tr><td width="100%" bgcolor="#CCCCFF">
   <a name="publish::track_publish_status"><font size="+1" weight=bold>publish::track_publish_status</font></a>
   
 </td>