1diff --git a/content/posts/2023-04-30-using-data-mode-alpine.md b/content/posts/2023-04-30-using-data-mode-alpine.md
2index d0e76236b7037a897961407ed94e83577b759dfb..f8465ed72820ea9ef6ac8ec56892be06b9ef5827 100644
3--- a/content/posts/2023-04-30-using-data-mode-alpine.md
4+++ b/content/posts/2023-04-30-using-data-mode-alpine.md
5@@ -6,23 +6,23 @@ ---
6
7 # Local testing
8
9-To facilitate iteration and testing of this setup, we can use `qemu` and for the
10-whole setup we will be using two disks: one for mounting the /var folder and
11-another for storing lbu files (more on that later). To create the two images,
12-follow these steps:
13+To make testing easier, we can use `qemu`, which will allow us to test the
14+configuration before going for the real machine. For this setup we will be
15+using two disks: one for mounting the /var folder and another for storing lbu
16+files (more on that later). To create the two images with `qemu` run:
17
18 ```bash
19 qemu-img create -f qcow2 var.cow2 10G
20 qemu-img create -f qcow2 media.cow2 5G
21 ```
22
23-Those images have arbitrary sizes and probably won't even required that much for
24-this setup so feel free to choose another size.
25+Those images have arbitrary sizes and probably we won't even required that much
26+for this setup so feel free to choose pick whatever size you want.
27
28-Once you have created the images go to alpine download page[^1] and grab the
29+Once we have created the images, go to alpine download page[^1] and grab the
30 latest virtual image.
31
32-We all of that we can now start the virtual machine
33+We all of that we can now start the virtual machine, run:
34
35 ```bash
36 qemu-system-x86_64 \
37@@ -36,20 +36,21 @@ -drive file=media.cow2,if=virtio
38 ```
39
40 For more info about what are those parameters head to `qemu` documentation[^2].
41-Just pay attention to the `-boot d` option which will force cdrom to boot first
42-(more on that later as well).
43+Just make sure to add `-boot d` option which will force cdrom to boot first
44+(more on that later).
45
46 # Setting up environment
47
48 Before we can run `setup-alpine` we need to mount a persistent media folder so
49-it can be picked up by the script and used to store the `lbu` files. To do so we
50-need to install some extra package that are not available in the live ISO.
51+it can be used by `lbu` to store backup files. To do so we need to install some
52+extra package that are not available in the live ISO.
53
54-Run `setup-interfaces` to configure interfaces. The default values will do.
55-After that start the networking service `rc-service networking start`. Now we
56-have internet we can setup a repository. You could edit `/etc/apk/repositories`
57-directly but there is handy command for that already `setup-apkrepos`. Run it
58-and pick any option you see fit. I'd go for `f` but `1` also works.
59+First we need to connect to internet. Run `setup-interfaces` to configure
60+interfaces, default values will do. After that start the networking service
61+`rc-service networking start`. Now we should have internet. After that we need
62+to setup a repository. You could edit `/etc/apk/repositories` directly but
63+there is handy command that does that already `setup-apkrepos`. Run it and pick
64+any option you see fit. I'd go for `f` but `1` also works.
65
66 Now we can install some packages required for the remaining of the setup:
67
68@@ -81,49 +82,50 @@ # mouting
69 mount -t ext4 /dev/vdb /media/vdb
70 ```
71
72-To confirm if device is mounted you can run `df -h /media/vdb`, it shows the
73-size and which device is mounted on that folder.
74+To confirm if device is mounted you can run `df -h /media/vdb`, and it should
75+show the size and which device is mounted on that folder.
76
77 # Setting up alpine on data mode
78
79-Now we can run `setup-alpine`. Choose whatever options fits your need up to the
80-point where it asks to choose the device. It may repeat some of the step we
81-already did but it is be fine.
82+Now we can run `setup-alpine`. Choose whatever options fits your need until up
83+to the point where it asks to choose a device.
84
85-When it asks to choose a disks to use enter the name of disk, which, in this
86-particularly setup, is `vda`. Then it will ask to choose how you would like to
87-run alpine[^3], pick `data`.
88+When it asks to choose a disks to use enter the name of the data disk, which,
89+in this particularly setup, is `vda`. Then it will ask to choose how you would
90+like to run alpine[^3], pick `data`.
91
92-Now it will prompt to choose which media device we want to use for storing the
93+Now it will prompt to choose which media device we want to use for storing
94 `lbu` files. By default it should the media folder we mounted in the previous
95-step, if not just enter `vdb`. Select place for cache. Default is fine.
96+step, if not just enter `vdb`. Then select place for cache, default is fine.
97
98-The cache folder is used to store the apk files we come to add. Since it does
99-not have internet access when booting it needs to store those extra package in
100-folder so later it can be restored.
101+The cache folder is also used to store the apk files we come to add. Since it
102+does not have internet access when booting it needs to store those extra
103+package in folder so later it can be restored.
104
105 **Warning**, do not reboot now. We need to use `lbu` to make a backup of all
106-changes we did, otherwise everything will be lost. Take a careful read of the
107-`lbu` documentation[^4], it will provide the necessary information to understand
108-how `lbu` works.
109+changes we did, otherwise everything will be lost on reboot. Take a careful
110+read on the `lbu` documentation[^4], it will provide the necessary information
111+to understand how `lbu` works.
112
113 Run `lbu commit` to backup it. You can check the `apkvol` file stored in the
114-`/media/vdb/`. Now you changes as saved and you are good to reboot.
115+`/media/vdb/`. Now that we have saved our changes, we are good to reboot.
116
117-The live ISO will look for `apkvol` files and try to restore it. That is why it
118-is required the ISO to be the first to boot. There is no boot info store
119-anywhere else since the one device is used to store `lbu` and the other one is
120-mount on `/var` so we use live ISO to boot and restore the state.
121+The `initramfs` of the live ISO will look for `apkvol` files and try to restore
122+it and that is why cdroom is required to be the first thing to boot.
123+
124+We can also notice that there is no boot info stored anywhere else. One device is
125+used to store the `lbu` files and the other one is used ,later after boot, to
126+mount `/var`, so the live iso is required.
127
128 You can check here[^5] how that is possible and here [^6] how we can expand that
129 idea and netboot using the apkvol to boot any machine to specific state.
130
131 # Making changes
132
133-After rebooting your system, you can now log into your fresh installation. You
134+After rebooting your system, you can log into your fresh installation. You
135 can then install a new package, such as vim, using the command `apk add vim`.
136 However, if you reboot the system again, the vim package will be lost and you
137-will need to reinstall it.
138+will need to reinstall it again after boot.
139
140 If you run `lbu status` will show what was changed and in this case
141 `/etc/apk/world`. The world file store all the package you have installed and
142@@ -135,12 +137,11 @@ package and its dependencies.
143
144 # Why /var?
145
146-The /var folder is a directory in Linux that is used to store variable data
147-files as the contents of this folder can change by the OS. This folder contains
148-files that are not critical to the basic operation of the system, but are
149-instead used for tasks such as logging, spooling, and caching. For example
150-postgresql store all its data on the var folder allowing us to use a database on
151-data mode and still have its data persistent between boots.
152+The `/var` folder contains files that are not critical to the basic operation of the
153+system, but are instead used for tasks such as logging, spooling, and caching.
154+For example postgresql store all its data on the var folder, and by mouting the
155+var folder into a persistent file system it allows us to use a database os
156+running on a tmpfs and still have its data persistent between boots.
157
158 # In conclusion
159