docs: replace weird symbols on wiki

docs/wiki/Simnet-Testing.md

@@ -44,13 +44,13 @@ When done with a harness, use `./quit` to shutdown all the processes and tmux se
 For convenience, the harnesses may continually mine blocks with the `watch` command. To generate a new Bitcoin block every 5 seconds:
 
 ```sh
-~  dextest  btc  harness-ctl  $  watch -n 25 ./mine-alpha 1
+~/dextest/btc/harness-ctl $ watch -n 25 ./mine-alpha 1
 ```
 
 Decred is similar, but under the `dcr` folder:
 
 ```sh
-~  dextest  dcr  harness-ctl  $  watch -n 30 ./mine-alpha 1
+~/dextest/dcr/harness-ctl $ watch -n 30 ./mine-alpha 1
 ```
 
 **WARNING**: Decred's harness can't mine indefinitely so stop the watch when you have completed your current test.  The harness config has a ticket buyer, but not enough tickets are purchased on a long enough timeline because automatic buying is not allowed before a price change.  This needs tweaking.
@@ -62,7 +62,7 @@ Decred is similar, but under the `dcr` folder:
 There is a dcrdex harness that will set up everything for you, although with a very short contract lock time set of 1 min maker and 30 sec taker.
 
 ```sh
-~  [repo root]  dex  testing  dcrdex  $  ./harness.sh
+/[repo root]/dex/testing/dcrdex $ ./harness.sh
 ```
 
 To setup the dcrdex server manually, and with the regular contract lock times, follow the steps in the following subsections.
@@ -179,7 +179,7 @@ enabled. This should redirect to <http://127.0.0.3:5758/register.>
 5. If auto-mining is not setup, mine a few blocks on Decred simnet. How many depends on the `regfeeconfirms` setting used with `dcrdex.
 
     ```none
-    ~  dextest  dcr  harness-ctl  $  ./mine-alpha 1 # mine one block
+    ~/dextest/dcr/harness-ctl $ ./mine-alpha 1 # mine one block
     ```
 
 6. Place a couple orders that match.
@@ -193,15 +193,15 @@ If this is the first time starting `dexc`, the application must be initialized w
 For example, initializing with the password "asdf":
 
 ```none
-$   ./dexcctl --simnet -u u -P p init
+$  ./dexcctl --simnet -u u -P p init
 Set new app password:  <asdf>
 app initialized
 ```
 
 Setting up a Decred wallet (DCR coin ID is 42):
 
 ```none
-$   ./dexcctl --simnet -u u -P p newwallet 42 ~/dextest/dcr/alpha/alpha.conf '{"account":"default"}'
+$  ./dexcctl --simnet -u u -P p newwallet 42 ~/dextest/dcr/alpha/alpha.conf '{"account":"default"}'
 App password:       <asdf>
 Wallet password:    <abc>
 dcr wallet created and unlocked
@@ -217,7 +217,7 @@ The `dexc` console should log something similar to the following:
 Setting up a Bitcoin wallet (BT coin ID is 0):
 
 ```none
-$   ./dexcctl --simnet -u u -P p newwallet 0 ~/dextest/btc/alpha/alpha.conf '{"walletname":"gamma"}'
+$  ./dexcctl --simnet -u u -P p newwallet 0 ~/dextest/btc/alpha/alpha.conf '{"walletname":"gamma"}'
 App password:      <asdf>
 Wallet password:   <abc>
 btc wallet created and unlocked
@@ -228,7 +228,7 @@ Note that Bitcoin's coin ID is always 0, even on testnet and simnet. Do not use
 Now both Decred and Bitcoin wallets are available. Query their status with the `wallets` command:
 
 ```none
-$   ./dexcctl --simnet -u u -P p wallets
+$  ./dexcctl --simnet -u u -P p wallets
 [
   {
     "symbol": "dcr",
@@ -258,7 +258,7 @@ $   ./dexcctl --simnet -u u -P p wallets
 Now that a Decred wallet is configured, you can register with a DEX server.  First query for the registration fee with the `getfee` command:
 
 ```none
-$   ./dexcctl --simnet -u u -P p getfee "http://127.0.0.1:7232" ~/.dcrdex/rpc.cert 
+$  ./dexcctl --simnet -u u -P p getfee "http://127.0.0.1:7232" ~/.dcrdex/rpc.cert 
 {
   "fee": 100000000
 }
@@ -269,7 +269,7 @@ Note that the fee is in atoms, the smallest unit of value in Decred, where 1 DCR
 If the fee is acceptable, use the `register` command to pay the fee:
 
 ```none
-$   ./dexcctl --simnet -u u -P p register "http://127.0.0.1:7232" 100000000 ~/.dcrdex/rpc.cert 
+$  ./dexcctl --simnet -u u -P p register "http://127.0.0.1:7232" 100000000 ~/.dcrdex/rpc.cert 
 App password:    <asdf>
 the DEX fee of 100000000 has been paid
 ```