Browse Source

[MANUAL] English:

- manual fixes

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

+ 7 - 5
documentation/manual/en/module_specs/Zend_Validate-Hostname.xml

@@ -6,8 +6,9 @@
     <para>
     <para>
         <classname>Zend_Validate_Hostname</classname> allows you to validate a hostname against a
         <classname>Zend_Validate_Hostname</classname> allows you to validate a hostname against a
         set of known specifications. It is possible to check for three different types of hostnames:
         set of known specifications. It is possible to check for three different types of hostnames:
-        a DNS Hostname (i.e. domain.com), IP address (i.e. 1.2.3.4), and Local hostnames (i.e.
-        localhost). By default only DNS hostnames are matched.
+        a <acronym>DNS</acronym> Hostname (i.e. <filename>domain.com</filename>), IP address (i.e.
+        1.2.3.4), and Local hostnames (i.e. localhost). By default only <acronym>DNS</acronym>
+        hostnames are matched.
     </para>
     </para>
 
 
     <sect3 id="zend.validate.set.hostname.options">
     <sect3 id="zend.validate.set.hostname.options">
@@ -112,8 +113,9 @@ if ($validator->isValid($hostname)) {
 
 
         <para>
         <para>
             As well as using <constant>ALLOW_ALL</constant> to accept all hostnames types you can
             As well as using <constant>ALLOW_ALL</constant> to accept all hostnames types you can
-            combine these types to allow for combinations. For example, to accept DNS and Local
-            hostnames instantiate your <classname>Zend_Validate_Hostname</classname> object as so:
+            combine these types to allow for combinations. For example, to accept
+            <acronym>DNS</acronym> and Local hostnames instantiate your
+            <classname>Zend_Validate_Hostname</classname> object as so:
         </para>
         </para>
 
 
         <programlisting language="php"><![CDATA[
         <programlisting language="php"><![CDATA[
@@ -137,7 +139,7 @@ $validator = new Zend_Validate_Hostname(Zend_Validate_Hostname::ALLOW_DNS |
             <title>IDN domains</title>
             <title>IDN domains</title>
 
 
             <para>
             <para>
-                Until now more than 50 ccTLDs support IDN domains.
+                Until now more than 50 ccTLDs support <acronym>IDN</acronym> domains.
             </para>
             </para>
         </note>
         </note>
 
 

+ 3 - 3
documentation/manual/en/module_specs/Zend_Validate-Identical.xml

@@ -157,7 +157,7 @@ if ($valid->isValid($input)) {
 
 
         <para>
         <para>
             But this adds one case which you have to be aware. When you are using an array as
             But this adds one case which you have to be aware. When you are using an array as
-            haystack then you should wrap it within an <property>'token'</property> key when
+            haystack then you should wrap it within an '<property>token</property>' key when
             it could contain only one element.
             it could contain only one element.
         </para>
         </para>
 
 
@@ -173,12 +173,12 @@ if ($valid->isValid($input)) {
         <para>
         <para>
             The above example validates the integer 123. The reason for this special case is, that
             The above example validates the integer 123. The reason for this special case is, that
             you can configure the token which has to be used by giving the
             you can configure the token which has to be used by giving the
-            <property>'token'</property> key.
+            '<property>token</property>' key.
         </para>
         </para>
 
 
         <para>
         <para>
             So, when your haystack contains one element and this element is named
             So, when your haystack contains one element and this element is named
-            <property>'token'</property> then you have to wrap it like shown in the example below.
+            '<property>token</property>' then you have to wrap it like shown in the example below.
         </para>
         </para>
 
 
         <programlisting language="php"><![CDATA[
         <programlisting language="php"><![CDATA[

+ 4 - 2
documentation/manual/en/module_specs/Zend_Validate-Ip.xml

@@ -53,7 +53,8 @@ if ($validator->isValid($ip)) {
 
 
             <para>
             <para>
                 Keep in mind that <classname>Zend_Validate_Ip</classname> only validates IP
                 Keep in mind that <classname>Zend_Validate_Ip</classname> only validates IP
-                addresses. Addresses like 'mydomain.com' or '192.168.50.1/index.html' are no valid
+                addresses. Addresses like '<filename>mydomain.com</filename>' or
+                '<filename>192.168.50.1/index.html</filename>' are no valid
                 IP addresses. They are either hostnames or valid <acronym>URL</acronym>s but not IP
                 IP addresses. They are either hostnames or valid <acronym>URL</acronym>s but not IP
                 addresses.
                 addresses.
             </para>
             </para>
@@ -65,7 +66,8 @@ if ($validator->isValid($ip)) {
             <para>
             <para>
                 <classname>Zend_Validate_Ip</classname> validates IPv6 addresses with regex. The
                 <classname>Zend_Validate_Ip</classname> validates IPv6 addresses with regex. The
                 reason is that the filters and methods from <acronym>PHP</acronym> itself don't
                 reason is that the filters and methods from <acronym>PHP</acronym> itself don't
-                follow the RFC. Many other available classes also don't follow it.
+                follow the <acronym>RFC</acronym>. Many other available classes also don't follow
+                it.
             </para>
             </para>
         </note>
         </note>
     </sect3>
     </sect3>

+ 1 - 1
documentation/manual/en/module_specs/Zend_Validate-Regex.xml

@@ -44,7 +44,7 @@ $validator->isValid("Pest"); // returns false
 
 
         <para>
         <para>
             As you can see, the pattern has to be given using the same syntax as for
             As you can see, the pattern has to be given using the same syntax as for
-            <methodname>preg_match</methodname>. For details about regular expressions take a look
+            <methodname>preg_match()</methodname>. For details about regular expressions take a look
             into <ulink url="http://php.net/manual/en/reference.pcre.pattern.syntax.php">PHP's
             into <ulink url="http://php.net/manual/en/reference.pcre.pattern.syntax.php">PHP's
                 manual about PCRE pattern syntax</ulink>.
                 manual about PCRE pattern syntax</ulink>.
         </para>
         </para>