*** a/doc/src/sgml/ref/notify.sgml
--- b/doc/src/sgml/ref/notify.sgml
***************
*** 152,169 **** NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable cla
   <refsect1>
    <title>Notes</title>
  
-   <indexterm>
-    <primary>pg_notify</primary>
-   </indexterm>
- 
-   <para>
-    To send a notification you can also use the function
-    <literal><function>pg_notify</function>(<type>text</type>,
-    <type>text</type>)</literal>. The function takes the channel name as the
-    first argument and the payload as the second. The function is much easier
-    to use than the <command>NOTIFY</command> command if you need to work with
-    non-constant channel names and payloads.
-   </para>
    <para>
     There is a queue that holds notifications that have been sent but not
     yet processed by all listening sessions.  If this queue becomes full,
--- 152,157 ----
***************
*** 180,185 **** NOTIFY <replaceable class="PARAMETER">channel</replaceable> [ , <replaceable cla
--- 168,190 ----
     A transaction that has executed <command>NOTIFY</command> cannot be
     prepared for two-phase commit.
    </para>
+ 
+   <refsect2>
+    <title>pg_notify</title>
+ 
+    <indexterm>
+     <primary>pg_notify</primary>
+    </indexterm>
+ 
+    <para>
+     To send a notification you can also use the function
+     <literal><function>pg_notify</function>(<type>text</type>,
+     <type>text</type>)</literal>. The function takes the channel name as the
+     first argument and the payload as the second. The function is much easier
+     to use than the <command>NOTIFY</command> command if you need to work with
+     non-constant channel names and payloads.
+    </para>
+   </refsect2>
   </refsect1>
  
   <refsect1>