@@ -89,7 +89,7 @@ the project directory and executing this command:
8989 $cd myproject/
9090 $ php app/console server:run
9191
92- http://localhost:8000 `` URL to see the
92+ http://localhost:8000/app/example `` URL to see the
9393welcome page of Symfony:
9494
9595..image ::/images/quick_tour/welcome.png
@@ -106,20 +106,16 @@ Congratulations! Your first Symfony project is up and running!
106106 them are explained in the
107107:ref: `Setting up Permissions <book-installation-permissions >` section
108108 of the official book.
109-
109+
110110 If the welcome page does not seem to be rendering CSS or image assets,
111111 install them first:
112-
112+
113113 ..code-block ::bash
114-
114+
115115 $ php app/console assets:install
116116
117117
118- the server with the ``server:stop `` command:
119-
120- ..code-block ::bash
121-
122- $ php app/console server:stop
118+ the server by pressing Ctrl and C.
123119
124120..tip ::
125121
@@ -135,15 +131,15 @@ of database calls, HTML tags and other PHP code in the same script. To achieve
135131this goal with Symfony, you'll first need to learn a few fundamental concepts.
136132
137133When developing a Symfony application, your responsibility as a developer
138- is to write the code that maps the user's *request * (e.g. ``http://localhost:8000/ ``)
139- to the *resource * associated with it (the ``Welcome to Symfony! `` HTML page).
134+ is to write the code that maps the user's *request * (e.g. ``http://localhost:8000/app/example ``)
135+ to the *resource * associated with it (the ``Homepage `` HTML page).
140136
141137The code to execute is defined in **actions ** and **controllers **. The mapping
142138between user's requests and that code is defined via the **routing ** configuration.
143139And the contents displayed in the browser are usually rendered using **templates **.
144140
145- When you browsed ``http://localhost:8000/ `` earlier, Symfony executed the
146- controller defined in the ``src/AppBundle/Controller/DefaultController.php ``
141+ When you browsed ``http://localhost:8000/app/example `` earlier, Symfony executed
142+ the controller defined in the ``src/AppBundle/Controller/DefaultController.php ``
147143file and rendered the ``app/Resources/views/default/index.html.twig `` template.
148144In the following sections you'll learn in detail the inner workings of Symfony
149145controllers, routes and templates.
@@ -186,7 +182,7 @@ information and then they render a template to show the results to the user.
186182
187183In this example, the ``index `` action is practically empty because it doesn't
188184need to call any other method. The action just renders a template with the
189- *Welcome to Symfony! * content.
185+ *Homepage. * content.
190186
191187Routing
192188~~~~~~~
@@ -221,8 +217,8 @@ start with ``/**``, whereas regular PHP comments start with ``/*``.
221217The first value of ``@Route() `` defines the URL that will trigger the execution
222218of the action. As you don't have to add the host of your application to
223219the URL (e.g. ```http://example.com ``), these URLs are always relative and
224- they are usually called *paths *. In this case, the ``/ `` path refers to
225- the application homepage. The second value of ``@Route() `` (e.g.
220+ they are usually called *paths *. In this case, the ``/app/example `` path
221+ refers to the application homepage. The second value of ``@Route() `` (e.g.
226222``name="homepage" ``) is optional and sets the name of this route. For now
227223this name is not needed, but later it'll be useful for linking pages.
228224