diff --git a/documentation/en/hardware-mining.md b/documentation/en/hardware-mining.md
index 5578f7d62..a7c410184 100644
--- a/documentation/en/hardware-mining.md
+++ b/documentation/en/hardware-mining.md
@@ -16,7 +16,7 @@ The setup below is a minimal example for sealing 32 GiB sectors on Lotus:
 
 Note that 1GB sectors don't require as high of specs, but are likely to be removed as we improve the performance of 32GB sector sealing.
 
-AMD CPU's are **highly recommended**, because of the `Intel SHA Extensions` instruction set that is available there since the `Zen` microarchitecture. Hence, AMD CPU's seem to perform much better on the testnet than other CPU's. Contrary to what the name implies, this extended instruction set is not available on recent Intel desktop/server chips. 
+AMD CPU's are __highly recommended__, because of the `Intel SHA Extensions` instruction set that is available there since the `Zen` microarchitecture. Hence, AMD CPU's seem to perform much better on the testnet than other CPU's. Contrary to what the name implies, this extended instruction set is not available on recent Intel desktop/server chips. 
 
 ## Testnet discoveries
 
diff --git a/documentation/en/mining-lotus-seal-worker.md b/documentation/en/mining-lotus-seal-worker.md
index 6cd7b2c7a..aba115661 100644
--- a/documentation/en/mining-lotus-seal-worker.md
+++ b/documentation/en/mining-lotus-seal-worker.md
@@ -72,7 +72,7 @@ Worker 1, host othercomputer
 ### Running locally for manually managing process priority
 
 You can also run the **Lotus Seal Worker** on the same machine as your **Lotus Storage Miner**, so you can manually manage the process priority.
-To do so you have to first **disable all seal task types** in the miner config. This is important to prevent conflicts between the two processes.
+To do so you have to first __disable all seal task types__ in the miner config. This is important to prevent conflicts between the two processes.
 
 You can then run the storage miner on your local-loopback interface;