Skip to content

Commit a2bcbc4

Browse files
authored
Merge pull request #516 from sajadtorkamani/patch-1
fix small typos
2 parents 901d0e8 + ed228ff commit a2bcbc4

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

docs/index.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ Once your fixtures have been written, load them by executing this command:
6969
.. caution::
7070

7171
By default the ``load`` command **purges the database**, removing all data
72-
from every table. To append your fixtures' data add the ``--append`` option.
72+
from every table. To append your fixtures' data, add the ``--append`` option.
7373

7474
This command looks for all services tagged with ``doctrine.fixture.orm``. If you're
7575
using the `default service configuration`_, any class that implements ``ORMFixtureInterface``
@@ -85,7 +85,7 @@ To see other options for the command, run:
8585
Accessing Services from the Fixtures
8686
------------------------------------
8787

88-
In some cases you may need to access your application's services inside a fixtures
88+
In some cases, you may need to access your application's services inside a fixtures
8989
class. No problem! Your fixtures class is a service, so you can use normal dependency
9090
injection::
9191

@@ -177,8 +177,8 @@ exact same object via its name.
177177
}
178178
179179
The only caveat of using references is that fixtures need to be loaded in a
180-
certain order (in this example, if the ``Group`` fixtures are load before the
181-
``User`` fixtures, you'll see an error). By default Doctrine loads the fixture
180+
certain order (in this example, if the ``Group`` fixtures are loaded before the
181+
``User`` fixtures, you'll see an error). By default, Doctrine loads the fixture
182182
files in alphabetical order, but you can control their order as explained in the
183183
next section.
184184

0 commit comments

Comments
 (0)