[MANUAL] English:

- unified "API" with acronym

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

documentation/manual/en/module_specs/Zend_Feed_Pubsubhubbub.xml

@@ -89,7 +89,7 @@
             <classname>Zend_Feed_Pubsubhubbub_Subscriber</classname>. In addition, the Subscriber
             implementation may handle any feed updates forwarded from a Hub by using
             <classname>Zend_Feed_Pubsubhubbub_Subscriber_Callback</classname>. These classes, their
-            use cases, and APIs are covered in subsequent sections.
+            use cases, and <acronym>API</acronym>s are covered in subsequent sections.
         </para>
     </sect2>
 
@@ -99,12 +99,12 @@
         <para>
             In Pubsubhubbub, the Publisher is the party who publishes a live feed and frequently
             updates it with new content. This may be a blog, an aggregator, or even a web service
-            with a public feed based API. In order for these updates to be pushed to Subscribers,
-            the Publisher must notify all of its supported Hubs that an update has occured using a
-            simple HTTP POST request containing the URI or the updated Topic (i.e the updated RSS or
-            Atom feed). The Hub will confirm receipt of the notification, fetch the updated feed,
-            and forward any updates to any Subscribers who have subscribed to that Hub for updates
-            from the relevant feed.
+            with a public feed based <acronym>API</acronym>. In order for these updates to be pushed
+            to Subscribers, the Publisher must notify all of its supported Hubs that an update has
+            occured using a simple HTTP POST request containing the URI or the updated Topic (i.e
+            the updated RSS or Atom feed). The Hub will confirm receipt of the notification, fetch
+            the updated feed, and forward any updates to any Subscribers who have subscribed to that
+            Hub for updates from the relevant feed.
         </para>
 
         <para>

documentation/manual/en/module_specs/Zend_Feed_Writer.xml

@@ -256,9 +256,9 @@ $out = $feed->export('atom');
         </para>
 
         <para>
-            The Feed Level API for data is contained in
-            <classname>Zend_Feed_Writer_Feed</classname>. In addition to the API detailed below, the
-            class also implements the <classname>Countable</classname> and
+            The Feed Level <acronym>API</acronym> for data is contained in
+            <classname>Zend_Feed_Writer_Feed</classname>. In addition to the <acronym>API</acronym>
+            detailed below, the class also implements the <classname>Countable</classname> and
             <classname>Iterator</classname> interfaces.
         </para>
 
@@ -489,7 +489,7 @@ $out = $feed->export('atom');
         </para>
 
         <para>
-            The Entry Level API for data is contained in
+            The Entry Level <acronym>API</acronym> for data is contained in
             <classname>Zend_Feed_Writer_Entry</classname>.
         </para>
 

documentation/manual/en/module_specs/Zend_Log-Writers-ZendMonitor.xml

@@ -5,16 +5,18 @@
 
     <para>
         <classname>Zend_Log_Writer_ZendMonitor</classname> allows you to log events via Zend
-        Server's Monitor API. This allows you to aggregate log messages for your entire application
-        environment in a single location. Internally, it simply uses the
-        <methodname>monitor_custom_event()</methodname> function from the Zend Monitor API.
+        Server's Monitor <acronym>API</acronym>. This allows you to aggregate log messages for your
+        entire application environment in a single location. Internally, it simply uses the
+        <methodname>monitor_custom_event()</methodname> function from the Zend Monitor
+        <acronym>API</acronym>.
     </para>
 
     <para>
-        One particularly useful feature of the Monitor API is that it allows you to specify
-        arbitrary custom information alongside the log message. For instance, if you wish to log an
-        exception, you can log not just the exception message, but pass the entire exception object
-        to the function, and then inspect the object within the Zend Server event monitor.
+        One particularly useful feature of the Monitor <acronym>API</acronym> is that it allows you
+        to specify arbitrary custom information alongside the log message. For instance, if you wish
+        to log an exception, you can log not just the exception message, but pass the entire
+        exception object to the function, and then inspect the object within the Zend Server event
+        monitor.
     </para>
 
     <note>
