Fix HTTPS and Ajax notation

bicpi · bicpi · commit 2f01f88ac848 · 2013-11-17T06:00:27.000+01:00
diff --git a/book/http_fundamentals.rst b/book/http_fundamentals.rst
@@ -246,7 +246,7 @@ have all the request information at your fingertips::
 As a bonus, the ``Request`` class does a lot of work in the background that
 you'll never need to worry about. For example, the ``isSecure()`` method
 checks the *three* different values in PHP that can indicate whether or not
-the user is connecting via a secured connection (i.e. ``https``).
+the user is connecting via a secured connection (i.e. HTTPS).
 
 .. sidebar:: ParameterBags and Request attributes
 
diff --git a/book/routing.rst b/book/routing.rst
@@ -1175,7 +1175,7 @@ In an upcoming section, you'll learn how to generate URLs from inside templates.
 
 .. tip::
 
-    If the frontend of your application uses AJAX requests, you might want
+    If the frontend of your application uses Ajax requests, you might want
     to be able to generate URLs in JavaScript based on your routing configuration.
     By using the `FOSJsRoutingBundle`_, you can do exactly that:
 
diff --git a/cookbook/form/dynamic_form_modification.rst b/cookbook/form/dynamic_form_modification.rst
@@ -527,7 +527,7 @@ only because in two different scenarios, the data that you can use is available
 Other than that, the listeners always perform exactly the same things on a given form.
 
 One piece that may still be missing is the client-side updating of your form
-after the sport is selected. This should be handled by making an AJAX call
+after the sport is selected. This should be handled by making an Ajax call
 back to your application. In that controller, you can bind your form, but
 instead of processing it, simply use the bound form to render the updated
-fields. The response from the AJAX call can then be used to update the view.
+fields. The response from the Ajax call can then be used to update the view.
diff --git a/cookbook/routing/scheme.rst b/cookbook/routing/scheme.rst
@@ -66,7 +66,7 @@ to always use ``http``.
 
 .. note::
 
-    The Security component provides another way to enforce HTTP or HTTPs via
+    The Security component provides another way to enforce HTTP or HTTPS via
     the ``requires_channel`` setting. This alternative method is better suited
     to secure an "area" of your website (all URLs under ``/admin``) or when
     you want to secure URLs defined in a third party bundle.
diff --git a/cookbook/security/force_https.rst b/cookbook/security/force_https.rst
@@ -4,10 +4,10 @@
 How to force HTTPS or HTTP for Different URLs
 =============================================
 
-You can force areas of your site to use the ``HTTPS`` protocol in the security
+You can force areas of your site to use the HTTPS protocol in the security
 config. This is done through the ``access_control`` rules using the ``requires_channel``
 option. For example, if you want to force all URLs starting with ``/secure``
-to use ``HTTPS`` then you could use the following configuration:
+to use HTTPS then you could use the following configuration:
 
 .. configuration-block::
 
@@ -35,7 +35,7 @@ to use ``HTTPS`` then you could use the following configuration:
             ),
 
 The login form itself needs to allow anonymous access, otherwise users will
-be unable to authenticate. To force it to use ``HTTPS`` you can still use
+be unable to authenticate. To force it to use HTTPS you can still use
 ``access_control`` rules by using the ``IS_AUTHENTICATED_ANONYMOUSLY``
 role:
 
@@ -66,5 +66,5 @@ role:
                 ),
             ),
 
-It is also possible to specify using ``HTTPS`` in the routing configuration
+It is also possible to specify using HTTPS in the routing configuration,
 see :doc:`/cookbook/routing/scheme` for more details.
diff --git a/cookbook/security/form_login.rst b/cookbook/security/form_login.rst
@@ -34,7 +34,7 @@ in several ways.
 .. note::
 
     As mentioned, by default the user is redirected back to the page he originally
-    requested. Sometimes, this can cause problems, like if a background AJAX
+    requested. Sometimes, this can cause problems, like if a background Ajax
     request "appears" to be the last visited URL, causing the user to be
     redirected there. For information on controlling this behavior, see
     :doc:`/cookbook/security/target_path`.
