From 129f044ce7640921a9306679b8d09c388f11d6ec Mon Sep 17 00:00:00 2001
From: Stoppedpuma <58333920+Stoppedpuma@users.noreply.github.com>
Date: Fri, 7 Jun 2024 21:22:04 +0200
Subject: [PATCH] Change ... to etc

---
 docs/concepts.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/concepts.md b/docs/concepts.md
index 503b7a6aa..eb4ccbbc4 100644
--- a/docs/concepts.md
+++ b/docs/concepts.md
@@ -8,7 +8,7 @@ There are over 50000 Linux packages and even more applications. It is simply not
 
 **What to confine and why?**
 
-We take inspiration from the [Android/ChromeOS Security Model](https://arxiv.org/pdf/1904.05572v2.pdf), and we apply it to the Linux world. Modern [Linux security distributions](https://clip-os.org/en/) usually consider an immutable core base image with a carefully selected set of applications. Everything else should be sandboxed. Therefore, this project tries to confine all the *core* applications you will usually find in a Linux system: all systemd services, xwayland, network, bluetooth, your desktop environment... Non-core user applications are out of scope as they should be sandboxed using a dedicated tool (minijail, bubblewrap, toolbox...).
+We take inspiration from the [Android/ChromeOS Security Model](https://arxiv.org/pdf/1904.05572v2.pdf), and we apply it to the Linux world. Modern [Linux security distributions](https://clip-os.org/en/) usually consider an immutable core base image with a carefully selected set of applications. Everything else should be sandboxed. Therefore, this project tries to confine all the *core* applications you will usually find in a Linux system: all systemd services, xwayland, network, bluetooth, your desktop environment, etc. Non-core user applications are out of scope as they should be sandboxed using a dedicated tool (minijail, bubblewrap, toolbox, etc).
 
 This is fundamentally different from how AppArmor is usually used on Linux servers as it is common to only confine the applications that face the internet and/or the users.