Fix blog title

Author: gastaldi

_posts/2024-08-19-quarkus-metaprogramming.adoc

@@ -1,9 +1,9 @@
 ---
 layout: post
-title: 'Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance'
+title: "Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance"
 date: 2024-08-19
 tags: gizmo,jandex,jackson,performances
-synopsis: 'Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance'
+synopsis: "Leveraging Quarkus build-time metaprogramming capabilities to improve Jackson's serialization performance"
 author: mariofusco
 ---
 :imagesdir: /assets/images/posts/metaprogramming
@@ -371,4 +371,4 @@ image::f3.png[]
 In fact in this case all the objects serializations, the one of the `Customer` instance returned by the rest endpoint plus all other objects referenced by it, are now performed by the serializers generated during the deployment phase, the ones with the class names terminating in `$quarkusjacksonserializer` and evidenced in purple in this last flamegraph.
 
 .Flamegraph of serialization demonstrating how all the necessary generated serializers are invoked
-image::f4.png[]
+image::f4.png[]