Merge "Remove old ODL+OpenStack content"

[docs.git] / docs / developer-guide / yang-tools.rst

diff --git a/docs/developer-guide/yang-tools.rst b/docs/developer-guide/yang-tools.rst
index 877a52aed2bc2f04f04ccb0f7e1d33aa1f555d88..fede7d9b1b6abacad97b1ccf0637eee28b81bc29 100644 (file)
--- a/docs/developer-guide/yang-tools.rst
+++ b/docs/developer-guide/yang-tools.rst
@@ -1,3 +1,5 @@
+.. _yangtools-developer-guide:
+
 YANG Tools Developer Guide
 ==========================
 
@@ -322,7 +324,7 @@ Before you use a semantic version statement in a YANG module, you need
 to define an extension for it so that the YANG statement parser can
 recognize it.
 
-.. code:: yang
+.. code::
 
     module semantic-version {
         namespace "urn:opendaylight:yang:extension:semantic-version";
@@ -350,7 +352,7 @@ semantic version processing mode being active, the foo module imports
 the bar module based on its semantic version. Notice how both modules
 import the module with the semantic-version extension.
 
-.. code:: yang
+.. code::
 
     module foo {
         namespace foo;
@@ -368,7 +370,7 @@ import the module with the semantic-version extension.
         ...
     }
 
-.. code:: yang
+.. code::
 
     module bar {
         namespace bar;
@@ -498,7 +500,7 @@ Below is an example which shows the use of this method.
 Let us show a more complex example of creating a NormalizedNode. First,
 consider the following YANG module:
 
-.. code:: yang
+.. code::
 
     module example-module {
         namespace "opendaylight.org/example-module";
@@ -709,4 +711,3 @@ Introducing specific extension support for YANG parser
 
 Diagnostics
 ~~~~~~~~~~~
-