Browse Source

[MANUAL] English:

- manual fixes

git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@19999 44c647ce-9c0f-0410-b52a-842ac1e357ba
thomas 16 years ago
parent
commit
5f483e9694

+ 11 - 11
documentation/manual/en/tutorials/form-decorators-layering.xml

@@ -45,15 +45,15 @@
 
 
         <listitem>
         <listitem>
             <para>
             <para>
-                <classname>HtmlTag</classname> (wrap all of the above in a <code>&lt;dd&gt;</code>
-                tag.
+                <classname>HtmlTag</classname> (wrap all of the above in a
+                <emphasis>&lt;dd&gt;</emphasis> tag.
             </para>
             </para>
         </listitem>
         </listitem>
 
 
         <listitem>
         <listitem>
             <para>
             <para>
                 <classname>Label</classname> (render the label preceding the above, wrapped in a
                 <classname>Label</classname> (render the label preceding the above, wrapped in a
-                <code>&lt;dt&gt;</code> tag.
+                <emphasis>&lt;dt&gt;</emphasis> tag.
             </para>
             </para>
         </listitem>
         </listitem>
     </itemizedlist>
     </itemizedlist>
@@ -141,7 +141,7 @@ class My_Decorator_SimpleLabel extends Zend_Form_Decorator_Abstract
 
 
     <para>
     <para>
         Now, this may look all well and good, but here's the problem: as written currently, the last
         Now, this may look all well and good, but here's the problem: as written currently, the last
-        decorator to run wins, and overwrites everything.  You'll end up with just the input, or
+        decorator to run wins, and overwrites everything. You'll end up with just the input, or
         just the label, depending on which you register last.
         just the label, depending on which you register last.
     </para>
     </para>
 
 
@@ -254,8 +254,8 @@ $element = new Zend_Form_Element('foo', array(
         <listitem>
         <listitem>
             <para>
             <para>
                 '' is passed to the <classname>SimpleInput</classname> decorator, which then
                 '' is passed to the <classname>SimpleInput</classname> decorator, which then
-                generates a form input that it appends to the empty string: <code>&lt;input
-                    id="bar-foo" name="bar[foo]" type="text" value="test"/&gt;</code>.
+                generates a form input that it appends to the empty string: <emphasis>&lt;input
+                    id="bar-foo" name="bar[foo]" type="text" value="test"/&gt;</emphasis>.
             </para>
             </para>
         </listitem>
         </listitem>
 
 
@@ -264,8 +264,8 @@ $element = new Zend_Form_Element('foo', array(
                 The input is then passed as content to the <classname>SimpleLabel</classname>
                 The input is then passed as content to the <classname>SimpleLabel</classname>
                 decorator, which generates a label and prepends it to the original content; the
                 decorator, which generates a label and prepends it to the original content; the
                 default separator is a <constant>PHP_EOL</constant> character, giving us this:
                 default separator is a <constant>PHP_EOL</constant> character, giving us this:
-                <code>&lt;label for="bar-foo"&gt;\n&lt;input id="bar-foo" name="bar[foo]"
-                    type="text" value="test"/&gt;</code>.
+                <emphasis>&lt;label for="bar-foo"&gt;\n&lt;input id="bar-foo" name="bar[foo]"
+                    type="text" value="test"/&gt;</emphasis>.
             </para>
             </para>
         </listitem>
         </listitem>
     </itemizedlist>
     </itemizedlist>
@@ -298,8 +298,8 @@ $element = new Zend_Form_Element('foo', array(
     </para>
     </para>
 
 
     <para>
     <para>
-        The above results in the markup <code>&lt;input id="bar-foo" name="bar[foo]" type="text"
-            value="test"/&gt;\n&lt;label for="bar-foo"&gt;</code>.
+        The above results in the markup <emphasis>&lt;input id="bar-foo" name="bar[foo]" type="text"
+            value="test"/&gt;\n&lt;label for="bar-foo"&gt;</emphasis>.
     </para>
     </para>
 
 
     <para>
     <para>
@@ -339,7 +339,7 @@ $element = new Zend_Form_Element('foo', array(
             <para>
             <para>
                 Reusable decorators. You can create truly re-usable decorators with this technique,
                 Reusable decorators. You can create truly re-usable decorators with this technique,
                 as you don't have to worry about the complete markup, but only markup for one or a
                 as you don't have to worry about the complete markup, but only markup for one or a
-                few pieces of element/form metadata.
+                few pieces of element or form metadata.
             </para>
             </para>
         </listitem>
         </listitem>
 
 

+ 3 - 3
documentation/manual/en/tutorials/form-decorators-simplest.xml

@@ -9,7 +9,7 @@
         <para>
         <para>
             To begin, we'll cover some background on the <ulink
             To begin, we'll cover some background on the <ulink
                 url="http://en.wikipedia.org/wiki/Decorator_pattern">Decorator design
                 url="http://en.wikipedia.org/wiki/Decorator_pattern">Decorator design
-                pattern</ulink>.  One common technique is to define a common interface that both
+                pattern</ulink>. One common technique is to define a common interface that both
             your originating object and decorator will implement; your decorator than accepts the
             your originating object and decorator will implement; your decorator than accepts the
             originating object as a dependency, and will either proxy to it or override its methods.
             originating object as a dependency, and will either proxy to it or override its methods.
             Let's put that into code to make it more easily understood:
             Let's put that into code to make it more easily understood:
@@ -148,7 +148,7 @@ class TextPerson
             This latter example is getting close to how <classname>Zend_Form</classname> decorators
             This latter example is getting close to how <classname>Zend_Form</classname> decorators
             work. The key difference is that instead of a decorator wrapping the element, the
             work. The key difference is that instead of a decorator wrapping the element, the
             element has one or more decorators attached to it that it then injects itself into in
             element has one or more decorators attached to it that it then injects itself into in
-            order to render.  The decorator then can access the element's methods and properties in
+            order to render. The decorator then can access the element's methods and properties in
             order to create a representation of the element -- or a subset of it.
             order to create a representation of the element -- or a subset of it.
         </para>
         </para>
     </sect2>
     </sect2>
@@ -158,7 +158,7 @@ class TextPerson
 
 
         <para>
         <para>
             <classname>Zend_Form</classname> decorators all implement a common interface,
             <classname>Zend_Form</classname> decorators all implement a common interface,
-            <interfacename>Zend_Form_Decorator_Interface</interfacename>. That interface provides
+            <classname>Zend_Form_Decorator_Interface</classname>. That interface provides
             the ability to set decorator-specific options, register and retrieve the element, and
             the ability to set decorator-specific options, register and retrieve the element, and
             render. A base decorator, <classname>Zend_Form_Decorator_Abstract</classname>, provides
             render. A base decorator, <classname>Zend_Form_Decorator_Abstract</classname>, provides
             most of the functionality you will ever need, with the exception of the rendering logic.
             most of the functionality you will ever need, with the exception of the rendering logic.