AETHER-3206 Update low level documentation for 2.0
AETHER-3330 Update diagrams and process docs for 2.0
Fix paths and language used on runtime deployment for clarity
Rename management server -> management router
Change-Id: Ib9745f45e2abee2a05ec49296dee9c7ff39b580d
diff --git a/edge_deployment/sdfabric_deployment.rst b/edge_deployment/sdfabric_deployment.rst
index 480e4db..0371f24 100644
--- a/edge_deployment/sdfabric_deployment.rst
+++ b/edge_deployment/sdfabric_deployment.rst
@@ -407,10 +407,12 @@
------------
Fabric connectivity should be fully ready at this point.
-We should verify that **all servers**, including compute nodes and the management server,
-have an IP address and are **able to reach each other via fabric interface** before continuing the next step.
+We should verify that **all servers**, including compute nodes and the
+management router, have an IP address and are **able to reach each other via
+fabric interface** before continuing the next step.
-This can be simply done by running a **ping** command from one server to another server's fabric IP.
+This can be simply done by running a **ping** command from one server to
+another server's fabric IP.
Troubleshooting