X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=docs%2Foverview.rst;h=b1223a3aedf2ea136e2a233f213e29cee3dcfc50;hb=9a0d7d6f6b9bb268514d0c0e75c071fd297a425a;hp=bda7dd03a3e6162927be5f64ddb2151a96d4aa1e;hpb=aca16f72ab8e1dfa3ef53c213e453d654c15c0ad;p=oam.git

diff --git a/docs/overview.rst b/docs/overview.rst
index bda7dd0..b1223a3 100644
--- a/docs/overview.rst
+++ b/docs/overview.rst
@@ -6,15 +6,15 @@ OAM Operation and Maintenance Overview
 ======================================
 
 The O-RAN SC OAM project provides administrative and operator
-functions for O-RAN components, such as Near-Realtime-RAN-Inelegant-Controller,
-O-RAN Centralized Unit, O-RAN Distributed Unit and O-RAN Radio Unit. 
+functions for O-RAN components, such as Near-Realtime-RAN-Intelligent-Controller,
+O-RAN Centralized Unit, O-RAN Distributed Unit and O-RAN Radio Unit.
 
-The project follows the specifications for the `O1 interface <https://www.o-ran.org/specifications>`_ 
+The project follows the specifications for the `O1 interface <https://www.o-ran.org/specifications>`_
 as provided by O-RAN Working Group 1 (new 10).
 
 The O-RAN-SC OAM project adds features and functions to the OpenDaylight-based ONAP
 controller 'CCSDK/SDNC'. It is built on the Common Controller Framework
-to control and to manage O-RAN ManagedElements and O-RAN ManagedFunctions. 
+to control and to manage O-RAN ManagedElements and O-RAN ManagedFunctions.
 
 .. figure:: ./_static/o-ran-architecture.png
    :alt: SDN-R in ONAP
@@ -33,7 +33,7 @@ The project uses the following Linux Foundation resources:
     `<https://jenkins.o-ran-sc.org/view/oam/>`_
 
 * Issues are tracked in this Jira:
-    `<https://jira.o-ran-sc.org/projects/OAM/>`_
+    `<https://jira.o-ran-sc.org/projects/OAM/issues>`_
 
 * Project information is available in this Wiki:
     `<https://wiki.o-ran-sc.org/display/OAM/Operations+and+Maintenance>`_
@@ -42,23 +42,23 @@ The project uses the following Linux Foundation resources:
 Scope
 -----
 
-According to the `O-RAN-OAM-Architecture document <https://www.o-ran.org/specifications>`_ 
-all ManagedElements (ME) (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU) 
+According to the `O-RAN-OAM-Architecture document <https://www.o-ran.org/specifications>`_
+all ManagedElements (ME) (near-real-time-RIC, O-CU-CP, O-CU-UP, O-DU and O-RU)
 implement the O1-interface.
 
 The O-RAN-OAM-interface specification defines
 
 - a NetConf-Server for Configuration Management (CM) and
-- a http-client for Fault Management (FM), Performance Management (PM) and other 
-  events on each Management-Service-Provider (MnS-Provider) running on the 
+- a http-client for Fault Management (FM), Performance Management (PM) and other
+  events on each Management-Service-Provider (MnS-Provider) running on the
   ManagedElement.
 
-THe O-RAN-SC-OAM project provides reference implementation according to the 
-O-RAN OAM documents. In addition it provides a lightweight MnS-Consumer for 
-development and module test purposes. The assumption is that the projects 
+THe O-RAN-SC-OAM project provides reference implementation according to the
+O-RAN OAM documents. In addition it provides a lightweight MnS-Consumer for
+development and module test purposes. The assumption is that the projects
 for the ManagedElements can concentrate on the more important user-plane.
 
-Each project requires its own OAM repository to address the specific needs 
+Each project requires its own OAM repository to address the specific needs
 of the ManagedFunction.
 
 The following O-RAN specifications are considered during implementations: