Skip to content

Commit baf9213

Browse files
authored
Fix typos
1 parent d53bd31 commit baf9213

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

quick_tour/the_architecture.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ great tools for this: the web debug toolbar displays at the bottom of the page,
207207
are big, beautiful & explicit, and any configuration cache is automatically rebuilt
208208
whenever needed.
209209

210-
But what about when you deploy to production? We will need to hide those tool and
210+
But what about when you deploy to production? We will need to hide those tools and
211211
optimize for speed!
212212

213213
This is solved by Symfony's *environment* system and there are three: ``dev``, ``prod``
@@ -266,7 +266,7 @@ Platform as a Service (PaaS) deployment systems as well as Docker.
266266
But setting environment variables while developing can be a pain. That's why your
267267
app automatically loads a ``.env`` file, if the ``APP_ENV`` environment variable
268268
isn't set in the environment. The keys in this file then become environment variables
269-
are and read by your app:
269+
and are read by your app:
270270

271271
.. code-block:: bash
272272
@@ -278,7 +278,7 @@ are and read by your app:
278278
279279
At first, the file doesn't contain much. But as your app grows, you'll add more
280280
configuration as you need it. But, actually, it gets much more interesting! Suppose
281-
your app needs database ORM. Let's install the Doctrine ORM:
281+
your app needs a database ORM. Let's install the Doctrine ORM:
282282

283283
.. code-block:: terminal
284284

0 commit comments

Comments
 (0)