Minor reword

javiereguiluz · javiereguiluz · commit 331084d6cf13 · 2018-06-29T08:57:17.000+02:00
diff --git a/testing.rst b/testing.rst
@@ -509,15 +509,13 @@ Accessing the Container
 ~~~~~~~~~~~~~~~~~~~~~~~
 
 .. versionadded:: 4.1
-
     The ``self::$container`` property was introduced in Symfony 4.1.
 
 It's highly recommended that a functional test only tests the response. But
-under certain very rare circumstances, you might want to access some internal
-objects to write assertions. In such cases, you can access your services via
-a special property on the test class. Because services are private by default,
-this property holds a special container, which allows fetching public and all
-non-removed private services::
+under certain very rare circumstances, you might want to access some services
+to write assertions. Given that services are private by default, test classes
+define a property that stores a special container created by Symfony which
+allows fetching both public and all non-removed private services::
 
     // gives access to the same services used in your test, unless you're using
     // $client->insulate() or using real HTTP requests to test your application
@@ -529,8 +527,8 @@ command.
 .. tip::
 
     The special container that gives access to private services exists only in
-    the ``test`` environment and is itself a service that you can accessed from
-    the real container using the ``test.service_container`` id.
+    the ``test`` environment and is itself a service that you can get from the
+    real container using the ``test.service_container`` id.
 
 .. tip::
 
