[project @ 2002-11-09 09:58:56 by chak]

[ghc-hetmet.git] / ghc / docs / users_guide / intro.sgml

diff --git a/ghc/docs/users_guide/intro.sgml b/ghc/docs/users_guide/intro.sgml
index 0162421..6e877b4 100644 (file)
--- a/ghc/docs/users_guide/intro.sgml
+++ b/ghc/docs/users_guide/intro.sgml
@@ -41,8 +41,8 @@
   details.</para>
 
   <para>GHC comes with a large collection of libraries, with
-  everything from parser combinators to networking.  These are all
-  described in <xref linkend="book-hslibs">.</para>
+  everything from parser combinators to networking.  The libraries are
+  described in separate documentation.</para>
 
   <Sect1 id="mailing-lists-GHC">
     <Title>Meta-information: Web sites, mailing lists, etc.</Title>
@@ -79,8 +79,9 @@
       <varlistentry>
        <term>glasgow-haskell-users:</term>
        <listitem>
-         <para>This list is for GHC users to chat among
-         themselves.</para>
+         <para>This list is for GHC users to chat among themselves.
+         If you have a specific question about GHC, please check the
+         FAQ first (<xref linkend="faq">).</para>
 
          <variablelist>
            <varlistentry>
@@ -222,7 +223,7 @@
     <para>Glasgow Haskell is a changing system so there are sure to be
     bugs in it. </para>
 
-    <para>To repot a bug, either:</para>
+    <para>To report a bug, either:</para>
 
     <itemizedlist>
       <listitem>
@@ -230,8 +231,8 @@
     url="http://sourceforge.net/projects/ghc/">SoureForge GHC
     page</ulink>, go to the <quote>bugs</quote> section, click on
     <quote>submit</quote>, and enter your bug report.  You can also
-    check the outstanding bugs here to make sure it hasn't already
-    been reported.  Or:</para>
+    check the outstanding bugs here and search the archives to make
+    sure it hasn't already been reported.  Or:</para>
       </listitem>
       <listitem>
        <para>Email your bug report to
@@ -240,6 +241,25 @@
     </itemizedlist>
 
     <sect2>
+      <title>How do I tell if I should report my bug?</title>
+
+      <para>Take a look at the FAQ (<xref linkend="faq">) and <xref
+      linkend="wrong">, which will give you some guidance as to
+      whether the behaviour you're seeing is really a bug or
+      not.</para>
+
+      <para>If it is a bug, then it might have been reported before:
+      try searching the mailing list archives.  The archives don't
+      have a built-in search facility, but we find that <ulink
+      url="http://www.google.com/">Google</ulink>'s site search works
+      pretty well: enter
+      <quote><literal>site:www.haskell.org</literal></quote> followed
+      by your search term into Google.</para>
+
+      <para>If in doubt, just report it.</para>
+    </sect2>
+
+    <sect2>
       <title>What to put in a bug report</title>
       <indexterm><primary>bug reports</primary><secondary>contents</secondary></indexterm>
 
@@ -358,12 +378,12 @@
     
     <para>The version number of your copy of GHC can be found by
     invoking <literal>ghc</literal> with the
-    <literal>--version</literal> flag (see <xref
+    <literal>&ndash;&ndash;version</literal> flag (see <xref
     linkend="options-help">).</para>
   </sect1>
 
 
-&relnotes
+&relnotes;
 
 </Chapter>