From df009c3f7b60659463963573c8e04e48043a9d56 Mon Sep 17 00:00:00 2001
From: Divlo <contact@divlo.fr>
Date: Thu, 10 Nov 2022 12:31:48 +0100
Subject: [PATCH] fix(posts): update broken link in thream-v1.0.0.md

---
 posts/thream-v1-0-0.md | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/posts/thream-v1-0-0.md b/posts/thream-v1-0-0.md
index 7eb2698..cc47885 100644
--- a/posts/thream-v1-0-0.md
+++ b/posts/thream-v1-0-0.md
@@ -53,12 +53,9 @@ Since the project is mainly developed during free time (mainly on weekends), the
 
 - The **client** part, called **frontend**, what **the user sees on the screen**, such as forms, buttons and all the **graphic elements** with which the user can interact from a browser.
 
-<p className='flex flex-col items-center justify-center'>
-  <img
-    alt='HTTP Communication Schema'
-    src='../public/images/posts/thream-v1-0-0/http-communication.png'
-  />
-</p>
+<span className='flex flex-col items-center justify-center'>
+  ![HTTP Communication Schema](../public/images/posts/thream-v1-0-0/http-communication.png)
+</span>
 
 This design allows the separation between the client and the server, as long as they both structure their communication according to the <abbr title="Representational state transfer">REST</abbr> architectural guidelines, using the <abbr title="Hypertext Transfer Protocol">HTTP</abbr> protocol, they will be able to communicate with each other, which makes it possible to work independently on the backend and on the frontend using different technologies and skills, really useful in teamwork.