spelling

docs/velos_networking.rst

@@ -23,13 +23,13 @@ Below is an example deployment; where each system controller has its own unique
   :align: center
   :scale: 50%
 
-It is recommended to connect both management intferaces from controller-1 and controller-2 to your switching infrastructure for resiliency and for increased bandwidth. Link Aggregation (LAG) is recommmended when setting up the system controller management ports. This will provide a better failover/reachabilty experience as well as double the bandwidth than having both ports connected to an upstream switch in an un-aggregated fashion . When un-aggregated the port on the standby system controller will be put in a blocking mode to prevent a bridge loop from occuring so you will be limited to 10Gb of bandwidth. The the internal switchd process monitors the HA status of the local controller and will disable forwarding on the mgmt port if the system controller is in standby mode. If a controller's mgmt interface goes down, it will fail over to the other system controller and will not assume the active role. 
+It is recommended to connect both management interfaces from controller-1 and controller-2 to your switching infrastructure for resiliency and for increased bandwidth. Link Aggregation (LAG) is recommended when setting up the system controller management ports. This will provide a better failover/reachability experience as well as double the bandwidth than having both ports connected to an upstream switch in an un-aggregated fashion. When un-aggregated the port on the standby system controller will be put in a blocking mode to prevent a bridge loop from occurring so you will be limited to 10Gb of bandwidth. The internal switchd process monitors the HA status of the local controller and will disable forwarding on the mgmt port if the system controller is in standby mode. If a controller's mgmt interface goes down, it will fail over to the other system controller and will not assume the active role. 
 
 .. image:: images/velos_networking/sys-con-mgmt-ports.png
   :align: center
   :scale: 100%
 
-Even though each system controller has a static IP adddress, they will still both be reachable even if one of the controller mgmt interfaces is down. This is due to the fact that there is an internal switch connecting the two system controllers so they they both have equal external connectivity, even if one of the interfaces is down. As an example, if the mgmt interface for controller-2 is disconnected, you might assume that controller-2 would be unreachable via its static IP address. But this is not the case. Since each mgmt port on the system controller is wired internally to a local controlplane switch and the two switches are cross-connected, you can still reach the fixed address of either controller even if only one mgmt interface is available. 
+Even though each system controller has a static IP address, they will still both be reachable even if one of the controller mgmt interfaces is down. This is due to the fact that there is an internal switch connecting the two system controllers so they both have equal external connectivity, even if one of the interfaces is down. As an example, if the mgmt interface for controller-2 is disconnected, you might assume that controller-2 would be unreachable via its static IP address. But this is not the case. Since each mgmt port on the system controller is wired internally to a local controlplane switch and the two switches are cross-connected, you can still reach the fixed address of either controller even if only one mgmt interface is available. 
 
 You can see this behavior when in an un-aggregated mode by looking at the mgmt interfaces of each controller in F5OS. The example below filters on the properties of interest and uses 'repeat' to watch how the counters change.