fix comments made by GromNaN

Author: RisingSunLight42

quick_tour/the_architecture.rst

@@ -191,7 +191,7 @@ After creating just *one* file, you can use this immediately:
     {# Will print something like "Hey Symfony!" #}
     <h1>{{ name|greet }}</h1>
 
-How does this work? Symfony notices that your class uses Twig attributes
+How does this work? Symfony notices that your class uses a Twig attribute
 and so *automatically* registers it as a Twig extension. This is called autoconfiguration,
 and it works for *many* many things. Create a class and then extend a base class
 (or implement an interface). Symfony takes care of the rest.

templates.rst

@@ -1555,7 +1555,9 @@ as currency:
 
 .. _templates-twig-filter-attribute:
 
-Create a class and fill in the logic::
+Create a class with a method that contains the filter logic, then add
+the `#[AsTwigFilter]` attribute to define the name and options of
+the Twig filter::
 
     // src/Twig/AppExtension.php
     namespace App\Twig;
@@ -1577,7 +1579,7 @@ Create a class and fill in the logic::
 .. _templates-twig-function-attribute:
 
 If you want to create a function instead of a filter, use the
-``AsTwigFunction`` attribute::
+``#[AsTwigFunction]`` attribute::
 
     // src/Twig/AppExtension.php
     namespace App\Twig;
@@ -1601,7 +1603,8 @@ 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.
-    Previously, you had to use the ``getFilters()`` and ``getFunctions()`` methods.
+    Previously, you had to extend the `AbstractExtension` class, and override the 
+    ``getFilters()`` and ``getFunctions()`` methods.
 
 Register an Extension as a Service
 ..................................
@@ -1626,10 +1629,11 @@ this command to confirm that your new filter was successfully registered:
 Creating Lazy-Loaded Twig Extensions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Including the code of the custom filters/functions in the Twig extension class
-is the simplest way to create extensions. However, Twig must initialize all
-extensions before rendering any template, even if the template doesn't use an
-extension. Note that if you use attributes, this part is not needed.
+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.
 
 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