From e891b587ee84189317c4d8b3ab1d891e6ffb1496 Mon Sep 17 00:00:00 2001 From: Dan Patrick Date: Tue, 1 Nov 2011 20:53:01 -0500 Subject: [PATCH] Substituted word service for scope. --- cookbook/service_container/scopes.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cookbook/service_container/scopes.rst b/cookbook/service_container/scopes.rst index b2cfbafbabc..e89aba27c0f 100644 --- a/cookbook/service_container/scopes.rst +++ b/cookbook/service_container/scopes.rst @@ -108,7 +108,7 @@ Using a Service from a narrower Scope If your service depends on a scoped service, the best solution is to put it in the same scope (or a narrower one). Usually, this means putting your -new service in the `request` service. +new service in the `request` scope. But this is not always possible (for instance, a twig extension must be in the `container` scope as the Twig environment needs it as a dependency).