Prettified Code!

docs/en/document/level-0/ch07-xray-server.md

@@ -123,7 +123,6 @@ chmod +r ~/xray_cert/xray.key
     In addition, when recording animated images, the script did not include a command to restart `Xray` because `Xray` plans to support the [Certificate Hot Update] function, which means that `Xray` will automatically identify certificate updates and reload certificates without manual restart. After the function is added, I will modify `config.json` appropriately
     to enable this setting and delete the restart command in the script.
     :::
-
     4.  Add [executable] permissions to this file
 
         ```
@@ -179,7 +178,6 @@ First, you can refer to the [official VLESS configuration example](https://githu
    ::: warning
    This location is not the standard log file location of `Xray`. It is placed here to avoid permission issues that cause trouble for new users. Once you are familiar with it, it is recommended to return to the default location: `/var/log/xray/access.log` and `/var/log/xray/error.log`.
    :::
-
    4. Because Xray is used by the nobody user by default, we need to allow other users to have "write" permissions (`*.log` means all files with the suffix `log`, and the efficiency advantage of the `CLI` interface gradually appears at this time)
 
    ```shell
@@ -433,6 +431,7 @@ deb http://deb.debian.org/debian buster-backports main
 If your VPS supports it, you can try the [cloud server dedicated kernel] `linux-image-cloud-amd64`. The advantages are simplicity and low resource usage. The disadvantage is that some students have reported that forced installation on an unsupported system will cause the system to fail to boot (the kernel cannot be recognized).
 
 To avoid the tragedy of being unable to identify, please make sure:
+
 - Take a system snapshot before trying, or
 - You have `vnc` to save the day (and you know how to use it)
 
@@ -476,21 +475,25 @@ If you are not sure whether your VPS supports it, please follow the command in s
 14. Confirm that `BBR` is enabled
 
 If you want to confirm whether `BBR` is enabled correctly, you can use the following command:
+
 ```shell
 lsmod | grep bbr
 ```
 
 This should return the following result:
+
 ```
 tcp_bbr
 ```
 
 If you want to confirm whether the `fq` algorithm is enabled correctly, you can use the following command:
+
 ```shell
 lsmod | grep fq
 ```
 
 This should return the following result:
+
 ```
 sch_fq
 ```