Merge pull request 0xPolygon#299 from 0xPolygon/email-obfuscation-fix-test

Email obfuscation fix test

Author: kmurphypolygon

docs/pos/how-to/full-node/full-node-ansible.md

@@ -1,6 +1,5 @@
 
-An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html) is used to
-configure and manage a full node. 
+An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html) is used to configure and manage a full node. 
 
 ## Prerequisites
 
@@ -13,8 +12,7 @@ configure and manage a full node.
 - You will also need to ensure that Go is **not installed** in your environment. You will run into issues if you attempt to set up your full node through Ansible with Go installed as Ansible requires specific packages of Go to be installed.
 - You will also need to make sure that your VM / Machine does not have any previous setups for Polygon Validator or Heimdall or Bor. You will need to delete them as your setup will run into issues.
 
-!!!info
-    Heimdall source enhancements
+!!! info "Heimdall source enhancements"
 
     The latest Heimdall version, **[v1.0.3](https://github.com/maticnetwork/heimdall/releases/tag/v1.0.3)**, contains a few enhancements.
     The delay time between the contract events of different validators **has been increased** to ensure that the mempool doesn't get filled quickly in case of a burst of events that could hamper the chain's progress.
@@ -71,30 +69,44 @@ configure and manage a full node.
 
 - Please **ensure that the value of seeds and bootnodes mentioned below is the same value as mentioned in Heimdall and Bor `config.toml` files**. If not, change the values accordingly.
 
-  - Heimdall seed nodes:
+### Heimdall seed nodes
 
-    ```bash
-    moniker=<enter unique identifier>
+```bash
+moniker=<enter unique identifier>
+```
+Copy the following line and add it to the config file to define the seed node addresses.
 
-    # Mainnet:
-    seeds="1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216:26656,dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80:26656,8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39:26656,e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5:26656,6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164:26656"
+seeds="<!--email_off-->1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216<!--/email_off-->:26656,<!--email_off-->dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80<!--/email_off-->:26656,<!--email_off-->8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39<!--/email_off-->:26656,<!--email_off-->e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5<!--/email_off-->:26656,<!--email_off-->6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164<!--/email_off-->:26656"
 
-    # Testnet:
-    seeds="9df7ae4bf9b996c0e3436ed4cd3050dbc5742a28@43.200.206.40:26656,d9275750bc877b0276c374307f0fd7eae1d71e35@54.216.248.9:26656,1a3258eb2b69b235d4749cf9266a94567d6c0199@52.214.83.78:26656"
-    ```
+**Mainnet**
+
+- 1500161dd491b67fb1ac81868952be49e2509c9f@52.78.36.216:26656
+- dd4a3f1750af5765266231b9d8ac764599921736@3.36.224.80:26656
+- 8ea4f592ad6cc38d7532aff418d1fb97052463af@34.240.245.39:26656
+- e772e1fb8c3492a9570a377a5eafdb1dc53cd778@54.194.245.5:26656
+- 6726b826df45ac8e9afb4bdb2469c7771bd797f1@52.209.21.164:26656
+
+**Testnet**
+
+- 9df7ae4bf9b996c0e3436ed4cd3050dbc5742a28@43.200.206.40:26656
+- d9275750bc877b0276c374307f0fd7eae1d71e35@54.216.248.9:26656
+- 1a3258eb2b69b235d4749cf9266a94567d6c0199@52.214.83.78:26656
 
 !!! tip
-    The following Heimdall seed can be used for both mainnet and Mumbai testnet: `8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:27656`
 
-  - Bootnodes:
+    The following Heimdall seed can be used for both mainnet and Mumbai testnet:
+    
+    8542cd7e6bf9d260fef543bc49e59be5a3fa9074@seed.publicnode.com:27656
 
-    ```bash
-    # Mainnet:
-    bootnode ["enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"]
+### Bootnodes
 
-    # Testnet:
-    bootnodes ["enode://bdcd4786a616a853b8a041f53496d853c68d99d54ff305615cd91c03cd56895e0a7f6e9f35dbf89131044e2114a9a782b792b5661e3aff07faf125a98606a071@43.200.206.40:30303", "enode://209aaf7ed549cf4a5700fd833da25413f80a1248bd3aa7fe2a87203e3f7b236dd729579e5c8df61c97bf508281bae4969d6de76a7393bcbd04a0af70270333b3@54.216.248.9:30303"]
-    ```
+```bash
+  # Mainnet:
+  bootnode ["enode://b8f1cc9c5d4403703fbf377116469667d2b1823c0daf16b7250aa576bacf399e42c3930ccfcb02c5df6879565a2b8931335565f0e8d3f8e72385ecf4a4bf160a@3.36.224.80:30303", "enode://8729e0c825f3d9cad382555f3e46dcff21af323e89025a0e6312df541f4a9e73abfa562d64906f5e59c51fe6f0501b3e61b07979606c56329c020ed739910759@54.194.245.5:30303"]
+
+  # Testnet:
+  bootnodes ["enode://bdcd4786a616a853b8a041f53496d853c68d99d54ff305615cd91c03cd56895e0a7f6e9f35dbf89131044e2114a9a782b792b5661e3aff07faf125a98606a071@43.200.206.40:30303", "enode://209aaf7ed549cf4a5700fd833da25413f80a1248bd3aa7fe2a87203e3f7b236dd729579e5c8df61c97bf508281bae4969d6de76a7393bcbd04a0af70270333b3@54.216.248.9:30303"]
+```
 
 - To check if Heimdall is synced
     - On the remote machine/VM, run `curl localhost:26657/status`
@@ -131,6 +143,6 @@ journalctl -u bor.service -f
 
 ## Ports and Firewall Setup
 
-Open ports 22, 26656 and 30303 to world (0.0.0.0/0) on sentry node firewall.
+Open ports 22, 26656, and 30303 to world (0.0.0.0/0) on sentry node firewall.
 
 You can use VPN to restrict access for port 22 as per your requirement and security guidelines.