[cig-commits] r13297 - doc/snac

[sue at geodynamics.org]

Author: sue
Date: 2008-11-12 10:10:02 -0800 (Wed, 12 Nov 2008)
New Revision: 13297

Modified:
   doc/snac/snac.lyx
Log:
a few minor edits

Modified: doc/snac/snac.lyx
===================================================================
--- doc/snac/snac.lyx	2008-11-12 17:08:35 UTC (rev 13296)
+++ doc/snac/snac.lyx	2008-11-12 18:10:02 UTC (rev 13297)
@@ -1,4 +1,4 @@
-#LyX 1.5.3 created this file. For more info see http://www.lyx.org/
+#LyX 1.5.1 created this file. For more info see http://www.lyx.org/
 \lyxformat 276
 \begin_document
 \begin_header
@@ -1525,8 +1525,12 @@
 \begin_layout Standard
 SNAC is readily customizable through writing a ``plugin,'' a shared object
  that can be loaded dynamically at run-time.
- A plugin is typically stored in Snac/plugins directory and Together with
- the Entry Point design, the time and effort to 
+ A plugin is typically stored in the 
+\family typewriter
+Snac/plugins
+\family default
+ directory and, together with the Entry Point design, the time and effort
+ to [TODO sentence incomplete]
 \end_layout
 
 \begin_layout Subsection
@@ -1573,7 +1577,7 @@
  When an EP is called, it runs each of the function pointers in its list
  sequentially, with the same arguments.
  Since the SNAC Context calls the EPs in a specific hierarchy, an application's
- set of EPs define the call-tree for an application.
+ set of EPs defines the call-tree for an application.
 \end_layout
 
 \begin_layout Standard
@@ -1602,7 +1606,7 @@
 
 \begin_layout Standard
 The two diagrams below outline the entry points set up in SNAC.
- It is represented as tree-like hierarchy: If a ``hook'' calls other entry
+ It is represented as a tree-like hierarchy: if a ``hook'' calls other entry
  points, either in its own function or other normal functions it calls,
  the called entry points are below and offset to the right of that hook.