From d41bb16074ea0cd7388061ae30a67e6e0e203502 Mon Sep 17 00:00:00 2001
From: Andy Green <andy@warmcat.com>
Date: Wed, 16 Sep 2020 13:02:04 +0100
Subject: [PATCH] docs: force markdown to render correct path

---
 lib/secure-streams/README.md                                | 6 +++---
 .../http-server/minimal-http-server-smp/README.md           | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/lib/secure-streams/README.md b/lib/secure-streams/README.md
index d7bf59881..ca0dfbdb5 100644
--- a/lib/secure-streams/README.md
+++ b/lib/secure-streams/README.md
@@ -13,11 +13,11 @@ creation, but able to be updated from a remote copy.
 
 Both client and server networking can be handled using Secure Streams APIS.
 
-![overview](../doc-assets/ss-operation-modes.png)
+![overview](/doc-assets/ss-operation-modes.png)
 
 ## Secure Streams CLIENT State lifecycle
 
-![overview](../doc-assets/ss-state-flow.png)
+![overview](/doc-assets/ss-state-flow.png)
 
 Secure Streams are created using `lws_ss_create()`, after that they may acquire
 underlying connections, and lose them, but the lifecycle of the Secure Stream
@@ -55,7 +55,7 @@ destroy the handle themselves, in that case the handler should return
 
 ## Secure Streams SERVER State lifecycle
 
-![overview](../doc-assets/ss-state-flow-server.png)
+![overview](/doc-assets/ss-state-flow-server.png)
 
 You can also run servers defined using Secure Streams, the main difference is
 that the user code must assertively create a secure stream of the server type
diff --git a/minimal-examples/http-server/minimal-http-server-smp/README.md b/minimal-examples/http-server/minimal-http-server-smp/README.md
index 6bc0096d3..33471a704 100644
--- a/minimal-examples/http-server/minimal-http-server-smp/README.md
+++ b/minimal-examples/http-server/minimal-http-server-smp/README.md
@@ -4,7 +4,7 @@ Lws supports multithreaded service... build lws with `-DLWS_MAP_SMP=<max number
 default is 1.  If nonzero, some extra pthreads locking is built into lws and it supports multiple
 independent service threads.
 
-![lws-smp-overview](../../doc-assets/lws-smp-ov.png)
+![lws-smp-overview](/doc-assets/lws-smp-ov.png)
 
 When an incoming connection is accepted, it is bound to the pt with the lowest current wsi
 count, to keep the load on the threads balanced.  Only the pt the wsi is bound to can service
@@ -13,7 +13,7 @@ service threads, a wsi can only be service by the pt it is bound to.
 
 The effectiveness of the scalability depends on the load.  Here is an example of roughly what can be expected
 
-![lws-smp-example](../../doc-assets/lws-smp-example.png)
+![lws-smp-example](/doc-assets/lws-smp-example.png)
 
 ## build