[DOCUMENTATION] English:

 - manual fixes: <acronym>HTTP</acronym>S => <acronym>HTTPS</acronym>

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

documentation/manual/en/module_specs/Zend_Http_Client-Adapters.xml

@@ -134,7 +134,7 @@
                 <title>HTTPS SSL Stream Parameters</title>
                 <para>
                     <code>ssltransport, sslcert</code> and <code>sslpassphrase</code>
-                    are only relevant when connecting using <acronym>HTTP</acronym>S.
+                    are only relevant when connecting using <acronym>HTTPS</acronym>.
                 </para>
                 <para>
                     While the default <acronym>SSL</acronym> settings should work for most
@@ -176,7 +176,7 @@ $response = $client->request();
                 provides direct access to the underlying <ulink url="http://php.net/manual/en/stream.contexts.php">stream context</ulink>
                 used to connect to the remote server. This allows the user to pass
                 specific options and parameters to the <acronym>TCP</acronym> stream, and to the <acronym>SSL</acronym> wrapper in
-                case of <acronym>HTTP</acronym>S connections.
+                case of <acronym>HTTPS</acronym> connections.
             </para>
 
             <para>

documentation/manual/en/module_specs/Zend_Http_Cookie-Handling.xml

@@ -180,7 +180,7 @@ echo $cookie;
                 <listitem>
                     <para>
                     <code>boolean isSecure()</code>: Check whether the cookie is set to be sent over secure
-                    connections only. Generally speaking, if true the cookie should only be sent over <acronym>HTTP</acronym>S.
+                    connections only. Generally speaking, if true the cookie should only be sent over <acronym>HTTPS</acronym>.
                     </para>
                 </listitem>
                 <listitem>
@@ -244,7 +244,7 @@ echo ($cookie->isSessionCookie() ? 'Yes' : 'No');
                     <para>
                     <code>mixed $uri</code>: A <classname>Zend_Uri_Http</classname> object with a domain name and path to be checked.
                     Optionally, a string representing a valid <acronym>HTTP</acronym> <acronym>URL</acronym> can be passed instead. The cookie will
-                    match if the <acronym>URL</acronym>'s scheme (HTTP or <acronym>HTTP</acronym>S), domain and path all match.
+                    match if the <acronym>URL</acronym>'s scheme (HTTP or <acronym>HTTPS</acronym>), domain and path all match.
                     </para>
                 </listitem>
                 <listitem>

documentation/manual/en/module_specs/Zend_Soap_Client.xml

@@ -113,7 +113,7 @@
                 </listitem>
                 <listitem>
                     <para>
-                        'local_cert' and 'passphrase' - <acronym>HTTP</acronym>S client certificate authentication options.
+                        'local_cert' and 'passphrase' - <acronym>HTTPS</acronym> client certificate authentication options.
                     </para>
                 </listitem>
                 <listitem>

documentation/manual/en/module_specs/Zend_Uri.xml

@@ -21,7 +21,7 @@
       itself which specializes in each scheme. The subclass
       will be named <classname>Zend_Uri_&lt;scheme&gt;</classname>, where
       <code>&lt;scheme&gt;</code> is the scheme lowercased with the first
-      letter capitalized. An exception to this rule is <acronym>HTTP</acronym>S, which is also
+      letter capitalized. An exception to this rule is <acronym>HTTPS</acronym>, which is also
       handled by <classname>Zend_Uri_Http</classname>.
     </para>
   </sect2>
@@ -48,7 +48,7 @@ $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 supports the <acronym>HTTP</acronym> and <acronym>HTTP</acronym>S schemes.</para></footnote> .
+      <classname>Zend_Uri</classname> only supports the <acronym>HTTP</acronym> and <acronym>HTTPS</acronym> schemes.</para></footnote> .
       If an unsupported scheme is passed, a <classname>Zend_Uri_Exception</classname>
       will be thrown.
     </para>