[elephant-cvs] CVS elephant/doc

[ieslick]

Update of /project/elephant/cvsroot/elephant/doc
In directory clnet:/tmp/cvs-serv575

Modified Files:
	elephant-design.texinfo 
Log Message:
Few tweaks to docs to build them; updated docs on website to match latest checkins

--- /project/elephant/cvsroot/elephant/doc/elephant-design.texinfo	2007/04/27 03:14:55	1.5
+++ /project/elephant/cvsroot/elephant/doc/elephant-design.texinfo	2007/04/30 02:33:17	1.6
@@ -13,7 +13,7 @@
 
 The architecture has been carefully modularized:
 
- at image{ArchDiagram,,4.5in,[Architecture Diagram],.png}
+ at image{ArchDiagram,,4.5in,[Architecture Diagram],png}
 
 To get a feeling for what is happening inside elephant, it is probably
 best to walk through the various major protocols to see how these
@@ -176,7 +176,7 @@
 The BTree protocol almost requires an actual BTree implementation to
 be at all efficient.  Keys and values need to be accessible via the
 cursor API, which means they need to be walked linearly in the sort
-order of the keys (described in @xref{Persistent BTrees}).
+order of the keys (described in @ref{Persistent BTrees}).
 
 An indexed BTree automatically maintains a hash table of the indices
 defined on it so that users can access them by mapping or