Changing some uses of we to you to be in keeping with the usual style

components/config/caching.rst

@@ -27,7 +27,7 @@ the cache can tell if it is still fresh or that its contents should be regenerat
 
     $cachePath = __DIR__.'/cache/appUserMatcher.php';
 
-    // the second argument indicates whether or not we are in debug mode
+    // the second argument indicates whether or not you want to use debug mode
     $userMatcherCache = new ConfigCache($cachePath, true);
 
     if (!$userMatcherCache->isFresh()) {

components/dependency_injection/introduction.rst

@@ -77,7 +77,7 @@ Then you can set the choice of transport in the container:
     $container->register('mailer', 'Mailer')
         ->addArgument('sendmail');
 
-This class is now much more flexible as we have separated the choice of
+This class is now much more flexible as you have separated the choice of
 transport out of the implementation and into the container.
 
 Which mail transport you have chosen may be something other services need to
@@ -185,9 +185,9 @@ Avoiding Your Code Becoming Dependent on the Container
 ------------------------------------------------------
 
 Whilst you can retrieve services from the container directly it is best
-to minimize this. For example, in the ``NewsletterManager`` we injected
+to minimize this. For example, in the ``NewsletterManager`` you injected
 the ``mailer`` service in rather than asking for it from the container.
-We could have injected the container in and retrieved the ``mailer`` service
+You could have injected the container in and retrieved the ``mailer`` service
 from it but it would then be tied to this particular container making it
 difficult to reuse the class elsewhere.
 

components/dependency_injection/tags.rst

@@ -67,9 +67,9 @@ Then, define the chain as a service:
 Define Services with a Custom Tag
 ---------------------------------
 
-Now we want several of the ``\Swift_Transport`` classes to be instantiated
+Now you might want several of the ``\Swift_Transport`` classes to be instantiated
 and added to the chain automatically using the ``addTransport()`` method.
-As an example we add the following transports as services:
+For example you may add the following transports as services:
 
 .. configuration-block::
 
@@ -198,7 +198,7 @@ To begin with, change the ``TransportChain`` class::
     }
 
 As you can see, when ``addTransport`` is called, it takes not only a ``Swift_Transport``
-object, but also a string alias for that transport. So, how can we allow
+object, but also a string alias for that transport. So, how can you allow
 each tagged transport service to also supply an alias?
 
 To answer this, change the service declaration:

components/serializer.rst

@@ -1,5 +1,5 @@
 .. index::
-   single: Serializer 
+   single: Serializer
    single: Components; Serializer
 
 The Serializer Component
@@ -15,7 +15,7 @@ simple schema.
 
 As you can see in the picture above, an array is used as a man in
 the middle. This way, Encoders will only deal with turning specific
-**formats** into **arrays** and vice versa. The same way, Normalizers 
+**formats** into **arrays** and vice versa. The same way, Normalizers
 will deal with turning specific **objects** into **arrays** and vice versa.
 
 Serialization is a complicated topic, and while this component may not work
@@ -34,7 +34,7 @@ You can install the component in many different ways:
 Usage
 -----
 
-Using the Serializer component is really simple. We just need to set up
+Using the Serializer component is really simple. You just need to set up
 the :class:`Symfony\\Component\\Serializer\\Serializer` specifying
 which Encoders and Normalizer are going to be available::
 
@@ -84,7 +84,7 @@ exists in our project::
         }
     }
 
-Now, if we want to serialize this object into JSON, we only need to
+Now, if you want to serialize this object into JSON, you only need to
 use the Serializer service created before::
 
     $person = new Acme\Person();
@@ -128,4 +128,4 @@ ability to configure how your objects should be serialize/deserialized via
 annotations (as well as YML, XML and PHP), integration with the Doctrine ORM,
 and handling of other complex cases (e.g. circular references).
 
-.. _`JMSSerializationBundle`: https://github.com/schmittjoh/JMSSerializerBundle
+.. _`JMSSerializationBundle`: https://github.com/schmittjoh/JMSSerializerBundle