[srm-cvs] CVS Update: - More grammatical fixes

Date: Thu Feb 21 04:10:55 CET 2002
User: Dan Kalowsky
Directory: srmdoc/user

Log Message:
 [1.20]
 - More grammatical fixes
 
Modified files:
           srmdoc/user/faq.xml (version: 1.5)
           srmdoc/user/support.xml (version: 1.2)
           srmdoc/user/using-banana.xml (version: 1.5)

[FILE: /srmdoc/user/faq.xml]

--- srmdoc/user/faq.xml:1.4 Wed Feb 20 17:00:22 2002 GMT
+++ srmdoc/user/faq.xml Thu Feb 21 02:10:55 2002 GMT
@@ -17,8 +17,8 @@
    </question>
    <answer>
     <para>
- SRM is written in C for more performance, and better
- control of threads and sockets.
+ SRM is written in C for better performance, and threading
+ and sockets control.
     </para>
    </answer>
   </qandaentry>
@@ -48,8 +48,8 @@
     <para>
      Yes they are, but you have to consider that SRM can be run on a box other
      then the main server. If SRM is run on the same machine as the webserver,
- you can use the UNIX domain socket interface. According to benchmarks
- this should be around 12 times faster then TCP/IP sockets.
+ it is possible to use the UNIX domain socket interface. According to
+ benchmarks this should be around 12 times faster then TCP/IP sockets.
     </para>
    </answer>
   </qandaentry>

[FILE: /srmdoc/user/support.xml]

--- srmdoc/user/support.xml:1.1 Sun Feb 10 18:22:51 2002 GMT
+++ srmdoc/user/support.xml Thu Feb 21 02:10:55 2002 GMT
@@ -14,11 +14,11 @@
     support issues, reporting bugs, usage questions and general discussion. You
     can subscribe to this mailinglist by sending an e-mail to <ulink
     url="mailto:listar@lists.vl-srm.net?subject=subscribe%20srm">listar@lists.vl-srm.net</ulink>
- with as subject "<literal>subscribe srm</literal>".
+ with a subject of "<literal>subscribe srm</literal>".
    </para>
 
    <para>
- The second one is a list for developing SRM. This is a closed list for
+ The second is a list for developing SRM. This is a closed list for
     development issues only. If you would like to participate in developing SRM
     you can write to <ulink
     url="mailto:group@vl-srm.net">group@vl-srm.net</ulink>.

[FILE: /srmdoc/user/using-banana.xml]

--- srmdoc/user/using-banana.xml:1.4 Sun Feb 10 18:22:51 2002 GMT
+++ srmdoc/user/using-banana.xml Thu Feb 21 02:10:55 2002 GMT
@@ -10,7 +10,7 @@
   <title>Using Bananas</title>
   <para>
    <example>
- <title>Using Bananas from client side scripts</title>
+ <title>Example: Using Bananas from a client side script</title>
     <programlisting>&lt;?php
     /* Starting a connection to the SRM daemon */
     $srm = new SRM ('localhost', 7777);
@@ -31,8 +31,8 @@
   <title>Writing Banana components</title>
   <para>
    Writing Banana objects is almost the same as writing a normal PHP class.
- However there are some specific things which are important. Below you can
- find an example.
+ There are some specific differences which are needed for proper
+ implemntation. Below you can find an example.
   </para>
   <para>
    <figure>
@@ -64,17 +64,19 @@
    </figure>
   </para>
   <para>
- There are only two special things in this class file. The first is the
- <literal>class Uptime extends Banana</literal> line. Basically you make
- an inherited class from the class <classname>Banana</classname>. This insures
- that several basic services, provided by the <classname>Banana</classname>
- class are included. This includes the special <function>run</function>
- method which will fire up the eventloop of the Banana.
+ There are only two special modifications in this class file for it to work
+ as a Banana. The first is the <literal>class Uptime extends Banana</literal>
+ line. A Banana must be an inherited class from the class
+ <classname>Banana</classname>. This insures that several basic services,
+ provided by the <classname>Banana</classname> class are included. This
+ includes the special <function>run</function> method which will begin the
+ Banana eventloop.
   </para>
   <para>
- The second special thing are the last two lines in the example. These
- instantiate the class (<literal>$uptime = new Uptime()</literal>) and the
- second one fires up the <literal>eventloop</literal>. Without calling this method, your
+ The second specific modification is found in the last two lines in the
+ example. The first of these two lines instantiates the class
+ (<literal>$uptime = new Uptime()</literal>), while the second line beings
+ the <literal>eventloop</literal>. Without calling this method, a
    <classname>Banana</classname> will not be accesible remotely.
   </para>
  </section>
@@ -86,17 +88,18 @@
    The eventloop of a <classname>Banana</classname> is intialized by the
    <function>run</function> member function. Without this, the
    <classname>Banana</classname> will not respond to requests from clients.
- The eventloop waits until a request is received from the client, by calling
+ The eventloop then waits until a request is received from a client calling
    a <link linkend="class.srmapp.members">function</link> on that object. An
    event can also be posted by a timer function (currently not implemented).
   </para>
 
   <para>
- When an event is posted, the event handler will dispatch it. There are
- three possible events; 1. <link linkend="user.bananas.eventloop.function">a
+ When an event is posted, the event handler dispatchs it to one of three
+ possible events. These events are: 1.
+ <link linkend="user.bananas.eventloop.function">a
    function is called</link>; 2. <!-- <link
    linkend="user.bananas.eventloop.property-get">-->the value of a property is
- requested<!--</link>--> and 3. <!-- <link
+ requested<!--</link>--> or 3. <!-- <link
    linkend="user.bananas.eventloop.property-set">-->the value of a property is
    set<!--</link>-->.
   </para>
Received on Thu Feb 21 04:10:53 2002