Add IP and ACL notation fixes

Author: bicpi

cookbook/cache/varnish.rst

@@ -137,7 +137,7 @@ that will invalidate the cache for a given resource:
             .port = "8080";
         }
 
-        // Acl's can contain IP's, subnets and hostnames
+        // ACL's can contain IP's, subnets and hostnames
         acl purge {
             "localhost";
             "192.168.55.0"/24;
@@ -146,7 +146,7 @@ that will invalidate the cache for a given resource:
         sub vcl_recv {
             // Match PURGE request to avoid cache bypassing
             if (req.request == "PURGE") {
-                // Match client IP to the acl
+                // Match client IP to the ACL
                 if (!client.ip ~ purge) {
                     // Deny access
                     error 405 "Not allowed.";

cookbook/profiler/matchers.rst

@@ -16,7 +16,7 @@ Using the built-in Matcher
 Symfony2 provides a
 :class:`built-in matcher <Symfony\\Component\\HttpFoundation\\RequestMatcher>`
 which can match paths and IPs. For example, if you want to only show the
-profiler when accessing the page with the ``168.0.0.1`` ip, then you can
+profiler when accessing the page with the ``168.0.0.1`` IP, then you can
 use this configuration:
 
 .. configuration-block::

cookbook/security/voters.rst

@@ -31,7 +31,7 @@ which requires the following three methods:
     }
 
 The ``supportsAttribute()`` method is used to check if the voter supports
-the given user attribute (i.e: a role, an acl, etc.).
+the given user attribute (i.e: a role, an ACL, etc.).
 
 The ``supportsClass()`` method is used to check if the voter supports the
 current user token class.

reference/constraints/Ip.rst

@@ -83,7 +83,7 @@ version
 
 **type**: ``string`` **default**: ``4``
 
-This determines exactly *how* the ip address is validated and can take one
+This determines exactly *how* the IP address is validated and can take one
 of a variety of different values:
 
 **All ranges**