From 9c9c869023f8ecc5e8af3067171dd84bff5e8013 Mon Sep 17 00:00:00 2001 From: Alexandre Aubin Date: Tue, 5 Sep 2023 13:30:12 +0200 Subject: [PATCH] Update pages/05.community/20.faq/faq.md Co-authored-by: tituspijean --- pages/05.community/20.faq/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/05.community/20.faq/faq.md b/pages/05.community/20.faq/faq.md index 7aabad0a..fe8ea4a2 100644 --- a/pages/05.community/20.faq/faq.md +++ b/pages/05.community/20.faq/faq.md @@ -88,7 +88,7 @@ If this does not convince you, there are other projects running on other distrib People have been tempted to compare YunoHost packages to traditional package managers (such as Debian's `.deb`), which hold a different purpose. Traditional package managers are meant to install low-level purpose of installing files, commands, programs and services on the system. It is often your duty to configure them properly, simply because there is no standard server setup. Typically, web apps requires a lot of configuration because they rely on a web server and a database (and the single sign-on). -YunoHost manipulates high-level abstractions (apps, domains, users...) and defines a standard setup (NGINX, Postfix, Metronome, SSOwat...) and, because of this, can handle the configuration for the user. +YunoHost manages high-level abstractions (apps, domains, users...) and defines a standard setup (NGINX, Postfix, Metronome, SSOwat...) and, because of this, can handle the configuration for the user. #### When will [this feature] be implemented? Why isn't [that app] packaged yet? I cannot believe you do not do [this] yet!