philip Wed May 9 20:58:00 2007 UTC
Modified files:
/phpdoc/howto cvs.xml generating.xml working.xml
Log:
Fix spelling errors
http://cvs.php.net/viewvc.cgi/phpdoc/howto/cvs.xml?r1=1.16&r2=1.17&diff_format=u
Index: phpdoc/howto/cvs.xml
diff -u phpdoc/howto/cvs.xml:1.16 phpdoc/howto/cvs.xml:1.17
--- phpdoc/howto/cvs.xml:1.16 Wed Jul 20 12:49:39 2005
+++ phpdoc/howto/cvs.xml Wed May 9 20:58:00 2007
@@ -27,7 +27,7 @@
to the file on your local copy. If you are ready, you
need to commit the changes (~upload the new file). The CVS
client asks for your short comment about why this commit
- was neccesary. You can provide a short summary here about what
+ was necessary. You can provide a short summary here about what
was changed. The CVS server stores the history of files with
these commit messages. Everybody can then see what was
modified by you, because all modifications generate a diff
@@ -42,7 +42,7 @@
<para>
This section is not intended to be a CVS tutorial, only a quick
walkthrough to help you get started checking out the
- <literal>phpdoc</literal> and your translation's tree and commiting
+ <literal>phpdoc</literal> and your translation's tree and committing
your changes. The complete CVS documentation can be found
at <ulink url="&url.cvs;">&url.cvs;</ulink>.
</para>
@@ -127,7 +127,7 @@
at cvs.php.net can be found on the same page as the request form,
<ulink url="&url.php.cvsaccount;">&url.php.cvsaccount;</ulink>.
Note that this it not an automated process. If you receive no
- reponse after days, do not hesitate to post a mail to the PHP Group
+ response after days, do not hesitate to post a mail to the PHP Group
and ask for consideration.
</para>
@@ -237,7 +237,7 @@
<para>
Change the <parameter>username</parameter> above to your own
CVS user name. You will be asked to supply your password. Once
- you successfully login to the CVS respository, your encrypted
+ you successfully login to the CVS repository, your encrypted
password is stored in the <filename>.cvspass</filename> file
in your home directory. You won't need to log back into the
same repository again unless you delete that file (or
@@ -253,7 +253,7 @@
<para>
Now it's time to checkout the <parameter>phpdoc</parameter>
- module first. Incidently, a module is a collection of source
+ module first. Incidentally, a module is a collection of source
directories and files. Usually it's simply a directory tree in
the CVS repository.
</para>
@@ -442,7 +442,7 @@
</sect1>
<sect1 id="cvs-commit">
- <title>Commiting Changes</title>
+ <title>Committing Changes</title>
<para>
Once you have made changes to a file and <emphasis>validated
@@ -451,7 +451,7 @@
</para>
<para>
- When commiting a file or files to the repository, it is polite to
+ When committing a file or files to the repository, it is polite to
supply a brief message of what you have changed. You do not need
to document every single line you changed, that is part of CVS'
job. However, it is helpful to see a brief summary of what has
http://cvs.php.net/viewvc.cgi/phpdoc/howto/generating.xml?r1=1.22&r2=1.23&diff_format=u
Index: phpdoc/howto/generating.xml
diff -u phpdoc/howto/generating.xml:1.22 phpdoc/howto/generating.xml:1.23
--- phpdoc/howto/generating.xml:1.22 Wed Apr 18 14:50:17 2007
+++ phpdoc/howto/generating.xml Wed May 9 20:58:00 2007
@@ -320,7 +320,7 @@
information. See the <link linkend="translation-practical">section
for translators</link> about the <filename>build.log.gz</filename>
file. If there were some errors in the build process,
- you can find the errors loged in this file.
+ you can find the errors logged in this file.
</para>
<para>
The automatic build process updates the online manual,
http://cvs.php.net/viewvc.cgi/phpdoc/howto/working.xml?r1=1.63&r2=1.64&diff_format=u
Index: phpdoc/howto/working.xml
diff -u phpdoc/howto/working.xml:1.63 phpdoc/howto/working.xml:1.64
--- phpdoc/howto/working.xml:1.63 Wed Apr 18 14:50:18 2007
+++ phpdoc/howto/working.xml Wed May 9 20:58:00 2007
@@ -206,7 +206,7 @@
<simpara>
If there is something dangerous to document such as the
<function>chroot</function>, or when something can be seen as a
- weirdness in the language such as weird autoconversion of types, use the
+ weirdness in the language such as weird auto-conversion of types, use the
<caution> element.
</simpara>
<simpara>
@@ -494,7 +494,7 @@
<title>A function skeleton (<filename>func-name.xml</filename>)</title>
<programlisting role="xml">
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.63 $ -->
+<!-- $Revision: 1.64 $ -->
<refentry id="function.func-name">
<refnamediv>
<refname>func_name</refname>
@@ -673,7 +673,7 @@
<title>A <filename>reference.xml</filename> skeleton</title>
<programlisting role="xml">
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.63 $ -->
+<!-- $Revision: 1.64 $ -->
<!-- Purpose: xx -->
<!-- Membership: xx -->
<!-- State: xx -->
@@ -743,7 +743,7 @@
<title>A <filename>configure.xml</filename> skeleton</title>
<programlisting role="xml">
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.63 $ -->
+<!-- $Revision: 1.64 $ -->
<section id="extname.installation">
&reftitle.install;
<para>
@@ -784,7 +784,7 @@
<title>A <filename>constants.xml</filename> skeleton</title>
<programlisting role="xml">
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.63 $ -->
+<!-- $Revision: 1.64 $ -->
<section id="extname.constants">
&reftitle.constants;
&extension.constants;
@@ -834,7 +834,7 @@
<title>A <filename>ini.xml</filename> skeleton</title>
<programlisting role="xml">
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.63 $ -->
+<!-- $Revision: 1.64 $ -->
<section id="extname.configuration">
&reftitle.runtime;
&extension.runtime;
@@ -1212,7 +1212,7 @@
<para>
This system is hard to maintain with the current
<filename>phpdoc</filename>
layout, as tracking the revisions of more then 4000 files in one text
file
- can be very hard. Consider using the revison comment method described
below,
+ can be very hard. Consider using the revision comment method described
below,
where you only need to work on one file if you make updates in your
language.
</para>
</note>
