diff --git a/docs/developer_info/developer_information.rst b/docs/developer_info/developer_information.rst
index 8613f26..61be8f0 100644
--- a/docs/developer_info/developer_information.rst
+++ b/docs/developer_info/developer_information.rst
@@ -8,13 +8,13 @@
 .. toctree::
    :maxdepth: 1
    
-.. developer_info/developer_info_Project_Structure.rst
-   developer_info/Camunda_Modeler.rst
-.. developer_info/developer_info_Main_Process_Flows.rst
-.. developer_info/developer_info_Subprocess_Process_Flows.rst
-.. developer_info/developer_info_Project_Deployment_Strategy.rst
-   developer_info/Building_SO.rst
-   developer_info/Working_with_SO_Docker.rst
-   developer_info/Camunda_Cockpit_Community_Edition.rst
-   developer_info/Camunda_Cockpit_Enterprise_Edition.rst
+.. developer_info_Project_Structure.rst
+   Camunda_Modeler.rst
+.. developer_info_Main_Process_Flows.rst
+.. developer_info_Subprocess_Process_Flows.rst
+.. developer_info_Project_Deployment_Strategy.rst
+   Building_SO.rst
+   Working_with_SO_Docker.rst
+   Camunda_Cockpit_Community_Edition.rst
+   Camunda_Cockpit_Enterprise_Edition.rst
    
\ No newline at end of file
diff --git a/docs/release_notes/release-notes.rst b/docs/release_notes/release-notes.rst
index d344849..f9c7002 100644
--- a/docs/release_notes/release-notes.rst
+++ b/docs/release_notes/release-notes.rst
@@ -19,7 +19,7 @@
 * Support PNF resource type.
 * Extend the support of homing to vFW, VDNS usecases.
 * Workflow Designer Integration.
-* Monitoring BPMN worflow capabiliities through UI.
+* Monitoring BPMN worflow capabilities through UI.
 * Support to the CCVPN Usecase.
 * SO internal architecture improvements 
 
@@ -35,7 +35,7 @@
 
 * Enhance Platform maturity by improving SO maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity>`_.
 * Manual scaling of network services and VNFs.
-* Homing and placement capabiliities through OOF interaction. 
+* Homing and placement capabilities through OOF interaction. 
 * Ability to perform change management.
 * Integrated to APPC
 * Integrated to OOF 
@@ -102,7 +102,7 @@
 The orchestration engine is a reusable service. Any component of the architecture can execute SO orchestration capabilities. 
 
 * Orchestration services will process workflows based on defined models and recipe. 
-* The service model maintains consistency and reusability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment.
+* The service model maintains consistency and re-usability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment.
 * Orchestration processes interact with other platform components or external systems via standard and well-defined APIs.