Apply suggestions

Author: RisingSunLight42

quick_tour/the_architecture.rst

@@ -158,7 +158,7 @@ Twig Extension & Autoconfiguration
 
 Thanks to Symfony's service handling, you can *extend* Symfony in many ways, like
 by creating an event subscriber or a security voter for complex authorization
-rules. Let's add a new filter to Twig called ``greet``. How? Create a simple class
+rules. Let's add a new filter to Twig called ``greet``. How? Create a class
 with your logic::
 
     // src/Twig/GreetExtension.php

templates.rst

@@ -1602,7 +1602,7 @@ If you want to create a function instead of a filter, use the
 
 .. versionadded:: 7.3
 
-    Support for the ``#[AsTwigFilter]`` and ``#[AsTwigFunction]`` attributes was introduced in Symfony 7.3.
+    Support for the ``#[AsTwigFilter]``, ``#[AsTwigFunction]`` and ``#[AsTwigTest]`` attributes was introduced in Symfony 7.3.
     Previously, you had to extend the ``AbstractExtension`` class, and override the
     ``getFilters()`` and ``getFunctions()`` methods.
 
@@ -1635,9 +1635,8 @@ Creating Lazy-Loaded Twig Extensions
 
 When using attributes to extend Twig, the services are initialized only when
 the functions or filters are used to render the template. But in case you use the
-classic approach by extending the ``AbstractExtension`` class, Twig initialize all extensions before
-rendering rendering any template, even if the template doesn't use an
-extension.
+classic approach by extending the ``AbstractExtension`` class, Twig initializes all the extensions before
+rendering any template, even if the extension is not used in the template.
 
 If extensions don't define dependencies (i.e. if you don't inject services in
 them) performance is not affected. However, if extensions define lots of complex