From d25bfd4345d726d706d80dc783f782a3749abe8f Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Tue, 25 Feb 2014 19:20:05 -0500 Subject: [PATCH] small change to module02-ch003-neutron-use-cases removed such Change-Id: I976348bf28c5161fa8bb339f4ecc92ab3d663cfa --- doc/training-guides/module002-ch003-neutron-use-cases.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/training-guides/module002-ch003-neutron-use-cases.xml b/doc/training-guides/module002-ch003-neutron-use-cases.xml index 9dcde18888..250c5b7888 100644 --- a/doc/training-guides/module002-ch003-neutron-use-cases.xml +++ b/doc/training-guides/module002-ch003-neutron-use-cases.xml @@ -16,7 +16,7 @@ This essentially maps to the FlatManager and FlatDHCPManager models provided by OpenStack Compute. Floating IPs are not supported. - It is common that such an OpenStack Networking network + It is common that an OpenStack Networking network is a "provider network", meaning it was created by the OpenStack administrator to map directly to an existing physical network in the data center. This allows the