Skip to content

Commit 2afd292

Browse files
committed
Revert and fix some changes
1 parent 46af801 commit 2afd292

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

cookbook/doctrine/multiple_entity_managers.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -151,8 +151,8 @@ The following configuration code shows how you can configure two entity managers
151151
152152
In this case, you've defined two entity managers and called them ``default``
153153
and ``customer``. The ``default`` entity manager manages entities in the
154-
AcmeDemoBundle and AcmeStoreBundle, while the ``customer`` entity
155-
manager manages entities in the AcmeCustomerBundle. You've also defined
154+
``AcmeDemoBundle`` and ``AcmeStoreBundle``, while the ``customer`` entity
155+
manager manages entities in the ``AcmeCustomerBundle``. You've also defined
156156
two connections, one for each entity manager.
157157

158158
.. note::

quick_tour/the_architecture.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@ Extending Bundles
269269

270270
If you follow these conventions, then you can use :doc:`bundle inheritance</cookbook/bundles/inheritance>`
271271
to "override" files, controllers or templates. For example, you can create
272-
a bundle - AcmeNewBundle - and specify that it overrides AcmeDemoBundle.
272+
a bundle - ``AcmeNewBundle`` - and specify that it overrides AcmeDemoBundle.
273273
When Symfony loads the ``AcmeDemoBundle:Welcome:index`` controller, it will
274274
first look for the ``WelcomeController`` class in AcmeNewBundle and, if
275275
it doesn't exist, then look inside AcmeDemoBundle. This means that one bundle

0 commit comments

Comments
 (0)