X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fshared_libs.xml;h=89b656a49f37dbbba7bdc56c122db3c8b5a6ed7a;hb=d45197aabb22178066a8ec50d29331786a0c518c;hp=ea5500b89d5d5037e5567b57bf4cbc14b207cdf0;hpb=5c2220aa9aac0fefcba5abbfa3059a6ef138655f;p=ghc-hetmet.git

diff --git a/docs/users_guide/shared_libs.xml b/docs/users_guide/shared_libs.xml
index ea5500b..89b656a 100644
--- a/docs/users_guide/shared_libs.xml
+++ b/docs/users_guide/shared_libs.xml
@@ -16,7 +16,7 @@
     shared between several programs. In contrast, with static linking the
     code is copied into each program. Using shared libraries can thus save
     disk space. They also allow a single copy of code to be shared in memory
-    between several programs that use it. Shared libraires are often used as
+    between several programs that use it. Shared libraries are often used as
     a way of structuring large projects, especially where different parts are
     written in different programming languages. Shared libraries are also
     commonly used as a plugin mechanism by various applications. This is
@@ -218,17 +218,6 @@ ghc -dynamic -shared Foo.o -o libfoo.so
 	    </para>
 	  </listitem>
 	</varlistentry>
-	<varlistentry>
-	  <term>wrapped</term>
-	  <listitem>
-	    <para>
-	      This mode generates a wrapper program which in turn calls the
-	      real program (in the same directory but with a .dyn extension)
-	      in such a way that it can find the shared libraries that it
-	      needs. At the current time this mode is somewhat experimental.
-	    </para>
-	  </listitem>
-	</varlistentry>
       </variablelist>
       To use relative paths for dependent libraries on Linux and Solaris you
       can use the <literal>deploy</literal> mode and pass suitable a -rpath