diff --git a/content/k3s/latest/en/advanced/_index.md b/content/k3s/latest/en/advanced/_index.md
index b2da9136bbd..ac4f88ed7c9 100644
--- a/content/k3s/latest/en/advanced/_index.md
+++ b/content/k3s/latest/en/advanced/_index.md
@@ -344,7 +344,7 @@ sudo reboot
 
 Standard Raspbian Buster installations do not start with `cgroups` enabled. **K3S** needs `cgroups` to start the systemd service. `cgroups`can be enabled by appending `cgroup_memory=1 cgroup_enable=memory` to `/boot/cmdline.txt`.
 
-## example of /boot/cmdline.txt
+### example of /boot/cmdline.txt
 ```
 console=serial0,115200 console=tty1 root=PARTUUID=58b06195-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait cgroup_memory=1 cgroup_enable=memory
 ```
@@ -417,7 +417,7 @@ reboot
 
 # Enabling Lazy Pulling of eStargz (Experimental)
 
-## What's lazy pulling and eStargz?
+### What's lazy pulling and eStargz?
 
 Pulling images is known as one of the time-consuming steps in the container lifecycle.
 According to [Harter, et al.](https://www.usenix.org/conference/fast16/technical-sessions/presentation/harter),
@@ -436,7 +436,7 @@ Because of the compatibility, eStargz can be pushed to standard container regist
 eStargz is developed based on the [stargz format proposed by Google CRFS project](https://github.com/google/crfs) but comes with practical features including content verification and performance optimization.
 For more details about lazy pulling and eStargz, please refer to [Stargz Snapshotter project repository](https://github.com/containerd/stargz-snapshotter).
 
-## Configure k3s for lazy pulling of eStargz
+### Configure k3s for lazy pulling of eStargz
 
 As shown in the following, `--snapshotter=stargz` option is needed for k3s server and agent.