From 093a453d767cf9d9d8e2d218875b5547643ffb17 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Thu, 15 Feb 2024 14:57:09 -0500
Subject: [PATCH] Update noise-sessions.md

---
 standards/application/noise-sessions.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/standards/application/noise-sessions.md b/standards/application/noise-sessions.md
index f0962d3..9df19be 100644
--- a/standards/application/noise-sessions.md
+++ b/standards/application/noise-sessions.md
@@ -88,7 +88,7 @@ This is achieved through two main supported session management mechanisms that w
 
 In a $N11M$ setting, each party's device shares the same Noise session information used to encrypt and decrypt messages exchanged with the other party.
 
-![](./images/N11M.png)
+![](../../images/N11M.png)
 
 More precisely, once the first Noise session between any of Alice's and Bob's device is instantiated, 
 its session information is securely propagated to all other devices, 
@@ -123,7 +123,7 @@ This session management mechanism is loosely based on the paper ["Multi-Device f
 In a $NM$ setting, we require all of $N$ Alice's devices to have an active Noise session with each of Bob's $M$ devices, 
 for a total of $NM$ concurrently active Noise sessions between Alice and Bob.
 
-![](./images/NM.png)
+![](../../images/NM.png)
 
 A message is sent from the currently-in-use sender's device to all recipent's devices, 
 by properly encrypting and sending it to the content topics of each corresponding active Noise session.