symfony · javiereguiluz · Jan 10, 2019 · Jan 10, 2019
diff --git a/_images/components/messenger/overview.png b/_images/components/messenger/overview.png
diff --git a/_images/components/messenger/overview.svg b/_images/components/messenger/overview.svg
diff --git a/_images/components/serializer/serializer_workflow.png b/_images/components/serializer/serializer_workflow.png
diff --git a/_images/components/serializer/serializer_workflow.svg b/_images/components/serializer/serializer_workflow.svg
diff --git a/_images/http/request-flow.png b/_images/http/request-flow.png
diff --git a/_images/http/request-flow.svg b/_images/http/request-flow.svg
diff --git a/_images/sources/components/messenger/overview.dia b/_images/sources/components/messenger/overview.dia
diff --git a/_images/sources/components/serializer/serializer_workflow.dia b/_images/sources/components/serializer/serializer_workflow.dia
diff --git a/_images/sources/http/request-flow.dia b/_images/sources/http/request-flow.dia
diff --git a/components/messenger.rst b/components/messenger.rst
@@ -31,7 +31,9 @@ Alternatively, you can clone the `<https://github.com/symfony/messenger>`_ repos
 Concepts
 --------
 
-.. image:: /_images/components/messenger/overview.png
+.. raw:: html
+
+    <object data="../_images/components/messenger/overview.svg" type="image/svg+xml"></object>
 
 **Sender**:
    Responsible for serializing and sending messages to *something*. This

diff --git a/components/serializer.rst b/components/serializer.rst
@@ -10,7 +10,9 @@ The Serializer Component
 
 In order to do so, the Serializer component follows the following schema.
 
-.. image:: /_images/components/serializer/serializer_workflow.png
+.. raw:: html
+
+    <object data="../_images/components/serializer/serializer_workflow.svg" type="image/svg+xml"></object>
 
 As you can see in the picture above, an array is used as an intermediary between
 objects and serialized contents. This way, encoders will only deal with turning

diff --git a/introduction/from_flat_php_to_symfony2.rst b/introduction/from_flat_php_to_symfony2.rst
@@ -664,9 +664,9 @@ object are sent back to the client.
 
 It's a beautiful thing.
 
-.. figure:: /_images/http/request-flow.png
-   :align: center
-   :alt: Symfony request flow
+.. raw:: html
+
+    <object data="../_images/http/request-flow.svg" type="image/svg+xml"></object>
 
 Where Symfony Delivers
 ----------------------

diff --git a/introduction/http_fundamentals.rst b/introduction/http_fundamentals.rst
@@ -361,12 +361,12 @@ to do:
 
 .. _request-flow-figure:
 
-.. figure:: /_images/http/request-flow.png
-   :align: center
-   :alt: Symfony request flow
+.. raw:: html
+
+    <object data="../_images/http/request-flow.svg" type="image/svg+xml"></object>
 
-   Incoming requests are interpreted by the :doc:`Routing component </routing>` and
-   passed to PHP functions that return ``Response`` objects.
+Incoming requests are interpreted by the :doc:`Routing component </routing>` and
+passed to PHP functions that return ``Response`` objects.
 
 This may not make sense yet, but as you keep reading, you'll learn about :doc:`routes </routing>`
 and :doc:`controllers </controller>`: the two fundamental parts to creating a page.