From 567c490a9786e204c444d4d533a2def39465cc17 Mon Sep 17 00:00:00 2001
From: Dave Abrahams <dave@boostpro.com>
Date: Tue, 17 Jun 2003 14:16:16 +0000
Subject: [PATCH] Fix errors reported by John Torjo <john-at-torjo.com>.

[SVN r18824]
---
 doc/paper/src/metafunctions.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/paper/src/metafunctions.sgml b/doc/paper/src/metafunctions.sgml
index eb31b12..4136b27 100644
--- a/doc/paper/src/metafunctions.sgml
+++ b/doc/paper/src/metafunctions.sgml
@@ -29,7 +29,7 @@ However, this model is far too limiting: it restricts the metafunction result no
 template< typename T1, typename T2 >
 struct derive
 {
-    struct type : N1, N2 {};
+    struct type : T1, T2 {};
 };
 
 // silly specialization, but demonstrates "returning" int
@@ -58,7 +58,7 @@ While syntactically simple, the simple template metafunction form does not alway
 <![CDATA[
 // returns F(T1,F(T2,T3))
 template<
-      template<typename> class F
+      template<typename,typename> class F
     , typename T1
     , typename T2
     , typename T3
@@ -94,7 +94,7 @@ However, things begin to break down noticeably when we want to <quote>return</>
 <programlisting>
 <![CDATA[
 // returns G s.t. G(T1,T2,T3) == F(T1,F(T2,T3))
-template< template<typename> class F >
+template< template<typename,typename> class F >
 struct compose_self
 {
     template<