Index: openacs-4/packages/acs-core-docs/www/db-api.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/db-api.html,v
diff -u -r1.53.2.9 -r1.53.2.10
--- openacs-4/packages/acs-core-docs/www/db-api.html	13 Jul 2023 12:43:19 -0000	1.53.2.9
+++ openacs-4/packages/acs-core-docs/www/db-api.html	1 Aug 2024 08:03:39 -0000	1.53.2.10
@@ -91,7 +91,7 @@
           Another very important reason for using bind variables is
 	  performance. Oracle can cache previously parsed queries. If
 	  there are values in the where clause, that is how the query
-	  is cached. It also performs bind variable susbstitution
+	  is cached. It also performs bind variable substitution
 	  after parsing the SQL statement. This means that SQL
 	  statements that use bind variables will always match
 	  (assuming all else is the same) while SQL statements that do
@@ -283,9 +283,7 @@
 	    <code class="computeroutput">
 	      <a name="devguide.dbapi_db_abort_transaction"></a>db_abort_transaction
 	    </code>
-	</span></dt><dd><pre class="programlisting">
-db_abort_transaction
-	  </pre><p>Aborts all levels of a transaction. That is if this is called within
+	</span></dt><dd><pre class="programlisting">db_abort_transaction</pre><p>Aborts all levels of a transaction. That is if this is called within
 	    several nested transactions, all of them are terminated. Use this instead of
 	    <code class="computeroutput">db_dml "abort" "abort transaction"</code>. 
 	    
@@ -337,8 +335,7 @@
     to skip this row and quit looping.
     </p><p>
     Notice the nonstandard numbering (everything
-    else in Tcl starts at 0); the reason is that the graphics designer, a non
-    programmer, may wish to work with row numbers.
+    else in Tcl starts at 0); the reason is that the graphics designer, a non-programmer, may wish to work with row numbers.
     </p><p>
        Example:
     </p><pre class="programlisting">