diff --git a/content/docs/rfcs/37/README.md b/content/docs/rfcs/37/README.md
index f9e28234f..595b235d2 100644
--- a/content/docs/rfcs/37/README.md
+++ b/content/docs/rfcs/37/README.md
@@ -90,7 +90,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.
 
-![](./N11M.png)
+![](../../../../rfcs/37/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, 
@@ -125,7 +125,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.
 
-![](./NM.png)
+![](../../../../rfcs/37/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. 
diff --git a/static/rfcs/37/N11M.png b/static/rfcs/37/N11M.png
new file mode 100644
index 000000000..bc28d58ee
Binary files /dev/null and b/static/rfcs/37/N11M.png differ
diff --git a/static/rfcs/37/NM.png b/static/rfcs/37/NM.png
new file mode 100644
index 000000000..b445d3d7c
Binary files /dev/null and b/static/rfcs/37/NM.png differ