@@ -113,8 +115,9 @@ $log->info('Exception occurred', array(
         </para>
 
         <para>
-            As noted previously, if the Monitor API is not detected in your <acronym>PHP</acronym>
-            installation, the logger will simply act as a <constant>NULL</constant> logger.
+            As noted previously, if the Monitor <acronym>API</acronym> is not detected in your
+            <acronym>PHP</acronym> installation, the logger will simply act as a
+            <constant>NULL</constant> logger.
         </para>
     </note>
 </sect2>

documentation/manual/en/module_specs/Zend_Oauth-GettingStarted.xml

@@ -8,7 +8,7 @@
         source code. Our new Consumer will be handling Twitter Status submissions.
         To do so, it will need to be registered with Twitter in order to receive
         an OAuth Consumer Key and Consumer Secret. This are utilised to obtain
-        an Access Token before we use the Twitter API to post a status message.
+        an Access Token before we use the Twitter <acronym>API</acronym> to post a status message.
     </para>
 
     <para>
@@ -31,8 +31,8 @@ $consumer = new Zend_Oauth_Consumer($config);
     <para>
         The callbackUrl is the URI we want Twitter to request from our server
         when sending information. We'll look at this later. The siteUrl is the
-        base URI of Twitter's OAuth API endpoints. The full list of endpoints include
-        http://twitter.com/oauth/request_token, http://twitter.com/oauth/access_token,
+        base URI of Twitter's OAuth <acronym>API</acronym> endpoints. The full list of endpoints
+        include http://twitter.com/oauth/request_token, http://twitter.com/oauth/access_token,
         and http://twitter.com/oauth/authorize. The base siteUrl utilises a convention
         which maps to these three OAuth endpoints (as standard) for requesting a
         request token, access token or authorization. If the actual endpoints of
@@ -102,8 +102,8 @@ $token = $consumer->getRequestToken();
     <para>
         The new request token (an instance of <classname>Zend_Oauth_Token_Request
         </classname>) is unauthorized. In order to exchange it for an authorized
-        token with which we can access the Twitter API, we need the user to authorize
-        it. We accomplish this by redirecting the user to Twitter's authorize endpoint
+        token with which we can access the Twitter <acronym>API</acronym>, we need the user to
+        authorize it. We accomplish this by redirecting the user to Twitter's authorize endpoint
         via:
     </para>
 
@@ -146,7 +146,7 @@ $consumer->redirect();
         can include code to parse out this access token as follows - this source
         code would exist within the executed code of our callback URI. Once parsed
         we can discard the previous request token, and instead persist the access
-        token for future use with the Twitter API. Again, we're simply persisting
+        token for future use with the Twitter <acronym>API</acronym>. Again, we're simply persisting
         to the user session, but in reality an access token can have a long lifetime
         so it should really be stored to a database.
     </para>
@@ -174,8 +174,8 @@ if (!empty($_GET) && isset($_SESSION['TWITTER_REQUEST_TOKEN'])) {
 
     <para>
         Success! We have an authorized access token - so it's time to actually
-        use the Twitter API. Since the access token must be included with every
-        single API request, Zend_Oauth_Consumer offers a ready-to-go HTTP client
+        use the Twitter <acronym>API</acronym>. Since the access token must be included with every
+        single <acronym>API</acronym> request, Zend_Oauth_Consumer offers a ready-to-go HTTP client
         (a subclass of <classname>Zend_Http_Client</classname>) to use either
         by itself or by passing it as a custom HTTP Client to another library or
         component. Here's an example of using it standalone. This can be done

documentation/manual/en/module_specs/Zend_Oauth-Introduction.xml

@@ -20,18 +20,18 @@
         will be in receipt of an Access Token associated with your account. Using this Access Token,
         the application can access your private data without continually requiring your credentials.
         In all this authorization delegation style of protocol is simply a more secure solution to
-        the problem of accessing private data via any web service API.
+        the problem of accessing private data via any web service <acronym>API</acronym>.
     </para>
 
     <para>
         OAuth is not a completely new idea, rather it is a standardized protocol building on the
-        existing properties of protocols such as Google AuthSub, Yahoo BBAuth, Flickr API, etc.
-        These all to some extent operate on the basis of exchanging user credentials for an Access
-        Token of some description. The power of a standardized specification like OAuth is that it
-        only requires a single implementation as opposed to many disparate ones depending on the web
-        service. This standardization has not occurred independently of the major players, and
-        indeed many now support OAuth as an alternative and future replacement for their own
-        solutions.
+        existing properties of protocols such as Google AuthSub, Yahoo BBAuth, Flickr
+        <acronym>API</acronym>, etc. These all to some extent operate on the basis of exchanging
+        user credentials for an Access Token of some description. The power of a standardized
+        specification like OAuth is that it only requires a single implementation as opposed to many
+        disparate ones depending on the web service. This standardization has not occurred
+        independently of the major players, and indeed many now support OAuth as an alternative and
+        future replacement for their own solutions.
     </para>
 
     <para>

documentation/manual/en/module_specs/Zend_Oauth-ProtocolWorkflow.xml

@@ -38,14 +38,14 @@
 
     <para>
         At this point the User may be asked to log into Twitter and will now be faced with a Twitter
-        screen asking if they approve this request by TweetExpress to access Twitter's API on the
-        User's behalf. Twitter will record the response which we'll assume was positive. Based on
-        the User's approval, Twitter will record the current unauthorized Request Token as having
-        been approved by the User (thus making it User specific) and will generate a new value in
-        the form of a verification code. The User is now redirected back to a specific callback URL
-        used by TweetExpress (this callback URL may be registered with Twitter or dynamically set
-        using an oauth_callback parameter in requests). The redirect URL will contain the newly
-        generated verification code.
+        screen asking if they approve this request by TweetExpress to access Twitter's
+        <acronym>API</acronym> on the User's behalf. Twitter will record the response which we'll
+        assume was positive. Based on the User's approval, Twitter will record the current
+        unauthorized Request Token as having been approved by the User (thus making it User
+        specific) and will generate a new value in the form of a verification code. The User is now
+        redirected back to a specific callback URL used by TweetExpress (this callback URL may be
+        registered with Twitter or dynamically set using an oauth_callback parameter in requests).
+        The redirect URL will contain the newly generated verification code.
     </para>
 
     <para>
@@ -54,17 +54,17 @@
         unauthorized Request Token for a fully authorized Access Token by sending a request back to
         Twitter including the Request Token and the received verification code. Twitter should now
         send back a response containing this Access Token which must be used in all requests used to
-        access Twitter's API on behalf of the User. Twitter will only do this once they have
-        confirmed the attached Request Token has not already been used to retrieve another Access
-        Token. At this point, TweetExpress may confirm the receipt of the approval to the User and
-        delete the original Request Token which is no longer needed.
+        access Twitter's <acronym>API</acronym> on behalf of the User. Twitter will only do this
+        once they have confirmed the attached Request Token has not already been used to retrieve
+        another Access Token. At this point, TweetExpress may confirm the receipt of the approval to
+        the User and delete the original Request Token which is no longer needed.
     </para>
 
     <para>
-        From this point forward, TweetExpress may use Twitter's API to post new tweets on the User's
-        behalf simply by accessing the API endpoints with a request that has been digitally signed
-        (via HMAC-SHA1) with a combination of TweetExpress' Consumer Secret and the Access Key being
-        used.
+        From this point forward, TweetExpress may use Twitter's <acronym>API</acronym> to post new
+        tweets on the User's behalf simply by accessing the <acronym>API</acronym> endpoints with a
+        request that has been digitally signed (via HMAC-SHA1) with a combination of TweetExpress'
+        Consumer Secret and the Access Key being used.
     </para>
 
     <para>

documentation/manual/en/module_specs/Zend_Pdf-InteractiveFeatures.xml

@@ -805,9 +805,9 @@ $pdf->resolveDestination(Zend_Pdf_Destination_Named::create('Page3'));
 
             <para>
                 <methodname>Zend_Pdf_Action_URI::create($uri[, $isMap])</methodname> method has
-                to be used to create a URI action (see API documentation for the details).
-                Optional <varname>$isMap</varname> parameter is set to <constant>FALSE</constant>
-                by default.
+                to be used to create a URI action (see <acronym>API</acronym> documentation for the
+                details). Optional <varname>$isMap</varname> parameter is set to
+                <constant>FALSE</constant> by default.
             </para>
 
             <para>

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

@@ -498,8 +498,8 @@ $queue = new Zend_Queue('Db', $options);
                 <listitem>
                     <para>
                         <methodname>getQueues()</methodname> - Zend Platform does not allow
-                        introspection into the attached job handling scripts via the API. This
-                        method throws an exception.
+                        introspection into the attached job handling scripts via the
+                        <acronym>API</acronym>. This method throws an exception.
                     </para>
                 </listitem>
 

documentation/manual/en/module_specs/Zend_Search_Lucene-Queries.xml

@@ -9,8 +9,8 @@
     </para>
 
     <para>
-        User queries can be combined with queries created through the query API. Simply use the
-        query parser to construct a query from a string:
+        User queries can be combined with queries created through the query <acronym>API</acronym>.
+        Simply use the query parser to construct a query from a string:
 
         <programlisting language="php"><![CDATA[
 $query = Zend_Search_Lucene_Search_QueryParser::parse($queryString);
@@ -376,7 +376,7 @@ $hits  = $index->find($query);
 
         <para>
             Each query which uses boolean operators can be rewritten using signs notation and
-            constructed using API. For example:
+            constructed using <acronym>API</acronym>. For example:
 
             <programlisting language="querystring"><![CDATA[
 word1 AND (word2 AND word3 AND NOT word4) OR word5
@@ -415,7 +415,7 @@ field1:test*
         <para>or</para>
 
         <para>
-            Query construction by API:
+            Query construction by <acronym>API</acronym>:
 
             <programlisting language="php"><![CDATA[
 $pattern = new Zend_Search_Lucene_Index_Term('test*', 'field1');
@@ -457,7 +457,7 @@ field1:test~
         <para>or</para>
 
         <para>
-            Query construction by API:
+            Query construction by <acronym>API</acronym>:
 
             <programlisting language="php"><![CDATA[
 $term = new Zend_Search_Lucene_Index_Term('test', 'field1');
@@ -481,7 +481,7 @@ field1:test~0.4
         <para>or</para>
 
         <para>
-            Query construction by API:
+            Query construction by <acronym>API</acronym>:
 
             <programlisting language="php"><![CDATA[
 $term = new Zend_Search_Lucene_Index_Term('test', 'field1');
@@ -732,7 +732,7 @@ title:{Aida TO Carmen}
         <para>or</para>
 
         <para>
-            Query construction by API:
+            Query construction by <acronym>API</acronym>:
 
             <programlisting language="php"><![CDATA[
 $from = new Zend_Search_Lucene_Index_Term('20020101', 'mod_date');

documentation/manual/en/module_specs/Zend_Service-ReCaptcha.xml

@@ -113,7 +113,7 @@ if (!$result->isValid()) {
         <para>
             In order to use this component you will need
             <ulink url="http://recaptcha.net/whyrecaptcha.html">an account</ulink> to generate
-            public and private keys for the mailhide API.
+            public and private keys for the mailhide <acronym>API</acronym>.
         </para>
 
         <example id="zend.service.recaptcha.mailhide.example-1">

documentation/manual/en/module_specs/Zend_Service_DeveloperGarden.xml

@@ -10,7 +10,7 @@
             Developer Garden is the name of Deutsche Telekom’s developer community.
             Developer Garden offers you  access to core services of Deutsche Telekom,
             such as voice connections (Voice Call) or sending text messages (Send SMS)
-            via open interfaces (Open APIs). You can access the Developer Garden
+            via open interfaces (Open <acronym>API</acronym>s). You can access the Developer Garden
             services directly via <acronym>SOAP</acronym> or <acronym>REST</acronym>.
         </para>
 
@@ -26,7 +26,7 @@
                 <para>
                     <link
                         linkend="zend.service.developergarden.baseuserservice">BaseUserService</link>:
-                    Class to manage API quota and user accounting details.
+                    Class to manage <acronym>API</acronym> quota and user accounting details.
                 </para>
             </listitem>
 
@@ -78,7 +78,7 @@
         </itemizedlist>
 
         <para>
-            The backend <acronym>SOAP</acronym> API is documented
+            The backend <acronym>SOAP</acronym> <acronym>API</acronym> is documented
             <ulink url="http://www.developergarden.com/openapi/dokumentation/">here</ulink>.
         </para>
 
@@ -86,8 +86,9 @@
             <title>Sign Up for an Account</title>
 
             <para>
-                Before you can start using the DeveloperGarden API, you first have to
-                <ulink url="http://www.developergarden.com/register">sign up</ulink> for an account.
+                Before you can start using the DeveloperGarden <acronym>API</acronym>, you first
+                have to <ulink url="http://www.developergarden.com/register">sign up</ulink> for an
+                account.
             </para>
         </sect3>
 
@@ -95,8 +96,8 @@
             <title>The Environment</title>
 
             <para>
-                With the DeveloperGarden API you have the possibility to choose between 3 different
-                development environments.
+                With the DeveloperGarden <acronym>API</acronym> you have the possibility to choose
+                between 3 different development environments.
             </para>
 
             <itemizedlist>
@@ -119,8 +120,9 @@
                 <listitem>
                     <para>
                         <emphasis>mock</emphasis>: The Mock environment allows you to build your
-                        application and have results but you do not initiate any action on the API
-                        side. This environment is intended for testing during development.
+                        application and have results but you do not initiate any action on the
+                        <acronym>API</acronym> side. This environment is intended for testing during
+                        development.
                     </para>
                 </listitem>
             </itemizedlist>
@@ -143,13 +145,15 @@
             <itemizedlist>
                 <listitem>
                     <para>
-                        <emphasis>username</emphasis>: Your DeveloperGarden API username.
+                        <emphasis>username</emphasis>: Your DeveloperGarden <acronym>API</acronym>
+                        username.
                     </para>
                 </listitem>
 
                 <listitem>
                     <para>
-                        <emphasis>password</emphasis>: Your DeveloperGarden API password.
+                        <emphasis>password</emphasis>: Your DeveloperGarden <acronym>API</acronym>
+                        password.
                     </para>
                 </listitem>
 
@@ -651,7 +655,7 @@ $service->tearDownCall($sessionId);
         </itemizedlist>
 
         <para>
-            Here is a list of currently implemented API methods:
+            Here is a list of currently implemented <acronym>API</acronym> methods:
         </para>
 
         <itemizedlist>

documentation/manual/en/module_specs/Zend_Service_LiveDocx.xml

@@ -87,8 +87,8 @@
             <para>
                 LiveDocx differentiates between the following terms: 1)
                 <emphasis>template</emphasis> and 2) <emphasis>document</emphasis>. In order to
-                fully understand the documentation and indeed the actual API, it is important that
-                any programmer deploying LiveDocx understands the difference.
+                fully understand the documentation and indeed the actual <acronym>API</acronym>, it
+                is important that any programmer deploying LiveDocx understands the difference.
             </para>
 
             <para>

documentation/manual/en/module_specs/Zend_Service_WindowsAzure_Blob.xml

@@ -10,9 +10,9 @@
     </para>
 
     <para>
-        Blob Storage is offered by Windows Azure as a <acronym>REST</acronym> API which is
-        wrapped by the <classname>Zend_Service_WindowsAzure_Storage_Blob</classname> class in
-        order to provide a native <acronym>PHP</acronym> interface to the storage account.
+        Blob Storage is offered by Windows Azure as a <acronym>REST</acronym> <acronym>API</acronym>
+        which is wrapped by the <classname>Zend_Service_WindowsAzure_Storage_Blob</classname> class
+        in order to provide a native <acronym>PHP</acronym> interface to the storage account.
     </para>
 
     <sect3 id="zend.service.windowsazure.storage.blob.api">
@@ -21,8 +21,8 @@
         <para>
             This topic lists some examples of using the
             <classname>Zend_Service_WindowsAzure_Storage_Blob</classname> class. Other features are
-            available in the download package, as well as a detailed API documentation of those
-            features.
+            available in the download package, as well as a detailed <acronym>API</acronym>
+            documentation of those features.
         </para>
 
         <sect4 id="zend.service.windowsazure.storage.blob.api.create-container">

documentation/manual/en/module_specs/Zend_Service_WindowsAzure_Queue.xml

@@ -17,8 +17,9 @@
     </para>
 
     <para>
-        Queue Storage is offered by Windows Azure as a <acronym>REST</acronym> API which is wrapped
-        by the <classname>Zend_Service_WindowsAzure_Storage_Queue</classname> class in order to
+        Queue Storage is offered by Windows Azure as a <acronym>REST</acronym>
+        <acronym>API</acronym> which is wrapped by the
+        <classname>Zend_Service_WindowsAzure_Storage_Queue</classname> class in order to
         provide a native <acronym>PHP</acronym> interface to the storage account.
     </para>
 
@@ -28,8 +29,8 @@
         <para>
             This topic lists some examples of using the
             <classname>Zend_Service_WindowsAzure_Storage_Queue</classname> class. Other features
-            are available in the download package, as well as a detailed API documentation of those
-            features.
+            are available in the download package, as well as a detailed <acronym>API</acronym>
+            documentation of those features.
         </para>
 
         <sect4 id="zend.service.windowsazure.storage.queue.api.create-queue">

documentation/manual/en/module_specs/Zend_Service_WindowsAzure_Table.xml

@@ -8,22 +8,22 @@
     </para>
 
     <para>
-        Table Storage is offered by Windows Azure as a REST API which is wrapped by the
-        <classname>Zend_Service_WindowsAzure_Storage_Table</classname> class in order to provide a
-        native <acronym>PHP</acronym> interface to the storage account.
+        Table Storage is offered by Windows Azure as a REST <acronym>API</acronym> which is wrapped
+        by the <classname>Zend_Service_WindowsAzure_Storage_Table</classname> class in order to
+        provide a native <acronym>PHP</acronym> interface to the storage account.
     </para>
 
     <para>
         This topic lists some examples of using the
         <classname>Zend_Service_WindowsAzure_Storage_Table</classname> class. Other features are
-        available in the download package, as well as a detailed API documentation of those
-        features.
+        available in the download package, as well as a detailed <acronym>API</acronym>
+        documentation of those features.
     </para>
 
     <para>
         Note that development table storage (in the Windows Azure SDK) does not support all features
-        provided by the API. Therefore, the examples listed on this page are to be used on Windows
-        Azure production table storage.
+        provided by the <acronym>API</acronym>. Therefore, the examples listed on this page are to
+        be used on Windows Azure production table storage.
     </para>
 
     <sect3 id="zend.service.windowsazure.storage.table.api">

documentation/manual/en/module_specs/Zend_Soap_Server.xml

@@ -205,7 +205,7 @@
 
         <para>
             The first one is to attach some class to the <classname>Zend_Soap_Server</classname>
-            object which has to completely describe Web Service API:
+            object which has to completely describe Web Service <acronym>API</acronym>:
 
             <programlisting language="php"><![CDATA[
 ...
@@ -254,9 +254,9 @@ $server->handle();
         </para>
 
         <para>
-            The second method of defining Web Service API is using set of functions and
-            <methodname>addFunction()</methodname> or <methodname>loadFunctions()</methodname>
-            methods:
+            The second method of defining Web Service <acronym>API</acronym> is using set of
+            functions and <methodname>addFunction()</methodname> or
+            <methodname>loadFunctions()</methodname> methods:
 
             <programlisting language="php"><![CDATA[
 ...

documentation/manual/en/module_specs/Zend_Tool-Extending.xml

@@ -785,7 +785,7 @@ class My_Component_HelloProvider
 ]]></programlisting>
 
                     <para>
-                        The API of the storage is very simple:
+                        The <acronym>API</acronym> of the storage is very simple:
                     </para>
 
                     <programlisting language="php"><![CDATA[

documentation/manual/en/module_specs/Zend_Tool_Framework-WritingProviders.xml

@@ -370,7 +370,7 @@ class My_Component_HelloProvider
 ]]></programlisting>
 
             <para>
-                The API of the storage is very simple:
+                The <acronym>API</acronym> of the storage is very simple:
             </para>
 
             <programlisting language="php"><![CDATA[

documentation/manual/en/tutorials/form-decorators-composite.xml

@@ -377,8 +377,8 @@ $d->setValue(array('year' => '2009', 'month' => '04', 'day' => '20'));
         </para>
 
         <para>
-            In the end, you get a uniform element API you can use to describe an element
-            representing a composite value.
+            In the end, you get a uniform element <acronym>API</acronym> you can use to describe an
+            element representing a composite value.
         </para>
     </sect2>
 </sect1>

documentation/manual/en/tutorials/multiuser-sessions.xml

@@ -34,10 +34,11 @@
         <title>Basic Usage of Zend_Session</title>
 
         <para>
-            The Zend_Session component is both a session manager as well as an API for
-            storing data into a session object for long-term persistence. The Zend_Session API is
-            for managing the options and behavior of a session, like options, starting and stopping
-            a session, whereas Zend_Session_Namespace is the actual object used to store data.
+            The Zend_Session component is both a session manager as well as an
+            <acronym>API</acronym> for storing data into a session object for long-term persistence.
+            The Zend_Session <acronym>API</acronym> is for managing the options and behavior of a
+            session, like options, starting and stopping a session, whereas Zend_Session_Namespace
+            is the actual object used to store data.
         </para>
 
         <para>
@@ -74,12 +75,12 @@ resources.session.remember_me_seconds = 864000
         </para>
 
         <para>
-            Zend_Session_Namespace is a simple class that proxies data via an easy to use API
-            into the Zend_Session managed $_SESSION superglobal. The reason it is called
-            Zend_Session_Namespace is that it effectively namespaces the data inside $_SESSION, thus
-            allowing multiple components and objects to safely store and retrieve data. In the
-            following code, we'll explore how to build a simple session incrementing counter,
-            starting at 1000 and resetting itself after 1999.
+            Zend_Session_Namespace is a simple class that proxies data via an easy to use
+            <acronym>API</acronym> into the Zend_Session managed $_SESSION superglobal. The reason
+            it is called Zend_Session_Namespace is that it effectively namespaces the data inside
+            $_SESSION, thus allowing multiple components and objects to safely store and retrieve
+            data. In the following code, we'll explore how to build a simple session incrementing
+            counter, starting at 1000 and resetting itself after 1999.
         </para>
 
         <programlisting language="php"><![CDATA[

documentation/manual/en/tutorials/paginator-together.xml

@@ -69,8 +69,9 @@ foreach ($this->paginator as $item) {
 
     <para>
         Now navigate to your project's index and see Paginator in action. What we have discussed
-        in this tutorial is just the tip of the iceberg. The reference manual and API documentation
-        can tell you more about what you can do with Zend_Paginator.
+        in this tutorial is just the tip of the iceberg. The reference manual and
+        <acronym>API</acronym> documentation can tell you more about what you can do with
+        Zend_Paginator.
     </para>
 
 </sect1>

documentation/manual/en/tutorials/quickstart-create-model.xml

@@ -35,7 +35,7 @@
         <emphasis>email address</emphasis>. Assuming we store them in a database, we may also want a
         <emphasis>unique identifier</emphasis> for each entry. We'll likely want to be able to save
         an entry, fetch individual entries, and retrieve all entries. As such, a simple guestbook
-        model API might look something like this:
+        model <acronym>API</acronym> might look something like this:
     </para>
 
     <programlisting language="php"><![CDATA[
@@ -420,8 +420,8 @@ class Application_Model_DbTable_Guestbook extends Zend_Db_Table_Abstract
         Now let's create a <ulink url="http://martinfowler.com/eaaCatalog/dataMapper.html">Data
             Mapper</ulink>. A <emphasis>Data Mapper</emphasis> maps a domain object to the database.
         In our case, it will map our model, <classname>Application_Model_Guestbook</classname>, to
-        our data source, <classname>Application_Model_DbTable_Guestbook</classname>. A typical API
-        for a data mapper is as follows:
+        our data source, <classname>Application_Model_DbTable_Guestbook</classname>. A typical
+        <acronym>API</acronym> for a data mapper is as follows:
     </para>
 
     <programlisting language="php"><![CDATA[