[DOCUMENTATION] English:

 - erased multiples whitespaces inside text

git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@17170 44c647ce-9c0f-0410-b52a-842ac1e357ba

documentation/manual/en/module_specs/Zend_Db_Table.xml

@@ -28,9 +28,9 @@
         <title>Using Zend_Db_Table as a concrete class</title>
 
         <para>
-            As of ZF 1.9, you can instantiate Zend_Db_Table.  This added benefit is that
+            As of ZF 1.9, you can instantiate Zend_Db_Table. This added benefit is that
             you do not have to extend a base class and configure it to do simple operations
-            such as selecting, inserting, updating and deleteing on a single table.  Below
+            such as selecting, inserting, updating and deleteing on a single table. Below
             is an example of the simplest of use cases.
         </para>
 
@@ -46,8 +46,8 @@ $bugTable = new Zend_Db_Table('bug');
         </example>
 
         <para>
-            The above example represents the simplest of use cases.  Make not of all the
-            options describe below for configuring Zend_Db_Table tables.  If you want to be
+            The above example represents the simplest of use cases. Make not of all the
+            options describe below for configuring Zend_Db_Table tables. If you want to be
             able to use the concrete usage case, in addition to the more complex relationhip
             features, see the Zend_Db_Table_Definition documentation.
         </para>

documentation/manual/en/module_specs/Zend_Db_Table_Definition.xml

@@ -23,14 +23,14 @@
         <para>
             For all of the same options that are available when configuring an extended
             Zend_Db_Table_Abstract class, those options are also available when describing
-            a definition file.  This definition file should be passed to the class at
+            a definition file. This definition file should be passed to the class at
             instantiation time so that it can know the full definition of all tables
             in said definition.
         </para>
 
         <para>
             Below is a definition that will describe the table names and relationships
-            between table objects.  Note: if 'name' is left out of the definition, it
+            between table objects. Note: if 'name' is left out of the definition, it
             will be taken as the key of the defined table (an example of this is in the
             'genre' section in the example below.)
         </para>
