dave            Thu Sep 25 18:44:30 2003 EDT

  Modified files:              
    /phpdoc/en/appendices       about.xml 
  Log:
  - Various typos.
  
  
Index: phpdoc/en/appendices/about.xml
diff -u phpdoc/en/appendices/about.xml:1.26 phpdoc/en/appendices/about.xml:1.27
--- phpdoc/en/appendices/about.xml:1.26 Sun Jun 22 11:27:57 2003
+++ phpdoc/en/appendices/about.xml      Thu Sep 25 18:44:30 2003
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.26 $ -->
+<!-- $Revision: 1.27 $ -->
 
 <!--
   TODO: add manual conventions section (eg. how to read
@@ -134,7 +134,7 @@
      Prerequisite: Basic understanding of <link linkend="language.types">types</link>
     </title>
     <para>
-     Although PHP is a loosly typed language, it's important to have 
+     Although PHP is a loosely typed language, it's important to have 
      a basic understanding of <link linkend="language.types">types</link> as 
      they have important meaning.
     </para>
@@ -218,7 +218,7 @@
     </para>
     <para>
      Many functions take on multiple parameters, such as 
<function>in_array</function>.
-     It's prototype is as follows:
+     Its prototype is as follows:
     </para>
     <para>
      <screen role="html">    
@@ -377,25 +377,25 @@
   <para>
    The PHP manual is not only available in various formats,
    it is also available in various languages. The text of the 
-   manual is first written in english, then teams of people across 
+   manual is first written in English, then teams of people across 
    the world take care of translating it to their native language.
    If a translation for a specified function or chapter has not yet
    been made, the build system of the manual falls back to the 
-   english version of it.
+   English version of it.
   </para>
   <para>
-   Peoples involved in the translations start from the <acronym>XML</acronym>
+   People involved in the translations start from the <acronym>XML</acronym>
    source code available from <ulink url="&url.php.cvs;">&url.php.cvs;</ulink>
-   and from it they translate to thier mother language. They do 
+   and from it they translate to their mother language. They do 
    <emphasis>not use</emphasis> the <acronym>HTML</acronym>, the plain text, 
    or the <acronym>PDF</acronym> version. It is the build system which takes 
    care of the conversions from <acronym>XML</acronym> to human readable formats.
   </para>
   <note>
    <para>
-    If you would like to help translating the documentation to your native 
-    language, please get in touch with the translation/documentation team
-    subscribing to the phpdoc mailinglist: send an empty mail to <ulink
+    If you would like to help translate the documentation to your native 
+    language, please get in touch with the translation/documentation team by
+    subscribing to the phpdoc mailing list: send an empty mail to <ulink
     url="mailto:&email.php.doc.subscribe;";>&email.php.doc.subscribe;</ulink>.
     The mailing list address is <literal>&email.php.doc;</literal>. State in the
     message that you are interested in translating the manual to a language 
@@ -411,7 +411,7 @@
    Turkish.
   </para>
   <para>
-   They all can be downloaded here: <ulink 
url="&url.php.docs;">&url.php.docs;</ulink>.
+   They can all be downloaded here: <ulink 
url="&url.php.docs;">&url.php.docs;</ulink>.
   </para>
  </sect1>
 

Reply via email to