[talks/lbs] Slight rewording and reformatting of users and groups slides

1 files changed, 4 insertions, 4 deletions

diff --git a/src/talks/linuxgraphy-by-strabo/index.md b/src/talks/linuxgraphy-by-strabo/index.md
index 0308f51..12b9e6c 100644
--- a/src/talks/linuxgraphy-by-strabo/index.md
+++ b/src/talks/linuxgraphy-by-strabo/index.md
@@ -388,9 +388,9 @@ The main attributes that every inode has are as follows:
 
 &&lineb3
 
-A user in UNIX is essentially a small collection of data, most important of it being a unique ID (number), a name (string), a group id (number; files created by the user are in that group) and a password.
+A user in UNIX is essentially a small collection of data, most important of it being a **unique ID** (number), a **name** (string), a **group id** (number; files created by the user are in that group) and a **password**.
 
-Groups are also small collections of data, but much simpler, comprised only of a unique ID (number), a name (string) and a list of users that are "in" the group. Their main purpose is to simplify access control.
+Groups are also small collections of data, but much simpler, comprised only of a **unique ID** (number), a **name** (string) and a **list of users** that are "in" the group. Their main purpose is to simplify access control.
 
 User with ID 0 is called root, it is the "system administrator", all actions made by the system itself are done as that user.
 Every user has their own "home" folder (under "/home/USERNAME/", except for root, which is "/root/"), in which they store personal files, as well as user-specific configuration files.
@@ -402,13 +402,13 @@ Every user has their own "home" folder (under "/home/USERNAME/", except for root
 &&slide
 
 - [file permissions](https://en.wikipedia.org/wiki/File_system_permissions): control the freedom of a user to read (navigate for directories), change and execute files  
-  File permissions are split into three sets: what the owner can do, what group members can do and what anyone else can do.
+  File permissions are split into three sets: what the **owner** can do, what **group** members can do and what **anyone else** can do.  
   Each set contains a mix of three permissions: **r**ead, **w**rite and e**x**ecute, and each set stores some combination of them.
   &&lineb1
   Each is represented by a bit in the order above (`101` means you *can* read, *cannot* write, *can* execute) and the overall permissions are often shown as a three digit number or character string.  
   Example: `111101100` will be shown as `754` or `rwxr-xr--`
 
-- link count: the amount of hard links that point to the inode. Every directory inode contains (normally) exactly two: one from the parent and one from itself ("."). A file is only deleted where there are no hard links left to it (or when there is only one for a directory).
+- link count: the amount of hard links that point to the inode. Every directory inode contains (normally) exactly two: one from the parent and one from itself ("."), though the latter isn't added to the count*^[citation ^needed]* . A file is only deleted where there are no hard links left to it.
 
 - User ID of owner, Group ID, file size and timestamps