@@ -78,7 +78,7 @@ $definition = new Zend_Db_Table_Definition(array(
         <para>
             As you can see, the same options you'd generally see inside of an
             extended Zend_Db_Table_Abstract class are documented in this
-            array as well.  When passed into Zend_Db_Table constructor, this
+            array as well. When passed into Zend_Db_Table constructor, this
             definition is <emphasis>persisted</emphasis> to any tables it will need
             to create in order to return the proper rows.
         </para>
@@ -127,8 +127,8 @@ foreach ($authors as $author) {
 
         <para>
             Sometimes you want to use both paradigms for defining and using the
-            table gateway: both by extension and concrete instantiation.  To do this
-            simply leave out any table configurations out of the definition.  This will
+            table gateway: both by extension and concrete instantiation. To do this
+            simply leave out any table configurations out of the definition. This will
             allow Zend_Db_Table to look for the actual refered class instead of the
             definition key.
         </para>
@@ -136,7 +136,7 @@ foreach ($authors as $author) {
         <para>
             Building on the example above, we will allow for one of the table configurations
             to be a Zend_Db_Table_Abstract extended class, while keeping the rest of the tables
-            as part of the definition.  We will also show how one would interact with this
+            as part of the definition. We will also show how one would interact with this
             new definition.
         </para>
 

documentation/manual/en/module_specs/Zend_Service_Amazon_Sqs.xml

@@ -137,7 +137,7 @@ foreach ($sqs->receive($queue_url) as $message) {
         <para>
             Since the <classname>Zend_Service_Amazon_Sqs</classname> service
             requires authentication, you should pass your credentials (AWS key
-            and secret key) to the constructor.  If you only use one account,
+            and secret key) to the constructor. If you only use one account,
             you can set default credentials for the service:
         </para>
 
@@ -158,7 +158,7 @@ $sqs = new Zend_Service_Amazon_Sqs();
 
         <para>
             Queue names can contain lowercase letters, digits, periods (.),
-            underscores (_), and dashes (-).  No other symbols allowed. Queue
+            underscores (_), and dashes (-). No other symbols allowed. Queue
             names can be a maximum of 80 characters.
         </para>
 
@@ -231,7 +231,7 @@ foreach($list as $queue) {
         <para>
             After a queue is created, simple messages can be sent into the queue
             then received at a later point in time. Messages can be up to 8KB in
-            length.  If longer messages are needed please see <ulink
+            length. If longer messages are needed please see <ulink
                 url="http://framework.zend.com/manual/en/zend.service.amazon.s3.html">S3</ulink>.
             There is no limit to the number of messages a queue can contain.
         </para>
@@ -278,7 +278,7 @@ foreach ($sqs->receive($queue_url) as $message) {
             <listitem>
                 <para>
                     <methodname>deleteMessage($queue_url, $handle)</methodname>
-                    deletes a message from a queue.  A message must first be
+                    deletes a message from a queue. A message must first be
                     received using the <methodname>receive()</methodname> method
                     before it can be deleted.
                 </para>

documentation/manual/en/module_specs/Zend_Test-PHPUnit-Db-Quickstart.xml

@@ -109,7 +109,7 @@ class BugsTest extends Zend_Test_PHPUnit_DatabaseTestCase
 
         <para>
             In the previous setup for the database testcase we have specified a seed file for the
-            database fixture.  We now create this file specified in the Flat XML format:
+            database fixture. We now create this file specified in the Flat XML format:
         </para>
 
         <programlisting language="xml"><![CDATA[
@@ -197,9 +197,9 @@ class BugsTest extends Zend_Test_PHPUnit_DatabaseTestCase
 
         <para>
             Now up to the <methodname>$bugsTable->insert($data);</methodname> everything looks
-            familiar.  The lines after that contain the assertion methodname. We want to verify
+            familiar. The lines after that contain the assertion methodname. We want to verify
             that after inserting the new bug the database has been updated correctly with the
-            given data.  For this we create a
+            given data. For this we create a
             <classname>Zend_Test_PHPUnit_Db_DataSet_QueryDataSet</classname> instance and give
             it a database connection. We will then tell this dataset that it contains a table
             "zfbugs" which is given by an SQL statement. This current/actual state of the
@@ -220,7 +220,7 @@ class BugsTest extends Zend_Test_PHPUnit_DatabaseTestCase
 
         <para>
             There are other ways to assert that the current database state equals an expected
-            state.  The "Bugs" table in the example already nows a lot about its inner state, so
+            state. The "Bugs" table in the example already nows a lot about its inner state, so
             why not use this to our advantage? The next example will assert that deleting from
             the database is possible:
         </para>
@@ -305,7 +305,7 @@ class BugsTest extends Zend_Test_PHPUnit_DatabaseTestCase
             Here we create the current database state from a
             <classname>Zend_Db_Table_Rowset_Abstract</classname> instance in conjunction with
             the <methodname>Zend_Test_PHPUnit_Db_DataSet_DbRowset($rowset)</methodname> instance
-            which creates an internal data-representation of the rowset.  This can again be
+            which creates an internal data-representation of the rowset. This can again be
             compared against another data-table by using the
             <methodname>$this->assertTablesEqual()</methodname> assertion.
         </para>

documentation/manual/en/module_specs/Zend_Test-PHPUnit-Db-Testing.xml

@@ -128,7 +128,7 @@
 
                         <entry>
                             Create a PHPUnit Database Extension compatible Connection instance from
-                            a <classname>Zend_Db_Adapter_Abstract</classname> instance.  This method
+                            a <classname>Zend_Db_Adapter_Abstract</classname> instance. This method
                             should be used in for testcase setup when implementing the abstract
                             <methodname>getConnection()</methodname> method of the database testcase.
                         </entry>

documentation/manual/en/module_specs/Zend_Test-PHPUnit-Db.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!-- Reviewed: no -->
-<sect1 id="zend.test.phpunit.db"  xmlns:xi="http://www.w3.org/2001/XInclude">
+<sect1 id="zend.test.phpunit.db" xmlns:xi="http://www.w3.org/2001/XInclude">
     <title>Zend_Test_PHPUnit_Db</title>
 
     <para>

documentation/manual/en/module_specs/Zend_Validate-Db.xml

@@ -152,14 +152,14 @@ if ($validator->isValid($username)) {
 $validator = new Zend_Validate_Db_RecordExists('users', 'id', null, $dbAdapter);
 ]]></programlisting>
     </sect3>
-    
+
     <sect3 id="zend.validate.db.database-schemas">
         <title>Database Schemas</title>
 
         <para>
             You can specify a schema within your database for adapters such as
-            PostgreSQL and DB/2 by simply supplying an array with 
-            <code>table</code> and <code>schema</code> keys. As in the example 
+            PostgreSQL and DB/2 by simply supplying an array with
+            <code>table</code> and <code>schema</code> keys. As in the example
             below:
         </para>