Minor typo fixes, and table syntax fixes (#110)

dreamportdev · Jan 19, 2025 · 1016632 · 1016632
1 parent c6d97a8
commit 1016632
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/08_VirtualFileSystem/02_VirtualFileSystem.md b/08_VirtualFileSystem/02_VirtualFileSystem.md
@@ -10,7 +10,7 @@ To keep our design simple, the features of our VFS driver will be:
 
 ## How The VFS Works
 
-The basic concept of a VFS layer is pretty simple, we can see it like a common way to access files/directories across different file systems, it is a layer that sits between the higher level interface to the FS and the low level implementation of the FS driver, as shown in the picture
+The basic concept of a VFS layer is pretty simple, we can see it like a common way to access files/directories across different file systems, it is a layer that sits between the higher level interface to the FS and the low level implementation of the FS driver, as shown in the picture:
 
 ![Where the VFS sits in an OS](/Images/vfs_layer.png)
 

diff --git a/10_Going_Beyond/01_Going_Beyond.md b/10_Going_Beyond/01_Going_Beyond.md
@@ -253,7 +253,7 @@ The Application layer instead are usually the protocols we want to implement, so
 
 When we want to send data, we start from the topmost layer (the application) and go down the whole stack until the network layer adding some extra information on each level. The extra information is the layer header and footer (if needed), so when the data has reached the last level it will have all the technical information for each level. This is described in the picture below.
 
-On the other way a packet received from the network will observe the opposite path, so it will start as a big packet containing headers/footers for each layer, and while it is traversing the stack upwards, at every layer it will have the layer's header stripped, so when it will reach the Application Layer it will be the information we are looking for (you can just look  at the picture from bottom to top.
+On the other way a packet received from the network will observe the opposite path, so it will start as a big packet containing headers/footers for each layer, and while it is traversing the stack upwards, at every layer it will have the layer's header stripped, so when it will reach the Application Layer it will be the information we are looking for (you can just look  at the picture from bottom to top):
 
 ![TCP/IP Layers](/Images/tcpip.png)