architecture.md

@@ -220,7 +220,7 @@ The process of migrating one's applications to a different host encompasses:
 Whereas the bulk of our configuration logic is covered in the [configuration schema](#sample-configuration-schema), our reference front-end application does in fact store data.
 The design for its data model to support the desired functionality is as follows, using the crow's foot notation to denote cardinality:
 
-![](https://git.fediversity.eu/Fediversity/meta/raw/branch/panel-data-model/architecture-docs/panel-data-model.svg)
+<img src="https://git.fediversity.eu/Fediversity/meta/raw/branch/panel-data-model/architecture-docs/panel-data-model.svg" alt="" style="max-width:600px;"/>
 
 ### Host architecture
 
@@ -427,7 +427,7 @@ Whereas details of the implementation may need to be decided as the technical ch
         - [Nix-less bootstrap](https://git.fediversity.eu/Fediversity/Fediversity/issues/332)
         - [ensure hosts may update users' deployments](https://git.fediversity.eu/Fediversity/Fediversity/issues/159)
         - [reference front-end decoupled from version of configuration module](https://git.fediversity.eu/Fediversity/Fediversity/issues/304)
-        - [security audit](https://git.fediversity.eu/Fediversity/Fediversity/issues/291)
+        - [security check](https://git.fediversity.eu/Fediversity/Fediversity/issues/291)
     - [Key features improving user experience supported](https://git.fediversity.eu/Fediversity/Fediversity/issues/289):
         - [enqueuing deployment syncs](https://git.fediversity.eu/Fediversity/Fediversity/issues/242)
         - [provide single sign-on](https://git.fediversity.eu/Fediversity/Fediversity/issues/212)