more doc (and by more I mean like 2 or 3 sentances)

1 files changed, 13 insertions, 6 deletions

diff --git a/doc/source/devref/multinic.rst b/doc/source/devref/multinic.rst
index 2a01010785..38e750a2d7 100644
--- a/doc/source/devref/multinic.rst
+++ b/doc/source/devref/multinic.rst
@@ -13,14 +13,21 @@ Managers
 
 Each of the 3 network managers are designed to run indipendantly of the compute manager. They expose a common API for the compute manager to call to determine and configure the network(s) for an instance. Direct calls to either the network api or especially the DB should be avoided by the virt layers.
 
-Flat Examples
--------------
+Flat Manager 
+------------
 
+<Diagram of Flat Network (basically the one above)>
 
+The flat manager is most similar to a traditional switched network environment. It assumes that the IP routing, DNS, DHCP (possibly) and bridge creation is handled by something else. That is it makes no attemp to configure any of this. It does keep track of a range of IPs for the instances that are connected to the network to be allocated.
 
+Each instance will get a fixed ip from each network's pool. The guest operating system may be configured to gather this information through an agent or by the hypervisor injecting the files, or it may ignore it completly and come up with only a layer 2 connection.
 
-FlatDHCP Examples
------------------
+FlatDHCP Manager
+----------------
 
-VLAN Examples
--------------
+<Diagram of FlatDHCP Manager>
+
+
+
+VLAN Manager
+------------