From 41a7ac66efd91e3e599c8f40b86d4cb5de3d30f3 Mon Sep 17 00:00:00 2001 From: Valentin Gagarin Date: Wed, 11 Jun 2025 18:04:41 +0200 Subject: [PATCH] polish wording on architecture --- architecture.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/architecture.md b/architecture.md index 160fd88..54c80fc 100644 --- a/architecture.md +++ b/architecture.md @@ -141,14 +141,14 @@ The process of migrating one's applications to a different host encompasses: ### Data model -Whereas the bulk of our configuration logic is covered in the 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: +Whereas the bulk of our configuration logic is covered in the configuration schema, our reference front-end applications will store data. +The data model design for the configuration front-end needed support the desired functionality is as follows, using the crow's foot notation to denote cardinality: ### Host architecture -Whereas the core abstraction in Fediversity is a NixOS configuration module, a more full-fledged example architecture of the web host use-case we aim to support as part of our exploitation would be as follows, where VMs in question run Fediversity to offer our selected applications: +Whereas the core abstraction in Fediversity is a NixOS configuration module, a more full-fledged example architecture of the web host use-case we aim to support as part of our exploitation would be as follows, where virtual machines in question run Fediversity to offer our selected applications: ![](https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/host-architecture.png)