fix: Update lists with empty lines in between items

With a new dunbar update, unordered/ordered lists specify a possible
empty line between all list items (instead of being simple aliases for
bulleted/numbered list).

1 files changed, 4 insertions, 3 deletions

diff --git a/src/slides/linuxgraphy-by-strabo/index.du b/src/slides/linuxgraphy-by-strabo/index.du
index a203bbb..1e7dfb1 100644
--- a/src/slides/linuxgraphy-by-strabo/index.du
+++ b/src/slides/linuxgraphy-by-strabo/index.du
@@ -64,6 +64,7 @@
 		1. Shell
 		2. UNIX-style file system
 		2. Kernel
+
 	[$br2]
 
 	3. Linux from the inside
@@ -212,14 +213,14 @@ In the beginning, programming was done mostly by [url https://en.wikipedia.org/w
 .p
 Ignoring [url https://unix.stackexchange.com/questions/14368/difference-between-posix-single-unix-specification-and-open-group-base-specifi/14415 standards] and [url https://unix.stackexchange.com/questions/87686/what-makes-an-operating-system-unix-like specifications], in my opinion, from the point of a user, a UNIX-like OS has the following components:
 
-[$br4]
+[$br2]
 
 .ordered
 1. =[shell]=: A programmable replaceable command-line interpreter, with utilities for managing the whole system and support for pipelines and I/O redirection
 2. =[UNIX-style file system]=: [url https://en.wikipedia.org/wiki/Unix_filesystem Filesystem] as a single rooted tree, objects (nodes) in the file system are [url https://en.wikipedia.org/wiki/Inode inodes] and an inode can be [url https://en.wikipedia.org/wiki/Unix_file_types (at least)] either a regular file, directory or devices. Permissions per users and group.
 3. =[kernel]=: Program that manages all communication and operations between the hardware and software
 
-[$br4]
+[$br2]
 
 .font18 *[For now we'll generally just look over some of the common stuff and go into detail later, while in Linux.]*
 
@@ -518,7 +519,7 @@ All process information is stored in a data structure, called a *[process contro
 Not to be confused with a [url https://en.wikipedia.org/wiki/Printed_circuit_board printed circuit board]!\n
 A PCB's data can be split into three categories:
 
-.ordered
+.numbered
 1. =[Process identification]= - the ID of the process itself, of it's parent process, of it's owner (user), etc.
 2. =[Process state]= - as described, the processor state, etc.\n
    On a context switch, values in registers are put into the stopped PCB and then are loaded from the running PCB.