Index: openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.adp,v
diff -u -N -r1.4.2.1 -r1.4.2.2
--- openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.adp	2 Mar 2019 19:30:04 -0000	1.4.2.1
+++ openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.adp	16 Dec 2019 17:14:38 -0000	1.4.2.2
@@ -202,7 +202,7 @@
 [ad_footer]"
 
 doc_return 200 text/html $page_content
-</pre><p>The old convention was to call <code class="computeroutput">ReturnHeaders</code> and then <code class="computeroutput">ns_write</code> for each distinct chunk of the
+</pre><p>The old convention was to call <code class="computeroutput">util_return_headers</code> and then <code class="computeroutput">ns_write</code> for each distinct chunk of the
 page. This approach has the disadvantage of tying up a scarce and
 valuable resource (namely, a database handle) for an unpredictable
 amount of time while sending packets back to the browser, and so it