Adapt feature names change in docs

[docs.git] / docs / developer-guide / network-intent-composition-(nic)-developer-guide.rst

diff --git a/docs/developer-guide/network-intent-composition-(nic)-developer-guide.rst b/docs/developer-guide/network-intent-composition-(nic)-developer-guide.rst
index 3a5f5a94709075d27b9f0dee549339019f020b2e..cb7941bf8f909eac9daedd7fc9ba742f6663cefa 100644 (file)
--- a/docs/developer-guide/network-intent-composition-(nic)-developer-guide.rst
+++ b/docs/developer-guide/network-intent-composition-(nic)-developer-guide.rst
@@ -1,3 +1,5 @@
+.. _nic-dev-guide:
+
 Network Intent Composition (NIC) Developer Guide
 ================================================
 
@@ -17,7 +19,7 @@ The Network Intent Composition (NIC) provides four features:
 -  odl-nic-console: Provides a karaf CLI extension for intent CRUD
    operations and mapping service operations.
 
--  odl-nic-renderer-of - Generic Openflow Renderer.
+-  odl-nic-renderer-of - Generic OpenFlow Renderer.
 
 -  odl-nic-renderer-vtn - a feature that transforms an intent to a
    network modification using the VTN project
@@ -263,7 +265,7 @@ illustrated in the diagram below:
    MPLS VPN Service Diagram
 
 where PE (Provider Edge) and P (Provider) switches are managed by
-Opendaylight. In NIC’s terminology the endpoints are the PE switches.
+OpenDaylight. In NIC’s terminology the endpoints are the PE switches.
 There could be many P switches between the PEs.
 
 In order for NIC to recognize endpoints as MPLS endpoints, the user is
@@ -277,7 +279,7 @@ mapping service to include the below properties:
 3. Switch-Port: Ingress (or Egress) for source (or Destination) endpoint
    of the source (or Destination) PE
 
-An intent:add between two MPLS endpoints renders Openflow rules for: 1.
+An intent:add between two MPLS endpoints renders OpenFlow rules for: 1.
 push/pop labels to the MPLS endpoint nodes after an IPv4 Prefix match.
 2. forward to port rule after MPLS label match to all the switches that
 form the shortest path between the endpoints (calculated using Dijkstra
@@ -308,7 +310,7 @@ How to use it?
    ::
 
        feature:install odl-nic-core-service-mdsal odl-nic-core odl-nic-console odl-nic-listeners
-       feature:install odl-dlux-all odl-dlux-core odl-dlux-yangui odl-dlux-yangvisualizer
+       feature:install  odl-dlux-core odl-dluxapps-applications
 
 2. Start mininet topology and verify in DLUX Topology page for the nodes
    and link.
@@ -414,7 +416,7 @@ How to use it?
        intent:add -f uva -t eur -a ALLOW
        intent:add -f eur -t uva -a ALLOW
 
-5. Verify by running ovs command on mininet if the flows were pushed
+5. Verify by running ovs-ofctl command on mininet if the flows were pushed
    correctly to the nodes that form the shortest path.
 
    Example: