Fix lnks

src/development.md

@@ -7,7 +7,7 @@ To enhance this openness, automated builds, testing and packaging are defined
 as part of the repositories - improving te robustness of the code base at every
 stage.
 
-![](/1.png)
+![](https://docs.openprivacy.ca/cwtch-security-handbook/1.png)
 
 While individual tests aren't perfect, and all processes have gaps, we should be
 committed to make it as easy as possible to contribute to Cwtch while also

src/overview.md

@@ -6,7 +6,7 @@ ecosystem, to document the known risks and mitigations, and to enable
 discussion about improvements and updates to Cwtch secure development
 processes.
 
-![](/2.png)
+![](https://docs.openprivacy.ca/cwtch-security-handbook/2.png)
 
 
 ## History

src/risk.md

@@ -6,7 +6,7 @@ and to conduct large scale social network analysis to feed mass surveillance.
 Metadata resistant tools are in their infancy and research into the construction
 and user experience of such tools is lacking.
 
-![](/4.png)
+![](https://docs.openprivacy.ca/cwtch-security-handbook/4.png)
 
 Cwtch was originally concieved an extension of the metadata resistant protocol
 Ricochet to support asynchronous, multi-peer group communications through the 

src/ui.md

@@ -3,7 +3,7 @@
 The UI is built on [therecipe/qt](https://github.com/therecipe/qt) which
  links in Qt libraries.
  
-![](/3.png)
+![](https://docs.openprivacy.ca/cwtch-security-handbook/3.png)
 
 # Known Risks