feat: use more of the wiki-style

1 files changed, 3 insertions, 3 deletions

diff --git a/blog/2022-04-17.md b/blog/2022-04-17.md
index b7c1150..d6ca637 100644
--- a/blog/2022-04-17.md
+++ b/blog/2022-04-17.md
@@ -7,7 +7,7 @@ I always wanted to do that, but there was a fear of unknown:
 
 Of course, none of that shit can stop me!
 
-## My CPU is weak :cry:
+# My CPU is weak :cry:
 My laptop has a pretty weak CPU (**Intel i3**) compared to flagship models. My PC has **Intel i5**, so obviously compiling packages on laptop will be even slower. That is definitely gonna be a problem...
 
 But wait, why don't we use **both CPU's** for compilation? :thinking:
@@ -25,12 +25,12 @@ Basically my PC runs a `distccd` server in my **LAN** and my laptop connects to
  - I can setup [ccache](https://wiki.gentoo.org/wiki/Ccache) and share compilation cache within my network, making heavy package updates finish in seconds
 
 
-## What if I'm outside and don't have time for compilation? :scream:
+# What if I'm outside and don't have time for compilation? :scream:
 Actually turns out it's a very hypothetical situation. Most of the time you already have your toolkit installed anyway. It's only annoying if you want to try something new - for that I recommend remote or virtual machines (yes, `docker` still exists).
 
 In any case, if such an urgent situation occurs, **you can just get a binary!** There are also ways to setup your own [binary package server](https://wiki.gentoo.org/wiki/Binary_package_guide).
 
-## Managing portage configuration across workstations :hammer_and_wrench:
+# Managing portage configuration across workstations :hammer_and_wrench:
 [Portage](https://wiki.gentoo.org/wiki/Portage) is **the best** package manager I ever used. The obvious benefit is an ability to split your packages into [sets](https://wiki.gentoo.org/wiki/Package_sets). I can define as many sets as I want, for example here's my `/etc/portage/sets/base`:
 ```bash
 app-admin/doas