X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fusing.xml;h=ce7ef7680b2f174ce1cd8f478a42289a1b9481b6;hb=aedb94f5f220b5e442b23ecc445fd38c8d9b6ba0;hp=4b3024ae9b945f6468cb3beb3dac8f72e9d3ae3c;hpb=cae75f82226638691cfa1e85fc168f4b65ddce4d;p=ghc-hetmet.git

diff --git a/docs/users_guide/using.xml b/docs/users_guide/using.xml
index 4b3024a..ce7ef76 100644
--- a/docs/users_guide/using.xml
+++ b/docs/users_guide/using.xml
@@ -1179,7 +1179,8 @@ f foo = foo { x = 6 }
 	  <para>The trouble with orphans is that GHC must pro-actively read the interface
 	    files for all orphan modules, just in case their instances or rules
 	    play a role, whether or not the module's interface would otherwise 
-	    be of any use.  Other things being equal, avoid orphan modules.</para>
+	    be of any use.  See <xref linkend="orphan-modules"/> for details.
+            </para>
 	</listitem>
       </varlistentry>
 
@@ -1905,7 +1906,7 @@ statements or clauses.
 
   <para>GHC can dump its optimized intermediate code (said to be in &ldquo;Core&rdquo; format) 
   to a file as a side-effect of compilation. Non-GHC back-end tools can read and process Core files; these files have the suffix
-  <filename>.hcr</filename>. The Core format is described in <ulink url="http://www.haskell.org/ghc/docs/papers/core.ps.gz">
+  <filename>.hcr</filename>. The Core format is described in <ulink url="../ext-core/core.pdf">
   <citetitle>An External Representation for the GHC Core Language</citetitle></ulink>, 
   and sample tools
   for manipulating Core files (in Haskell) are in the GHC source distribution