@@ -144,18 +144,18 @@ at a regular interval.
144144
145145.. caution ::
146146
147- When you create a message with swiftmailer , it generate a Swift_Message
148- class. If the swiftmailer service is lazy loaded, it generate instead a
149- proxy class named Swift_Message_<someRandomCharacters>.
147+ When you create a message with SwiftMailer , it generates a `` Swift_Message ``
148+ class. If the `` swiftmailer `` service is lazy loaded, it generates instead a
149+ proxy class named `` Swift_Message_<someRandomCharacters> `` .
150150
151- If you use the memory spool, this change is transparent and has no impart .
152- But when you use the filesystem spool, the message class is serialized on
151+ If you use the memory spool, this change is transparent and has no impact .
152+ But when using the filesystem spool, the message class is serialized in
153153 a file with the randomized class name. The problem is that this random
154- class name change on every cache clear. So if you send a mail, then you
154+ class name changes on every cache clear. So if you send a mail and then you
155155 clear the cache, the message will not be unserializable.
156156
157- On the next ``swiftmailer:spool:send `` an error will raise because the
158- class ``Swift_Message_<someRandomCharacters> `` doesn't exist (anymore).
157+ On the next execution of ``swiftmailer:spool:send `` an error will raise because
158+ the class ``Swift_Message_<someRandomCharacters> `` doesn't exist (anymore).
159159
160160 The solutions are either to use the memory spool or to load the
161- swiftmailer service without ``lazy `` option (see :doc: `/service_container/lazy_services `).
161+ `` swiftmailer `` service without ``lazy `` option (see :doc: `/service_container/lazy_services `).
0 commit comments