From f9431270ee08733672063211770a6c2dc6ed3c0e Mon Sep 17 00:00:00 2001
From: Joel Schulz-Andres <joelsa@users.noreply.github.com>
Date: Wed, 7 Aug 2024 12:01:02 +0200
Subject: [PATCH] Fix image too wide

---
 src/docs/tools/cargo-embed.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/docs/tools/cargo-embed.md b/src/docs/tools/cargo-embed.md
index 9a0214b..8af7731 100644
--- a/src/docs/tools/cargo-embed.md
+++ b/src/docs/tools/cargo-embed.md
@@ -334,7 +334,7 @@ tabs = [
 
 This screenshot shows how it can be used with a single socket. The logger is configured to redirect `log::trace!()` to channel 1, which is then sent to the real time plotting app.
 
-![Real time plotting rtt data via tcp](/images/cargo-embed-tcp-socket.png)
+<img src="/images/cargo-embed-tcp-socket.png" alt="Real time plotting rtt data via tcp" width="100%"/>
 
 Note that the raw bytes are send over the socket, so no timestamps are added, nor any parsing or line splitting is done. You have all the flexibility to do this yourself in the tcp endpoint.