shannon     2002/06/07 14:10:52

  Modified:    src/documentation/xdocs/userdocs/concepts databases.xml
  Log:
  Previous commit was premature.
  This commit clarifies the language.
  Some edits.
  
  Revision  Changes    Path
  1.2       +9 -9      
xml-cocoon2/src/documentation/xdocs/userdocs/concepts/databases.xml
  
  Index: databases.xml
  ===================================================================
  RCS file: 
/home/cvs/xml-cocoon2/src/documentation/xdocs/userdocs/concepts/databases.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- databases.xml     28 Apr 2002 18:11:12 -0000      1.1
  +++ databases.xml     7 Jun 2002 21:10:52 -0000       1.2
  @@ -16,13 +16,13 @@
          <p>
                Publishing dynamic content or creating web-applications at
                some point often involves database access. Apache Cocoon
  -             offers a number of different facilities to access databases,
  -             (object) relational and XML. This document aims to give an
  -             overview over the different choices to access (object)
  +             offers a number of different facilities to access
  +             (object) relational and XML databases. This document provides
  +             an overview of the different ways to access (object)
                relational databases.
          </p>
          <p>
  -             This document will not explain how to setup database
  +             This document will not explain how to set up database
                connectivity with Apache Cocoon. For this, see <link
                  href="../../developing/datasources.html">here.</link>
          </p>
  @@ -37,14 +37,14 @@
   
        <s1 title="Actions">
          <p>
  -             <link href="actions.html">Actions</link> are code that is executed
  -             during pipeline setup and its outcome can change how the pipeline is
  -             assembled. This way a pipeline can for example contain an alternative
  +             <link href="actions.html">Actions</link> are code to be executed
  +             during pipeline setup. The outcome of an action can change how the 
pipeline is
  +             assembled. For exampl, a pipeline may produce an alternative
                page to display when a database operation failed.
          </p>
          <p>
  -             Actions are especially great to insert, change, or delete data. By
  -             using the pipeline switching feature of actions, pages can be simpler
  +             Actions are especially great for inserting, changing, or deleting 
data. 
  +             When pipeline switching features of actions are used, pages can be 
simpler
                as they are only concerned with one view - either successful operation
                or failure.
          </p>
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to