Fixed some typos reported by @henrikbjorn

Author: javiereguiluz

best_practices/business-logic.rst

@@ -164,7 +164,7 @@ Using a Persistence Layer
 Symfony is an HTTP framework that only cares about generating an HTTP response
 for each HTTP request. That's why Symfony doesn't provide a way to talk to
 a persistence layer (e.g. database, external API). You can choose whatever
-library of strategy you want for this.
+library or strategy you want for this.
 
 In practice, many Symfony applications rely on the independent
 `Doctrine project`_ to define their model using entities and repositories.

best_practices/templates.rst

@@ -40,7 +40,7 @@ drastically simplifies their logical names:
 ==================================================  ==================================
 Templates stored inside bundles                     Templates stored in ``app/``
 ==================================================  ==================================
-``AcmeDemoBunde:Default:index.html.twig``           ``default/index.html.twig``
+``AcmeDemoBundle:Default:index.html.twig``          ``default/index.html.twig``
 ``::layout.html.twig``                              ``layout.html.twig``
 ``AcmeDemoBundle::index.html.twig``                 ``index.html.twig``
 ``AcmeDemoBundle:Default:subdir/index.html.twig``   ``default/subdir/index.html.twig``