manual: fixing parsing #70
| @@ -743,18 +743,18 @@ To learn more about this process, [watch this great video](https://youtu.be/axvK | ||||
| If you've already done an SSH connection on your computer, the issue is most probably that the "host key has just been changed". To fix this, try one of those two solutions: | ||||
|  | ||||
| * Linux and MAC:  | ||||
|   * ``` | ||||
|     ``` | ||||
|     sudo rm ~/.ssh/known_hosts | ||||
|     ``` | ||||
| * Windows:  | ||||
|   * ``` | ||||
|     ``` | ||||
|     rm ~/.ssh/known_hosts | ||||
|     ``` | ||||
|  | ||||
| To be more specific, you can remove the probematic host: | ||||
|  | ||||
| * Windows, Linux and MAC:  | ||||
|   * ``` | ||||
|     ``` | ||||
|     ssh-keygen -R <host> | ||||
|     ``` | ||||
|  | ||||
| @@ -2074,7 +2074,7 @@ There can be many different fixes for this error. Here are some troubleshooting | ||||
|   * [Flash the RAID controller](https://fohdeesha.com/docs/perc.html) (i.e. crossflashing), OR; | ||||
|   * Change the controller to a Dell H310 controller (for Dell servers) | ||||
| * Try the command **badblocks** (replace **sda** with your specific disk). Note that this command will delete all the data on the disk | ||||
|   * ``` | ||||
|     ``` | ||||
|     sudo badblocks -svw -b 512 -t 0x00 /dev/sda | ||||
|     ``` | ||||
|  | ||||
| @@ -2094,7 +2094,7 @@ Anyone experiencing frequently this issue where Z-OS sometimes detects an SSD as | ||||
|  | ||||
| * Boot a Ubuntu Linux live USB | ||||
| * Install **gnome-disks** if it isn't already installed: | ||||
|   * ``` | ||||
|     ``` | ||||
|     sudo apt install gnome-disks | ||||
|     ``` | ||||
| * Open the application launcher and search for **Disks** | ||||
| @@ -2161,15 +2161,13 @@ Many different reasons can cause this issue. When you get that error, sometimes | ||||
|  | ||||
| * Fix 1: | ||||
|   * Force the wiping of the disk: | ||||
|     * ``` | ||||
|       ``` | ||||
|       sudo wipefs -af /dev/sda | ||||
|       ``` | ||||
| * Fix 2: | ||||
|   * Unmount the disk then wipe it: | ||||
|     * ``` | ||||
|       sudo umount /dev/sda | ||||
|       ``` | ||||
|     * ``` | ||||
|       sudo umount /dev/sda | ||||
|       sudo wipefs -a /dev/sda | ||||
|       ``` | ||||
|  | ||||
|   | ||||
| @@ -36,15 +36,15 @@ TFT lives on 4 different chains: TFChain, Stellar chain, Ethereum chain and Bina | ||||
| The TFT contract address on different chains are the following: | ||||
|  | ||||
| - [TFT Contract address on Stellar](https://stellarchain.io/assets/TFT-GBOVQKJYHXRR3DX6NOX2RRYFRCUMSADGDESTDNBDS6CDVLGVESRTAC47) | ||||
|   - ``` | ||||
|     ``` | ||||
|     TFT-GBOVQKJYHXRR3DX6NOX2RRYFRCUMSADGDESTDNBDS6CDVLGVESRTAC47 | ||||
|     ``` | ||||
| - [TFT Contract address on Ethereum](https://etherscan.io/token/0x395E925834996e558bdeC77CD648435d620AfB5b) | ||||
|     - ``` | ||||
|       ``` | ||||
|       0x395E925834996e558bdeC77CD648435d620AfB5b | ||||
|       ``` | ||||
| - [TFT Contract address on BSC](https://bscscan.com/address/0x8f0FB159380176D324542b3a7933F0C2Fd0c2bbf) | ||||
|   - ``` | ||||
|     ``` | ||||
|     0x8f0FB159380176D324542b3a7933F0C2Fd0c2bbf | ||||
|     ``` | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user