Updated software-upgrade documentation
Change-Id: I9653dbe5180a382c9944980bb0bc78b6f7bb472b
diff --git a/operations/software-upgrade.rst b/operations/software-upgrade.rst
index 5d9b592..b125bb5 100644
--- a/operations/software-upgrade.rst
+++ b/operations/software-upgrade.rst
@@ -112,10 +112,19 @@
ONOS app not starting or broken functionality
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
For ONOS apps a manual intervention is always necessary, both if the app does not start or if functionality is broken.
The rollback of an ONOS application is done by following the same procedure as the
update using the previous, or last known working, version of the `.oar` file.
+Inter-dependency among changes submitted in different Components
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Even though it is expected that minor version upgrade should be seemless,
+still there are chances that the changes that went in for a component are related with other component changes.
+In this case the operator needs to perform a manual intervention,
+and upgrade the components manually in desired order.
+
Major Software Version Update
=============================
A software update is qualified to be `major` where there are changes in the APIs or in the format of the