[Gnash-commit] gnash/doc/C amf.xml cygnal.man-xml extensions.x... [release_0_8_2_rc1]

[Russ Nelson]

CVSROOT:        /sources/gnash
Module name:    gnash
Branch:         release_0_8_2_rc1
Changes by:     Russ Nelson <nelsonrn>  08/03/04 21:01:53

Modified files:
        doc/C          : amf.xml cygnal.man-xml extensions.xml 
                         gnash.man-xml gprocessor.man-xml rtmp.xml 

Log message:
        Fixed typos.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/amf.xml?cvsroot=gnash&only_with_tag=release_0_8_2_rc1&r1=1.5&r2=1.5.2.1
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/cygnal.man-xml?cvsroot=gnash&only_with_tag=release_0_8_2_rc1&r1=1.1&r2=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/extensions.xml?cvsroot=gnash&only_with_tag=release_0_8_2_rc1&r1=1.5&r2=1.5.2.1
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/gnash.man-xml?cvsroot=gnash&only_with_tag=release_0_8_2_rc1&r1=1.1&r2=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/gprocessor.man-xml?cvsroot=gnash&only_with_tag=release_0_8_2_rc1&r1=1.1&r2=1.1.2.1
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/rtmp.xml?cvsroot=gnash&only_with_tag=release_0_8_2_rc1&r1=1.7&r2=1.7.2.1

Patches:
Index: amf.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/amf.xml,v
retrieving revision 1.5
retrieving revision 1.5.2.1
diff -u -b -r1.5 -r1.5.2.1
--- amf.xml     20 Feb 2008 11:13:31 -0000      1.5
+++ amf.xml     4 Mar 2008 21:01:52 -0000       1.5.2.1
@@ -9,7 +9,7 @@
   </para>
   
   <para>
-    Like the RTMP messages, an AMF packet header can be of a variable
+    Like the RTMP messages, an AMF packet header varies in
     size. The size is either the same as the initial header of the
     RTMP message, or a 1 byte header, which is commonly used for
     streaming audio or video data.

Index: cygnal.man-xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/cygnal.man-xml,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -b -r1.1 -r1.1.2.1
--- cygnal.man-xml      19 Feb 2008 02:12:47 -0000      1.1
+++ cygnal.man-xml      4 Mar 2008 21:01:52 -0000       1.1.2.1
@@ -34,7 +34,7 @@
 <para>
   Cygnal is a multimedia media server for streaming audio, video, and
   video conferencing. Cygnal supports several protocols used by SWF
-  file players, including RTMP, RTMPTS, and RTMPT, while encouring the
+  file players, including RTMP, RTMPTS, and RTMPT, while encouraging the
   use of patent free codecs.
 </para>
 

Index: extensions.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/Attic/extensions.xml,v
retrieving revision 1.5
retrieving revision 1.5.2.1
diff -u -b -r1.5 -r1.5.2.1
--- extensions.xml      18 Dec 2007 22:05:14 -0000      1.5
+++ extensions.xml      4 Mar 2008 21:01:53 -0000       1.5.2.1
@@ -61,7 +61,7 @@
       Each new extension should live in it's own directory. The
       extensions included in Gnash are all in the
       <code>gnash/extensions</code> directory. Creating an extension
-      requires a Makefile.am,
+      requires a Makefile.am.
     </para>
 
     <para>
@@ -170,7 +170,7 @@
 
       <para>
        The trick for the above simple constructor to work is that
-        class appartenence is setup in the C++ DummyExt constructor
+        class appurtenance is setup in the C++ DummyExt constructor
         itself, which should derive from as_object and construct the
         base passing it the interface (prototype) of it's class.
       </para>

Index: gnash.man-xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/gnash.man-xml,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -b -r1.1 -r1.1.2.1
--- gnash.man-xml       16 Feb 2008 23:32:22 -0000      1.1
+++ gnash.man-xml       4 Mar 2008 21:01:53 -0000       1.1.2.1
@@ -386,7 +386,7 @@
   </variablelist>
 
 <para>
-  Flash is Trademarked by Adobe Corporation.
+Flash is a registered trademark of Adobe Corporation.
 </para>
 
 </refsect2>

Index: gprocessor.man-xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/gprocessor.man-xml,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -b -r1.1 -r1.1.2.1
--- gprocessor.man-xml  16 Feb 2008 23:32:22 -0000      1.1
+++ gprocessor.man-xml  4 Mar 2008 21:01:53 -0000       1.1.2.1
@@ -90,8 +90,8 @@
     <term>-f [frames]</term>
     <listitem>
       <para>
-       Allow the given number of frame advancements. Keep advancing
-       untill any other stop condition is encountered if set to 0
+       Allow the given number of frame advancements.  If set to 0, keep
+        advancing until any other stop condition is encountered
        (default).
       </para>
     </listitem>
@@ -102,7 +102,7 @@
     <listitem>
       <para>
         Allow the given number of complete runs. Keep looping
-        undefinitely if set to 0. Default is 1 (end as soon as the
+        indefinitely if set to 0. Default is 1 (end as soon as the
         last frame is reached).
       </para>
     </listitem>

Index: rtmp.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/rtmp.xml,v
retrieving revision 1.7
retrieving revision 1.7.2.1
diff -u -b -r1.7 -r1.7.2.1
--- rtmp.xml    20 Feb 2008 11:13:31 -0000      1.7
+++ rtmp.xml    4 Mar 2008 21:01:53 -0000       1.7.2.1
@@ -48,14 +48,14 @@
   <para>
     The client starts the RTMP connection by sending a single byte
     with a value of 0x3. This byte is followed by a data block of 1536
-    bytes. The format if this data block is unknown, but it appears to
+    bytes. The format of this data block is unknown, but it appears to
     not be actually used by the protocol except as a handshake.
   </para>
 
   <para>
     The server receives this packet, stores the 1536 byte data block,
     and then send a single byte with the value of 0x3, followed by two
-    1536 data blocks. The second data block is the full contents of
+    1536 data blocks. The second data block has the full contents of
     the original data block as sent by the client.
   </para>
 
@@ -63,7 +63,7 @@
     The client receives the 1536 byte data block, and if they match,
     the connection is established. After the handshake process is
     done, there are three other messages that the client sends to the
-    sever to start the data flowing.
+    server to start the data flowing.
   </para>
 
   <para>
@@ -108,7 +108,7 @@
     ASCII string as the message body. The following AMF packet is the
     <emphasis>NetConnection</emphasis> one, which specifies that this is coming
     from a Flash application. This also contains the file path the server
-    can use to find the file to stream. This is then followed by the
+    can use to find the file to stream. This is followed by the
     version number, which I assume is the version of the Flash player,
     so the server knows what it is talking to.
   </para>
@@ -363,7 +363,7 @@
        <term>0x6</term>
        <listitem>
          <para>
-           This specifies the data in the AMF packet is a
+           This specifies the data in the AMF packet is
            undefined. This is also used as the return code from
            calling Flash functions.
          </para>
@@ -437,7 +437,7 @@
        <term>0xd</term>
        <listitem>
          <para>
-           This specifies the data in the AMF packet is a an
+           This specifies the data in the AMF packet is an
            unsupported feature.
          </para>
        </listitem>
@@ -457,7 +457,7 @@
        <term>0xf</term>
        <listitem>
          <para>
-           This specifies the data in the AMF packet is a AML
+           This specifies the data in the AMF packet is a XML
            object. XML objects are then parsed by the
            <emphasis>XML</emphasis> ActionScript class.
          </para>