[MANUAL] English:

- erasing ending spaces

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

documentation/manual/en/module_specs/Zend_Service_Twitter.xml

@@ -98,7 +98,7 @@
                 Twitter API (except for public timeline). This must be accomplished using OAuth since
                 Twitter has disabled it's basic HTTP authentication as of August 2010.
             </para>
-            
+
             <para>
                 There are two options to establishing authorization. The first is to implement the
                 workflow of <classname>Zend_Oauth</classname> via <classname>Zend_Service_Twitter</classname>
@@ -130,7 +130,7 @@
  * We assume $serializedToken is the serialized token retrieved from a database
  * or even $_SESSION (if following the simple Zend_Oauth documented example)
  */
-$token = unserialize($serializedToken);            
+$token = unserialize($serializedToken);
 
 $twitter = new Zend_Service_Twitter(array(
     'username' => 'johndoe',
@@ -146,7 +146,7 @@ $response = $twitter->account->verifyCredentials();
             <para>
                 In order to authenticate with Twitter, ALL applications MUST be registered with
                 Twitter in order to receive a Consumer Key and Consumer Secret to be used when
-                authenticating with OAuth. This can not be reused across multiple applications - 
+                authenticating with OAuth. This can not be reused across multiple applications -
                 you must register each new application separately. Twitter access tokens have
                 no expiry date, so storing them to a database is advised (they can, of course,
                 be refreshed simply be repeating the OAuth authorization process). This can only

documentation/manual/en/module_specs/Zend_Uri.xml

@@ -47,9 +47,9 @@ $uri = Zend_Uri::factory('http');
         <para>
             To create a new <acronym>URI</acronym> from scratch, pass only the scheme to
             <methodname>Zend_Uri::factory()</methodname><footnote><para>At the time of writing,
-            <classname>Zend_Uri</classname> only provides built-in support for the <acronym>HTTP</acronym> 
+            <classname>Zend_Uri</classname> only provides built-in support for the <acronym>HTTP</acronym>
             and <acronym>HTTPS</acronym> schemes.</para></footnote>. If an unsupported scheme is
-            passed and no scheme-specific class is specified, a <classname>Zend_Uri_Exception</classname> 
+            passed and no scheme-specific class is specified, a <classname>Zend_Uri_Exception</classname>
             will be thrown.
         </para>
 
@@ -58,41 +58,41 @@ $uri = Zend_Uri::factory('http');
             <methodname>Zend_Uri::factory()</methodname> will return a subclass of itself that
             specializes in the scheme to be created.
         </para>
-        
+
         <sect3>
             <title>Creating a New Custom-Class URI</title>
-            
+
             <para>
-                Starting from Zend Framework 1.10.5, you can specify a custom class to be 
-                used when creating the Zend_Uri instance, as a second parameter to the 
-                <methodname>Zend_Uri::factory()</methodname> method.  
+                Starting from Zend Framework 1.10.5, you can specify a custom class to be
+                used when creating the Zend_Uri instance, as a second parameter to the
+                <methodname>Zend_Uri::factory()</methodname> method.
                 This enables you to subclass Zend_Uri and create your own custom URI classes,
-                and instantiate new URI objects based on your own custom classes. 
+                and instantiate new URI objects based on your own custom classes.
             </para>
-            
+
             <para>
                 The 2nd parameter passed to <methodname>Zend_Uri::factory()</methodname> must
-                be a string with the name of a class extending <classname>Zend_Uri</classname>. 
-                The class must either be alredy-loaded, or loadable using <methodname>Zend_Loader::loadClass()</methodname> - 
-                that is, it must follow the Zend Framework class and file naming conventions, and 
-                must be in your include_path.   
+                be a string with the name of a class extending <classname>Zend_Uri</classname>.
+                The class must either be alredy-loaded, or loadable using <methodname>Zend_Loader::loadClass()</methodname> -
+                that is, it must follow the Zend Framework class and file naming conventions, and
+                must be in your include_path.
             </para>
-            
+
             <example id="zend.uri.creation.custom.example-1">
                 <title>Creating a URI using a custom class</title>
-                
+
                 <programlisting language="php"><![CDATA[
 // Create a new 'ftp' URI based on a custom class
 $ftpUri = Zend_Uri::factory(
-    'ftp://user@ftp.example.com/path/file', 
+    'ftp://user@ftp.example.com/path/file',
     'MyLibrary_Uri_Ftp'
 );
 
-// $ftpUri is an instance of MyLibrary_Uri_Ftp, which is a subclass of Zend_Uri 
+// $ftpUri is an instance of MyLibrary_Uri_Ftp, which is a subclass of Zend_Uri
 ]]></programlisting>
             </example>
         </sect3>
-                
+
     </sect2>
 
     <sect2 id="zend.uri.manipulation">