Removed html

Author: x1y

content/documentation/General/Overclocking.md

@@ -187,7 +187,7 @@ DTB is in `/boot/dtbs/rockchip/rk3328-rock64.dtb`. CPU clock rates are inside `o
 
 Check the achieved clock speed with `sudo cat /sys/kernel/debug/clk/clk_summary | grep armclk`.
 
-Thanks to [Ayufan](https://github.com/ayufan-rock64)'s work (with their [overclocking recipe](https://github.com/ayufan-rock64/linux-build/blob/master/recipes/overclocking.md)), we know we can add a <strong>1.392GHz</strong> operating point, and a <strong>1.512GHz</strong> operating point (you should ensure you have a large heatsink for this last one). You can do so by adding the following in the `opp_table0` object, after the `opp-1296000000` operating point:
+Thanks to [Ayufan](https://github.com/ayufan-rock64)'s work (with their [overclocking recipe](https://github.com/ayufan-rock64/linux-build/blob/master/recipes/overclocking.md)), we know we can add a **1.392GHz** operating point, and a **1.512GHz** operating point (you should ensure you have a large heatsink for this last one). You can do so by adding the following in the `opp_table0` object, after the `opp-1296000000` operating point:
 
     opp-1392000000 {
             opp-hz = <0x00 0x52f83c00>;

content/documentation/PinePhone_Pro/Software/Multi-distribution_image.md

@@ -17,14 +17,13 @@ This article explains how to install a multiple linux distribution environment o
 
 During the processes of [partitioning](#partitioning) the target device, [building](#building) the image or installing the [bootloader](#u_boot), make sure the variables are properly defined. Each time you open a new terminal window, the values of the variables must be re-set.
 
-<dl><dt><strong>💡 TIP</strong></dt><dd>
-
+{{< admonition type="info" >}}
 _BASE_ is the base directory path on your computer\
 _DEV_ is the device name from the lsblk command\
 _ATTR_ are the attributes of each partition/distribution\
 _SIZE_ is the GiB capacity of each partition/distribution\
 _NameUrl_ is the Key:Value of distribution name and relative URL download address
-</dd></dl>
+{{< /admonition >}}
 
 This guide has been tested with 6 Linux distributions on a 128 GiB microSD card, and following variables:
 
@@ -59,8 +58,7 @@ $ cd ppp
 $ sudo ./spinor-flash-initial-setup.sh
 ```
 
-<dl><dt><strong>💡 TIP</strong></dt><dd>
-
+{{< admonition type="info" >}}
 The multi-boot image _can_ function without rk2aw, but you will need to make sure the correct [bootloader](#uboot) is started by your phone’s SoC.
 
 If you are installing to a microSD card, then either:
@@ -69,7 +67,7 @@ If you are installing to a microSD card, then either:
 2. Hold down the _RE_ button during boot to force the phone to boot from the microSD card by disabling the SPI flash and the eMMC.
 
 If you are installing to the eMMC, make sure the SPI flash is empty.
-</dd></dl>
+{{< /admonition >}}
 
 Further instructions can be found on the [author’s website](https://xff.cz/kernels/bootloaders-2024.04/ppp/rk2aw/INSTALL).
 
@@ -180,12 +178,11 @@ Then, use the following command to install the U-Boot image to the correct locat
 $ sudo dd if=ppp/foss/u-boot-rockchip.bin of=/dev/$DEV bs=512 seek=64 status=progress conv=fsync
 ```
 
-<dl><dt><strong>💡 TIP</strong></dt><dd>
-
+{{< admonition type="info" >}}
 If you are interested in building this U-Boot image yourself, you can download the source code from [xff.cz](https://xff.cz/git/u-boot/tree/?h=ppp-2023.07). However, you will still need a copy of _ppp.tar.gz_ since it contains the U-Boot build configuration file (`ppp/foss/.config`).
 
 Copy this file to the root of your U-Boot source directory, keeping the name `.config`. You can then use `make` to initiate the build process.
-</dd></dl>
+{{< /admonition >}}
 
 ## Build the partitions
 

content/documentation/ROCKPro64/Hardware/Hardware_tweaks.md

@@ -263,12 +263,12 @@ The patch above only pulls in lines from the following firmware file: https://gi
 This code comes with the following license - which is not replicated here because it will fill this wiki with text - see the link here for the license: https://github.com/reMarkable/brcmfmac-firmware/blob/master/LICENCE.
 
 ## Stabilizing the system (underclocking the RAM)
-<dl><dt><strong>⚠️ WARNING</strong></dt><dd>
 
+{{< admonition type="warning" >}}
 As pointed out by CrystalGamma, "normal accesses should simply work, though with higher access latency than necessary (since it uses the same number of cycles as would be necessary for a higher frequency), but I’d be slightly worried about refresh, since it also issues refresh based on number of cycles as would be used for a higher frequency, instead of actual time elapsed". In other words, "the risk is refreshes coming to late, though it’s probably within tolerance with this little of a frequency diff".
 
 To put it simply, the suggested changes to DRAM configuration may actually cause system instability or data corruption under certain circumstances.
-</dd></dl>
+{{< /admonition >}}
 
 By default, it seems that the some RockPro64 devices are not stable. This seems to manifest as gcc segfaulting randomly. Usually, this can be "fixed" by starting the build again and hoping gcc doesn’t crash. If the build finishes or crashes at a different point, this is a good indicator that the system is not stable. The issue seems to be that the RAM is running a little too fast and some bits are getting randomly flipped. Other frequencies are possible, but the highest officially supported frequency below 800MHz is 666MHz, which is still a big step down from the default frequency of 800MHz provided by ManjaroARM. It is also possible to set arbitrary frequencies in u-boot. Frequencies that have been tested with this method are 702MHz and 752MHz. It seems that there is only a slight performance decrease at 752MHz compared to 800MHz.