From edca0b698637c3fd0a70af7e4752a46afca938d3 Mon Sep 17 00:00:00 2001
From: Narayan Desai <desai@mcs.anl.gov>
Date: Mon, 23 Jan 2006 22:35:40 +0000
Subject: last step of repo switches

git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@1716 ce84e21b-d406-0410-9b95-82705330c041
---
 doc/architecture.xml | 20 +++++++++++++-------
 1 file changed, 13 insertions(+), 7 deletions(-)

(limited to 'doc/architecture.xml')

diff --git a/doc/architecture.xml b/doc/architecture.xml
index abb90c640..7c54fca45 100644
--- a/doc/architecture.xml
+++ b/doc/architecture.xml
@@ -72,7 +72,7 @@
       </listitem>
       <listitem>
 	<para>
-	  Generators and administrative applications.
+	  Plugins and administrative applications.
 	</para>
       </listitem>
       <listitem>
@@ -104,6 +104,12 @@
       simple as possible. The normal configuration process consists of
       four main steps:</para>
 
+<!--     <procedure> -->
+<!--       <title>Bcfg2 Client Execution Process</title> -->
+
+<!--       <step>foo</step> -->
+<!--     </procedure> -->
+
     <variablelist>
       <varlistentry>
 	<term>Probe Execution</term>
@@ -316,18 +322,18 @@
 	      literal configuration information. After the abstract
 	      configuration is created, each configuration entry must
 	      be bound to a client-specific value. The Bcfg2 server
-	      uses generators to provide these client-specific bindings.
+	      uses plugins to provide these client-specific bindings.
 	    </para>
 
 	    <para>
 	      The Bcfg2 server core contains a dispatch table that
-	      describes which generator can handle requests of a
-	      particular type. The responsible generator is located
+	      describes which plugins can handle requests of a
+	      particular type. The responsible plugin is located
 	      for each entry. It is called, passing in the
 	      configuration entry and the client's metadata. The
-	      behavior of generators is explicitly undefined, so as to
-	      allow maximum flexibility. The behavior of the stock
-	      generators is documented elsewhere in this manual.
+	      behavior of plugins is explicitly undefined, so as to
+	      allow maximum flexibility. The behaviors of the stock
+	      plugins are documented elsewhere in this manual.
 	    </para>
 
 	    <para>
-- 
cgit v1.2.3-1-g7c22