Index: openacs-4/packages/search/www/doc/guidelines.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/search/www/doc/guidelines.adp,v
diff -u -r1.3.2.1 -r1.3.2.2
--- openacs-4/packages/search/www/doc/guidelines.adp	3 Sep 2021 09:16:47 -0000	1.3.2.1
+++ openacs-4/packages/search/www/doc/guidelines.adp	13 Jul 2023 12:45:46 -0000	1.3.2.2
@@ -35,8 +35,7 @@
 writing concrete functions that follow the specification. For
 example, the implementation of <code>datasource</code> for the
 object type <code>note</code>, looks like this:
-<pre><code>
-ad_proc notes__datasource {
+<pre><code>ad_proc notes__datasource {
     object_id
 } {
     \@author Neophytos Demetriou
@@ -61,8 +60,7 @@
 file which associates the implementation with a contract name. The
 implementation of <code>FtsContentProvider</code> for the object
 type <code>note</code> looks like:
-<pre><code>
-select acs_sc_impl__new(
+<pre><code>select acs_sc_impl__new(
            'FtsContentProvider',                -- impl_contract_name
            'note',                              -- impl_name
            'notes'                              -- impl_owner_name
@@ -75,8 +73,7 @@
 <code>FtsContentProvider</code> and your concrete functions.
 Here&#39;s how an association between an operation and a concrete
 function looks like:
-<pre><code>
-select acs_sc_impl_alias__new(
+<pre><code>select acs_sc_impl_alias__new(
            'FtsContentProvider',                -- impl_contract_name
            'note',                              -- impl_name
            'datasource',                        -- impl_operation_name
@@ -96,8 +93,7 @@
 We do this by adding triggers on the table that stores the content
 items of your object type. Here&#39;s how that part looks like for
 <code>note</code>.
-<pre><code>
-create function notes__itrg ()
+<pre><code>create function notes__itrg ()
 returns opaque as $$
 begin
     perform search_observer__enqueue(new.note_id,'INSERT');