Use <important> rather than <caution> when the condition isn't hazardous,

because the result looks to "scary" otherwise.

doc/src/sgml/monitoring.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/monitoring.sgml,v 1.2 2001/10/19 00:46:51 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/monitoring.sgml,v 1.3 2001/11/08 23:39:22 petere Exp $
 -->
 
 <chapter id="monitoring">
@@ -117,7 +117,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
    allowed to change these variables with <command>SET</>.)
   </para>
 
-   <caution>
+   <important>
     <para>
      Since the variables <varname>STATS_COMMAND_STRING</varname>,
      <varname>STATS_BLOCK_LEVEL</varname>,
@@ -127,7 +127,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
      before you will get useful results from the statistical display
      functions.
     </para>
-   </caution>
+   </important>
 
  </sect2>
 

doc/src/sgml/runtime.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.92 2001/11/02 18:39:57 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.93 2001/11/08 23:39:22 petere Exp $
 -->
 
 <Chapter Id="runtime">
@@ -2328,13 +2328,13 @@ default:\
     </varlistentry>
    </variablelist>
 
-   <caution>
+   <important>
     <para>
      It is best not to use <systemitem>SIGKILL</systemitem> to shut down the postmaster. This
      will prevent the postmaster from releasing shared memory and
      semaphores, which you may then have to do by hand.
     </para>
-   </caution>
+   </important>
 
    The <acronym>PID</> of the postmaster process can be found using the
    <application>ps</application> program, or from the file