[MANUAL] English:

- some manual fixes

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

documentation/manual/en/module_specs/Zend_Gdata_Gapps.xml

@@ -135,7 +135,7 @@ $user = $gdata->insertUser($user);
             <para>
                 The user's password should normally be provided as cleartext.
                 Optionally, the password can be provided as an SHA-1 digest if
-                <code>login->passwordHashFunction</code> is set to 'SHA-1'.
+                <command>login->passwordHashFunction</command> is set to 'SHA-1'.
             </para>
         </sect3>
 
@@ -256,7 +256,7 @@ $user = $user->save();
 
                 <para>
                     A user's password can be reset to a new value by updating
-                    the <code>login->password</code> property.
+                    the <command>login->password</command> property.
                 </para>
 
                 <programlisting language="php"><![CDATA[
@@ -278,7 +278,7 @@ $user = $user->save();
                 <para>
                     A user can be forced to change their password at their
                     next login by setting the
-                    <code>login->changePasswordAtNextLogin</code> property to
+                    <command>login->changePasswordAtNextLogin</command> property to
                     <constant>TRUE</constant>.
                 </para>
 
@@ -290,7 +290,7 @@ $user = $user->save();
 
                 <para>
                     Similarly, this can be undone by setting the
-                    <code>login->changePasswordAtNextLogin</code> property to
+                    <command>login->changePasswordAtNextLogin</command> property to
                     <constant>FALSE</constant>.
                 </para>
             </sect4>
@@ -314,7 +314,7 @@ $gdata->restoreUser('foo');
 
                 <para>
                     Alternatively, you can set the UserEntry's
-                    <code>login->suspended</code> property to
+                    <command>login->suspended</command> property to
                     <constant>TRUE</constant>.
                 </para>
 
@@ -326,7 +326,7 @@ $user = $user->save();
 
                 <para>
                     To restore the user's access, set the
-                    <code>login->suspended</code> property to
+                    <command>login->suspended</command> property to
                     <constant>FALSE</constant>.
                 </para>
             </sect4>
@@ -336,7 +336,7 @@ $user = $user->save();
 
                 <para>
                     Users can be granted the ability to administer your domain
-                    by setting their <code>login->admin</code> property to
+                    by setting their <command>login->admin</command> property to
                     <constant>TRUE</constant>.
                 </para>
 
@@ -347,7 +347,7 @@ $user = $user->save();
 ]]></programlisting>
 
                 <para>
-                    And as expected, setting a user's <code>login->admin</code>
+                    And as expected, setting a user's <command>login->admin</command>
                     property to <constant>FALSE</constant> revokes their
                     administrative rights.
                 </para>

documentation/manual/en/module_specs/Zend_Gdata_Gbase.xml

@@ -321,7 +321,7 @@ $feed = $service->getGbaseSnippetFeed($query);
 
             <para>
                 Google Base items can contain item-specific attributes such as
-                <code>&lt;g:main_ingredient&gt;</code> and <code>&lt;g:weight&gt;</code>.
+                <emphasis>&lt;g:main_ingredient&gt;</emphasis> and <emphasis>&lt;g:weight&gt;</emphasis>.
             </para>
 
             <para>

documentation/manual/en/module_specs/Zend_Gdata_Health.xml

@@ -283,9 +283,9 @@ $healthService = new Zend_Gdata_Health($client,
 
         <para>
             To query the user's profile feed, make sure your initial AuthSub token was requested
-            with the <code>permission=1</code> parameter set. The process of extracting data from
-            the profile requires two steps, sending a query and iterating through the resulting
-            feed.
+            with the <property>permission</property> parameter set to <emphasis>1</emphasis>. The
+            process of extracting data from the profile requires two steps, sending a query and
+            iterating through the resulting feed.
         </para>
 
         <sect3 id="zend.gdata.health.profilefeed.query">
@@ -328,7 +328,7 @@ $profileFeed = $healthService->getHealthProfileFeed($query);
 
                 <para>
                     Using <methodname>setDigest("true")</methodname> returns all of user's CCR data
-                    in a single Atom <code>&lt;entry&gt;</code>.
+                    in a single Atom <emphasis>&lt;entry&gt;</emphasis>.
                 </para>
 
                 <para>
@@ -354,8 +354,9 @@ $profileFeed = $healthService->getHealthProfileFeed($query);
 
             <para>
                 Each Google Health entry contains CCR data, however, using the
-                <code>digest=true</code> query parameter will consolidate all of the CCR elements
-                (that match your query) into a single Atom <code>&lt;entry&gt;</code>.
+                <property>digest</property> query parameter and setting is to
+                <constant>TRUE</constant> will consolidate all of the CCR elements
+                (that match your query) into a single Atom <emphasis>&lt;entry&gt;</emphasis>.
             </para>
 
             <para>
@@ -423,8 +424,8 @@ foreach ($conditions as $cond) {
             Since ClientLogin requires a profile ID with each of its feeds, applications will likely
             want to query this feed first in order to select the appropriate profile. The profile
             list feed returns Atom entries corresponding each profile in the user's Google Health
-            account. The profile ID is returned in the Atom <code>&lt;content&gt;</code> and the
-            profile name in the <code>&lt;title&gt;</code> element.
+            account. The profile ID is returned in the Atom <emphasis>&lt;content&gt;</emphasis> and
+            the profile name in the <emphasis>&lt;title&gt;</emphasis> element.
         </para>
 
         <sect3 id="zend.gdata.health.profilelist.query">