AETHER-2011 (part3)
- Clarity pass on the edge deployment overview
- Fixed issues Ain found (mainly grammar)
- Updated the paired-leaves doc to clarify single-homed nodes
Change-Id: I865cc0934d4b63e513b348355e02aa62a0121aec
diff --git a/edge_deployment/site_planning.rst b/edge_deployment/site_planning.rst
index ad93cb7..9c36a97 100644
--- a/edge_deployment/site_planning.rst
+++ b/edge_deployment/site_planning.rst
@@ -8,9 +8,9 @@
Site Design in Netbox
---------------------
-The Aether project uses Netbox as source of truth, and the automation script uses
-it's API to create input files for Ansible Playbooks which are used to configure
-each site.
+The Aether project uses Netbox as source of truth, and the automation script
+uses the Netbox API to create input files for Ansible Playbooks which are used
+to configure each site.
Once the hardware has been ordered, the installation can be planned. The
following information needs to be added to `NetBox
@@ -268,9 +268,9 @@
Rackmount of Equipment
----------------------
-Most of the Pronto equipment has a 19" rackmount form factor.
-
-Guidelines for mounting this equipment:
+Most of the switch and server equipment used for Aether is available in the 19"
+rackmount form factor, but care needs to be taken in mounting this equipment to
+ensure proper airflow. Please follow these guidelines:
- The EdgeCore Wedge Switches have a front-to-back (aka "port-to-power") fan
configuration, so hot air exhaust is out the back of the switch near the