sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-15 16:38:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix typos and small grammatical thingies.

Browse source 
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@191762 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Dan Scott 2005-07-28 19:45:25 +00:00
parent 7a48c96b55
commit 04ef7baafc
1 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
reference/sdo/reference.xml
View file

@ -1,5 +1,5 @@
<?xml version='1.0' encoding='iso-8859-1'?>
<!-- $Revision: 1.9 $ -->
<!-- $Revision: 1.10 $ -->
<!-- Generated by xml_proto.php v2.1. Found in /scripts directory of phpdoc. -->
<reference id="ref.sdo">
<title>SDO Functions</title>
@ -78,7 +78,7 @@
can do so by following steps described below.
</para>
<procedure id='sdo.installation.linux.steps'>
<title>Linux intallation steps</title>
<title>Linux installation steps</title>
<para>
The following instructions describe how to install the
SDO extension on Linux. Note, these steps will also install the
@ -874,8 +874,8 @@ sdoxml:propertyType="company:EmployeeType"/> </xsd:complexType>
from the sequence (Note: <function>unset</function> currently
leaves the values in the data object, but this behaviour is
likely to change to also remove the data from the data object).
Sequence behaves like a contiguous list and therefore removing
from the middle results in entries at higher indices being shifted
A sequence behaves like a contiguous list; therefore, removing
items from the middle will shift entries at higher indices
down. The following example tests to see if the first sequence
element is set and unsets it if is.
</para>
@ -897,7 +897,7 @@ sdoxml:propertyType="company:EmployeeType"/> </xsd:complexType>
<section id='sdo.classes'>
&reftitle.classes;
<para>
SDO consists of two set of interfaces. The first set covers those
SDO consists of two sets of interfaces. The first set covers those
interfaces for use by SDO client applications. These are identified by
the package prefix 'SDO_'. The second set is those for use by Data
Access Service implementations and are identified by the package prefix
@ -930,7 +930,7 @@ sdoxml:propertyType="company:EmployeeType"/> </xsd:complexType>
<listitem>
<para>
<link linkend='function.SDO-DataObject-getSequence'>
getSequnece
getSequence
</link> - get the sequence for the data object
</para>
</listitem>
@ -972,11 +972,11 @@ sdoxml:propertyType="company:EmployeeType"/> </xsd:complexType>
<classname>SDO_Sequence</classname>
</title>
<para>
The interface through which sequenced data objects can be accessed in
order to preserve ordering across a data object's properties and
The interface through which sequenced data objects can be accessed
to preserve ordering across a data object's properties and
to allow unstructured text.
SDO_Sequence preserves contiguous indices and therefore inserting
or removing elements may results in other elements shifted up or
or removing elements may shift other elements up or
down. In addition to the methods below, SDO_Sequence extends the
ArrayAccess, Iterator and Countable interface.
</para>
@ -1022,9 +1022,9 @@ sdoxml:propertyType="company:EmployeeType"/> </xsd:complexType>
<para>
The interface through which many-valued properties are manipulated.
In addition to the method defined below, SDO_List extends ArrayAccess,
Iterator and Coutable. SDO_List preserves contiguous indices and
therefore inserting or removing elements may results in other elements
shifted up or down.
Iterator and Countable. SDO_List preserves contiguous indices and
therefore inserting or removing elements may shift other elements
up or down.
</para>
<section id='sdo.class.SDO-List.methods'>
&reftitle.methods;
@ -1111,7 +1111,7 @@ sdoxml:propertyType="company:EmployeeType"/> </xsd:complexType>
</para>
<para>
If logging is no longer active
then the change summary only hold changes made up to the point when
then the change summary only holds changes made up to the point when
logging was deactivated.
Reactivating logging clears the change summary.
This is useful when a set of changes have been written out by a