consisteny, use "front-end" instead of "frontend" or "front end"

Author: xabbuh

book/routing.rst

@@ -1407,7 +1407,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 front-end 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:
 

cookbook/assetic/asset_management.rst

@@ -204,7 +204,7 @@ Combining Assets
 ~~~~~~~~~~~~~~~~
 
 One feature of Assetic is that it will combine many files into one. This helps
-to reduce the number of HTTP requests, which is great for front end performance.
+to reduce the number of HTTP requests, which is great for front-end performance.
 It also allows you to maintain the files more easily by splitting them into
 manageable parts. This can help with re-usability as you can easily split
 project-specific files from those which can be used in other applications,

cookbook/configuration/front_controllers_and_kernel.rst

@@ -129,7 +129,7 @@ controller to make use of the new kernel.
 
 Having different ``AppKernels`` might be useful to enable different front
 controllers (on potentially different servers) to run parts of your application
-independently (for example, the admin UI, the frontend UI and database migrations).
+independently (for example, the admin UI, the front-end UI and database migrations).
 
 .. note::
 

cookbook/symfony1.rst

@@ -200,14 +200,14 @@ Applications
 ------------
 
 In a symfony1 project, it is common to have several applications: one for the
-frontend and one for the backend for instance.
+front-end and one for the back-end for instance.
 
 In a Symfony2 project, you only need to create one application (a blog
 application, an intranet application, ...). Most of the time, if you want to
 create a second application, you might instead create another project and
 share some bundles between them.
 
-And if you need to separate the frontend and the backend features of some
+And if you need to separate the front-end and the back-end features of some
 bundles, you can create sub-namespaces for controllers, sub-directories for
 templates, different semantic configurations, separate routing configurations,
 and so on.

reference/forms/types/integer.rst

@@ -7,7 +7,7 @@ integer Field Type
 Renders an input "number" field. Basically, this is a text field that's good
 at handling data that's in an integer form. The input ``number`` field looks
 like a text box, except that - if the user's browser supports HTML5 - it will
-have some extra frontend functionality.
+have some extra front-end functionality.
 
 This field has different options on how to handle input values that aren't
 integers. By default, all non-integer values (e.g. 6.78) will round down (e.g. 6).