Bundle names should not be placed in literals

javiereguiluz · weaverryan · commit e00466139d17 · 2014-02-26T15:45:21.000-05:00
diff --git a/quick_tour/the_architecture.rst b/quick_tour/the_architecture.rst
@@ -259,7 +259,7 @@ Extending Bundles
 
 If you follow these conventions, then you can use :doc:`bundle inheritance</cookbook/bundles/inheritance>`
 to "override" files, controllers or templates. For example, you can create
-a bundle - ``AcmeNewBundle`` - and specify that it overrides AcmeDemoBundle.
+a bundle - AcmeNewBundle - and specify that it overrides AcmeDemoBundle.
 When Symfony loads the ``AcmeDemoBundle:Welcome:index`` controller, it will
 first look for the ``WelcomeController`` class in AcmeNewBundle and, if
 it doesn't exist, then look inside AcmeDemoBundle. This means that one bundle
diff --git a/quick_tour/the_big_picture.rst b/quick_tour/the_big_picture.rst
@@ -293,7 +293,7 @@ have seen so far. All the code you write for your application is organized in
 bundles. In Symfony2 speak, a bundle is a structured set of files (PHP files,
 stylesheets, JavaScripts, images, ...) that implements a single feature (a
 blog, a forum, ...) and which can be easily shared with other developers. As
-of now, you have manipulated one bundle, ``AcmeDemoBundle``. You will learn
+of now, you have manipulated one bundle, AcmeDemoBundle. You will learn
 more about bundles in the :doc:`last part of this tutorial</quick_tour/the_architecture>`.
 
 .. _quick-tour-big-picture-environments:
