svn commit: rev 21377 - avalon/trunk/central/site/src/xdocs/central/laboratory/studio/manual

Author: mcconnell
Date: Wed Jun 16 23:54:21 2004
New Revision: 21377

Modified:
   avalon/trunk/central/site/src/xdocs/central/laboratory/studio/manual/chapter2.xml
Log:
fix some odd characters in the xdocs

Modified: avalon/trunk/central/site/src/xdocs/central/laboratory/studio/manual/chapter2.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/central/laboratory/studio/manual/chapter2.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/central/laboratory/studio/manual/chapter2.xml	Wed Jun 16 23:54:21 2004
@@ -19,8 +19,8 @@
           <p>
             A component is a logical unit of one or more classes and related
             artifacts which together implement a functionality. A component 
-            delivers his functionality only through its "component interface”. 
-            There can be one or more "component interface implementations”.
+            delivers his functionality only through its "component interface". 
+            There can be one or more "component interface implementations".
           </p>
           <p>
             A component is not aware of its functional environment - eg. a 
@@ -32,7 +32,7 @@
             incoming data / objects.
           </p>
           <p>
-            A component is described by a "component type descriptor” (Type) 
+            A component is described by a "component type descriptor" (Type) 
             which holds immutable information associated with the component 
             implementation and its interface (Metadata). Based on information 
             accessible from an instance of Type a container has available the 
@@ -41,7 +41,7 @@
           </p>
           <p>
             In Merlin metadata are stored either in XML or in a binary format.
-            Metadata are created automatically by "Magic” - which is the build
+            Metadata are created automatically by "Magic" - which is the build
             tool for Merlin - or by Eclipse Studio from JavaDoc tags contained
             in the components interface or implementation.
           </p>
@@ -86,7 +86,7 @@
               In Merlin a block is a logical and physical unit of one or more 
               components and its related artifacts. One artifact is the blocks
               metadata which contains information like its containing 
-              components, classloader directives and the "services” it delivers.
+              components, classloader directives and the "services" it delivers.
             </p>
             <p>
               Other artifacts of a block might be persistence mapping 
@@ -95,10 +95,10 @@
             <p>
               Physically a block is deployed in a standard jar file. To make it
               possible to identify blocks visually Merlin blocks are using the 
-              ".bar” file extension.
+              ".bar" file extension.
             </p>
             <p>
-              It's quite usual that the term "block” and the term "component" 
+              It's quite usual that the term "block" and the term "component" 
               are used equivalent. 
             </p>
           </subsection>
@@ -108,19 +108,19 @@
               A block can declare the export of a set of services established by
               the components contained within it. This enables a container to 
               function as a composite component relative to its peers. This 
-              composition is either done by "nested” or by "referenced” blocks.
+              composition is either done by "nested" or by "referenced" blocks.
             </p>
           </subsection>
           <!-- 2.1.2.3 -->
           <subsection name="Nested Blocks" >
             <p>
-              An "include” directive in a block instructs Merlin to include an 
+              An "include" directive in a block instructs Merlin to include an 
               external block within the container. Services exported by the 
               block will be made available to other components at the same 
               level as the included block
             </p>
             <p>
-              With the "include” directive a block is included "by value” into a
+              With the "include" directive a block is included "by value" into a
               block. This is especially useful  to structure larger blocks into 
               smaller reusable blocks. 
             </p>
@@ -128,7 +128,7 @@
           <!-- 2.1.2.4 -->
           <subsection name="Referenced Blocks" >
             <p>
-              A "container” directive is used to reference other blocks / 
+              A "container" directive is used to reference other blocks / 
               containers. Only services declared in the referenced block are 
               accessible by the parent block. This directive is used to assemble
               a whole application by reusable blocks.            
@@ -138,9 +138,9 @@
         <!-- 2.1.3 -->
         <subsection name="Kernel / Container" >
           <p>
-            In Merlin every block is covered by its own container. The "startup”
+            In Merlin every block is covered by its own container. The "startup"
             program, which instantiates and manages all the subsequent 
-            containers is called the "kernel”. 
+            containers is called the "kernel". 
           </p>
           <p>
             Through that architecture Merlin assures a very secure and 
@@ -151,7 +151,7 @@
         <subsection name="Facilities / Application blocks" >
           <p>
             Merlin differentiates two types of blocks: On one hand "application 
-            blocks” and on the other hand "Facilities”.
+            blocks" and on the other hand "Facilities".
           </p>
           <!-- 2.1.4.1 -->
           <subsection name="Facilities" >