ZF-10989: Note: Note: appearing in coding standards docs

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

documentation/manual/en/ref/coding_standard.xml

@@ -19,11 +19,11 @@
 
             <note>
                 <para>
-                    Note: Sometimes developers consider the establishment of a standard more
-                    important than what that standard actually suggests at the most detailed level
-                    of design. The guidelines in Zend Framework's coding standards capture
-                    practices that have worked well on the Zend Framework project. You may modify
-                    these standards or use them as is in accordance with the terms of our <ulink
+                    Sometimes developers consider the establishment of a standard more important
+                    than what that standard actually suggests at the most detailed level of
+                    design. The guidelines in Zend Framework's coding standards capture practices
+                    that have worked well on the Zend Framework project. You may modify these
+                    standards or use them as is in accordance with the terms of our <ulink
                         url="http://framework.zend.com/license">license</ulink>.
                 </para>
             </note>
@@ -800,8 +800,8 @@ class Foo
 
                 <note>
                     <para>
-                        <emphasis>Note</emphasis>: Pass-by-reference is the only parameter passing
-                        mechanism permitted in a method declaration.
+                        Pass-by-reference is the only parameter passing mechanism permitted in a
+                        method declaration.
                     </para>
                 </note>
 
@@ -1027,13 +1027,13 @@ switch ($numPeople) {
 
                 <note>
                     <para>
-                        <emphasis>Note</emphasis>: It is sometimes useful to write a
-                        <property>case</property> statement which falls through to the next case by
-                        not including a <property>break</property> or <property>return</property>
-                        within that case. To distinguish these cases from bugs, any
-                        <property>case</property> statement where <property>break</property> or
-                        <property>return</property> are omitted should contain a comment indicating
-                        that the break was intentionally omitted.
+                        It is sometimes useful to write a <property>case</property> statement
+                        which falls through to the next case by not including a
+                        <property>break</property> or <property>return</property> within that
+                        case. To distinguish these cases from bugs, any <property>case</property>
+                        statement where <property>break</property> or <property>return</property>
+                        are omitted should contain a comment indicating that the break was
+                        intentionally omitted.
                     </para>
                 </note>
             </sect3>