X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=ghc%2Fdocs%2Fusers_guide%2Fprimitives.sgml;h=4706671f3ddef49688c4507e4582e5d09a284d89;hb=2dfd507259664e6f28df4a9467a8de34d01d70a0;hp=807e55ad4bba6f80ce1f58c6f7e58c5563371bdd;hpb=dc801dc275fb8f81d482535b4d6317e234bb10f8;p=ghc-hetmet.git

diff --git a/ghc/docs/users_guide/primitives.sgml b/ghc/docs/users_guide/primitives.sgml
index 807e55a..4706671 100644
--- a/ghc/docs/users_guide/primitives.sgml
+++ b/ghc/docs/users_guide/primitives.sgml
@@ -787,7 +787,7 @@ primitive ops compile to one machine instruction or thereabouts.
 
 <para>
 We use the terms &ldquo;reading&rdquo; and &ldquo;writing&rdquo; to refer to accessing
-<emphasis>mutable</emphasis> arrays (see <xref LinkEnd="sect-mutable">), and
+<emphasis>mutable</emphasis> arrays (see <xref linkend="sect-mutable">), and
 &ldquo;indexing&rdquo; to refer to reading a value from an <emphasis>immutable</emphasis>
 array.
 </para>
@@ -835,7 +835,7 @@ objects, because the result is simply the boxed object. So presumably
 it should be entered&mdash;we never usually return an unevaluated
 object!  This is a pain: primitive ops aren't supposed to do
 complicated things like enter objects.  The current solution is to
-return a single element unboxed tuple (see <xref LinkEnd="unboxed-tuples">).
+return a single element unboxed tuple (see <xref linkend="unboxed-tuples">).
 </para>
 
 <para>