Update firewallexpectation.md

docs/best-practices/firewallexpectation.md

-For a database to successfully be accessed by IICS, it must first accept connections from the IICS Secure Agent. If the database has a firewall associated with it, then any attempt at connecting without altering the firewall will most likely result in an error (and on the IICS side, only providing the vague error message of ‘Connection Refused’).
+# Firewall Expectations
 
-For connection to be successful, the database admin must edit the firewall to allow communications from the Secure Agent through. There are two secure agents running - one for test, and one for production - and each one has a separate IP address. These addresses are listed below.
+For a database to successfully be accessed by IICS, it must first accept connections from the IICS Secure Agent. If the database has a firewall associated with it, then any attempt at connecting without altering the firewall will most likely result in an error (only providing the vague error message of ‘Connection Refused’ within IICS).
 
-test - 3.230.240.5
-prod - 3.19.12.147
+For connection to be successful, the database admin must edit the firewall to allow communications from the Secure Agent through. There are two secure agents running under the label ei.secureagent.wisc.edu - one for the test organization, and one for production - and each one has a separate IP address. These addresses are listed below.
+
+|Organization|IP|
+|:-------|:---------------|
+|test | 3.230.240.5 |
+|production | 3.19.12.147 |
 
 Once the connection in IICS and the firewall rules in the database are set up, they can easily be tested by using the ‘test connection’ button in IICS. If the connection is unsuccessful, it is recommended you double-check the connection properties within IICS, and check the firewall traffic in the database to make sure no connection attempts are being blocked.