Replace supported admonitions with rst directives

[docs.git] / docs / user-guide / group-based-policy-user-guide.rst

diff --git a/docs/user-guide/group-based-policy-user-guide.rst b/docs/user-guide/group-based-policy-user-guide.rst
index d730db164f6ec8f3a7b6b70741b3d1690b261f9e..f0344a9f33534017d5f967f02c9aa3a27e822dff 100644 (file)
--- a/docs/user-guide/group-based-policy-user-guide.rst
+++ b/docs/user-guide/group-based-policy-user-guide.rst
@@ -72,7 +72,7 @@ By thinking of **Intent Systems** in this way, it enables:
    -  To an optical network: The port maybe *abstract*, yet the optical
       wavelength is *concrete*.
 
-    **Note**
+.. note::
 
     *This is a very domain specific analogy, tied to something most
     readers will understand. It in no way implies the **GBP** should be
@@ -1690,7 +1690,7 @@ the user is responsible for the provisioning of endpoints via:
 
 -  REST API
 
-    **Note**
+.. note::
 
     When using the :ref:`Neutron mapper <gbp-neutron>` feature, everything is
     managed transparently via Neutron.
@@ -1960,7 +1960,7 @@ Generic allow:
 Configuring OpenFlow Overlay via REST
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-    **Note**
+.. note::
 
     Please see the :ref:`UX <gbp-ux>` section on how to configure **GBP** via
     the GUI.
@@ -1988,7 +1988,7 @@ Configuring OpenFlow Overlay via REST
         }
     }
 
-    **Note**
+.. note::
 
     The usage of "port-name" preceded by "ofoverlay". In OpenDaylight,
     base datastore objects can be *augmented*. In **GBP**, the base