X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2Fuser-guide%2Fgenius-user-guide.rst;h=1385ebb30901336ff50cf3a1fcc161cd72fd5c8d;hb=c7aee2f0179b89ed22e8e628ee437b41203edd4c;hp=bf07ff911ca339b0f2270a48d170766d1f1f9daa;hpb=2099ac6c19a11179b3e90ef1104147e95494a83d;p=docs.git

diff --git a/docs/user-guide/genius-user-guide.rst b/docs/user-guide/genius-user-guide.rst
index bf07ff911..1385ebb30 100644
--- a/docs/user-guide/genius-user-guide.rst
+++ b/docs/user-guide/genius-user-guide.rst
@@ -1,3 +1,5 @@
+.. _genius-user-guide:
+
 Genius User Guide
 =================
 
@@ -11,8 +13,8 @@ interference-free co-existence with other applications using Genius.
 Modules and Interfaces
 ----------------------
 
-In the the first phase delivered in OpenDaylight Boron release, Genius
-provides following modules — 
+In the first phase delivered in OpenDaylight Boron release, Genius
+provides following modules —
 
 -  Modules providing a common view of network interfaces for different
    services
@@ -130,7 +132,7 @@ Creating L2 port interfaces
 '''''''''''''''''''''''''''
 
 Interfaces on normal L2 ports (e.g. Neutron tap ports) are created with
-type *l2vlan* and *l2vlan-mode* as *transparent*. This type of interfce
+type *l2vlan* and *l2vlan-mode* as *transparent*. This type of interface
 classifies packets passing through a particular L2 (OpenFlow) port. In
 dataplane, packets belonging to this interface are classified by
 matching in-port against the of-port-id assigned to the base port as
@@ -218,6 +220,8 @@ MPLSoverGRE.
         ]
     }
 
+.. _genius-user-guide-binding-services:
+
 Binding services on interface
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -228,9 +232,9 @@ contains the service binding configuration data model.
 An application can bind services to a particular interface by
 configuring MD-SAL data node at path /config/interface-service-binding.
 Binding services on interface allows particular service to pull traffic
-arriving on that interafce depending upon the a service priority.
+arriving on that interface depending upon the service priority.
 Service modules can specify openflow-rules to be applied on the packet
-belonging to the inetrface. Usually these rules include sending the
+belonging to the interface. Usually these rules include sending the
 packet to specific service table/pipeline. Service modules are
 responsible for sending the packet back (if not consumed) to service
 dispatcher table, for next service to process the packet.