Pārlūkot izejas kodu

[MANUAL] English:

- manual fixes

git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@19997 44c647ce-9c0f-0410-b52a-842ac1e357ba
thomas 16 gadi atpakaļ
vecāks
revīzija
a9b8b026bc
1 mainītis faili ar 6 papildinājumiem un 4 dzēšanām
  1. 6 4
      documentation/manual/en/tutorials/plugins-intro.xml

+ 6 - 4
documentation/manual/en/tutorials/plugins-intro.xml

@@ -5,7 +5,7 @@
 
     <para>
         Zend Framework makes heavy use of plugin architectures. Plugins allow for easy extensibility
-        and customization of the framework while keeping your code separate from the Zend Framework
+        and customization of the framework while keeping your code separate from Zend Framework's
         code.
     </para>
 
@@ -25,7 +25,8 @@
         <listitem>
             <para>
                 Related plugins will share a common class prefix. For instance, if you have created
-                a number of view helpers, they might all share the class prefix "Foo_View_Helper_".
+                a number of view helpers, they might all share the class prefix
+                "<classname>Foo_View_Helper_</classname>".
             </para>
         </listitem>
 
@@ -34,8 +35,9 @@
                 Everything after the common prefix will be considered the <emphasis>plugin
                     name</emphasis> or <emphasis>short name</emphasis> (versus the "long name",
                 which is the full classname). For example, if the plugin prefix is
-                "Foo_View_Helper_", and the class name is "Foo_View_Helper_Bar", the plugin name
-                will be simply "Bar".
+                "<classname>Foo_View_Helper_</classname>", and the class name is
+                "<classname>Foo_View_Helper_Bar</classname>", the plugin name will be simply
+                "<classname>Bar</classname>".
             </para>
         </listitem>