01/01: website: services-in-containers: "single view" of the resources.

[Ludovic Courtès]

civodul pushed a commit to branch master
in repository guix-artwork.

commit bf7054bf5d25605a8b961333e76e092ba7be8f01
Author: Ludovic Courtès <address@hidden>
Date:   Fri Apr 14 14:52:09 2017 +0200

    website: services-in-containers: "single view" of the resources.
    
    * website/posts/running-services-in-containers.md (tags): "single view"
    instead of "unique view".  Suggested by Andy Wingo.
---
 website/posts/running-services-in-containers.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/posts/running-services-in-containers.md 
b/website/posts/running-services-in-containers.md
index d8c6a41..b18d133 100644
--- a/website/posts/running-services-in-containers.md
+++ b/website/posts/running-services-in-containers.md
@@ -44,7 +44,7 @@ The operating system side of things is less bright.  Although 
the
 has been well-known in operating system circles for a long time, it
 remains foreign to Unix and GNU/Linux.  Processes run with the full
 authority of their user.  On top of that, until recent changes to the
-Linux kernel, resources were global and there was essentially a unique
+Linux kernel, resources were global and there was essentially a single
 view of the file system, of the process hierarchy, and so on.  So when a
 remote-code-execution vulnerability affects a system service—like
 [in the BitlBee instant messaging gateway 
(CVE-2016-10188)](https://bugs.bitlbee.org/ticket/1281)