@@ -13,7 +13,7 @@ ideas from many technologies: the tools and concepts you're about to learn
13
13
represent the efforts of thousands of people, over many years. In other words,
14
14
you're not just learning "Symfony", you're learning the fundamentals of the
15
15
web, development best practices, and how to use many amazing new PHP libraries,
16
- inside or independent of Symfony2. So, get ready.
16
+ inside or independently of Symfony2. So, get ready.
17
17
18
18
True to the Symfony2 philosophy, this chapter begins by explaining the fundamental
19
19
concept common to web development: HTTP. Regardless of your background or
@@ -298,7 +298,7 @@ and create the appropriate response based on your application logic*.
298
298
299
299
The ``Request `` and ``Response `` classes are part of a standalone component
300
300
included with Symfony called ``HttpFoundation ``. This component can be
301
- used entirely independent of Symfony and also provides classes for handling
301
+ used entirely independently of Symfony and also provides classes for handling
302
302
sessions and file uploads.
303
303
304
304
The Journey from the Request to the Response
@@ -351,7 +351,7 @@ file that handles every request coming into your application. For example:
351
351
the URLs can easily be cleaned up to be just ``/ ``, ``/contact `` and
352
352
``/blog ``.
353
353
354
- Now, every request is handled exactly the same. Instead of individual URLs
354
+ Now, every request is handled exactly the same way . Instead of individual URLs
355
355
executing different PHP files, the front controller is *always * executed,
356
356
and the routing of different URLs to different parts of your application
357
357
is done internally. This solves both problems with the original approach.
0 commit comments