Renamed and moved a few things
address assignment -> dhcp relay
community -> resource
Change-Id: I807a896d8a8f610eb8af0063ba36ba0f0d55c070
diff --git a/configuration/bridging-unicast.rst b/configuration/bridging-unicast.rst
index ede859d..1eb54a9 100644
--- a/configuration/bridging-unicast.rst
+++ b/configuration/bridging-unicast.rst
@@ -138,7 +138,7 @@
There is no need to configure ports on switches that are meant to connect to other switches.
The VLAN (untagged or tagged) configuration is only meant for ports that are connected to hosts (edge ports).
-.. image:: images/vlan-config.png
+.. image:: ../images/config-vlan.png
Furthermore, note that the same VLAN can be configured on multiple ToRs - e.g. vlan 20 in the figure above.
However this does not mean that the ports are in the same bridging domain, because in the fabric, the communication between ToRs is through a routed network. '
@@ -150,4 +150,4 @@
If the bridging domain is extended across two ToRs directly linked to each other, there is a chance of loops.
In other words, the ToRs/Leafs are not standalone 802.1Q bridges, and should not be used as such.
-.. image:: images/vlan-config-invalid.png
+.. image:: ../images/config-vlan-invalid.png