minor #388 [Turbo] Moving repeatable Broadcast changelog to 2.3 (weav…

…erryan)

This PR was merged into the 2.x branch.

Discussion
----------

[Turbo] Moving repeatable Broadcast changelog to 2.3

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| Tickets       | None
| License       | MIT

CHANGELOG tweak needed for #387

Commits
-------

6defd83 [Turbo] Moving repeatable Broadcast changelog to 2.3

src/Turbo/CHANGELOG.md

@@ -1,9 +1,12 @@
 # CHANGELOG
 
+## 2.3
+
+-   The `Broadcast` attribute can now be repeated, this is convenient to render several Turbo Streams Twig templates for the same change
+
 ## 2.2
 
 -   The topics defined in the `Broadcast` attribute now support expression language when prefixed with `@=`.
--   The `Broadcast` attribute can now be repeated, this is convenient to render several Turbo Streams Twig templates for the same change
 
 ## 2.1
 

src/Turbo/Resources/doc/index.rst

@@ -620,10 +620,10 @@ The ``Broadcast`` attribute comes with a set of handy options:
    is derived from the FQCN of the entity and from its id
 -  ``template`` (``string``): Twig template to render (see above)
 
-The ``Broadcast`` attribute can be repeated. This is convenient to
-to render several templates associated with their own topics for the
-same change (e.g. the same data is rendered in different way in the
-list and in the detail pages).
+The ``Broadcast`` attribute can be repeated (e.g. you can have multiple
+`#[Broadcast]`. This is convenient to to render several templates associated with
+their own topics for the same change (e.g. the same data is rendered in different
+way in the list and in the detail pages).
 
 Options are transport-specific. When using Mercure, some extra options
 are supported: