diff --git a/configuration/application_filtering.rst b/configuration/application_filtering.rst
index 5fd79dc..6222cc0 100644
--- a/configuration/application_filtering.rst
+++ b/configuration/application_filtering.rst
@@ -7,6 +7,10 @@
 Application Filtering Overview
 ==============================
 
+.. image:: ../_static/images/SDCore_Access_Control.png
+  :width: 700px
+  :align: center
+
 Below config snapshot shows how to configure application filtering in the network slice.
 Each application filter in the network slice can have action either ``permit`` or ``deny``
 
diff --git a/configuration/config.rst b/configuration/config.rst
index d37072c..df751dd 100644
--- a/configuration/config.rst
+++ b/configuration/config.rst
@@ -29,10 +29,16 @@
     - REST Config Interface
 
         - Basic static configuration is passed through helm chart
-        - Dynamic slice creation APIs are provided through REST interface.
+        - Dynamic *Network Slice* management  APIs are provided through REST interface.
         - REST APIs are defined to create/modify/delete network slice.
         - REST APIs are also provided to provision subscribers and grouping the subscribers under device Group.
 
+.. image:: ../_static/images/config_slice.png
+  :width: 500px
+  :align: center
+
+
+
 Configuration Steps
 -------------------
 This Configuration describes what to configure at high level from RoC/SIMAPP. ConfigPod stores this configuration
diff --git a/configuration/config_simapp.rst b/configuration/config_simapp.rst
index 6029c71..0828d6b 100644
--- a/configuration/config_simapp.rst
+++ b/configuration/config_simapp.rst
@@ -8,6 +8,9 @@
 Easiest way to configure SD-Core is to use simapp. Simapp is the POD which takes
 yaml configuration and configures the subscribers, device groups, network slices
 
+Simapp Initial Configuration Helm Values
+----------------------------------------
+
 .. code-block::
 
   config:
@@ -81,8 +84,11 @@
 
 .. note::
     Simapp takes initial configuration through helm chart. Above yaml files is initial config.
-    Operator can add multiple devices, device groups & slices in the initial config. If simapp
-    is already running then ``kubectl edit configmap simapp -n <namespace>`` can be used to update
-    the simapp configuration. Simapp handles config delete, modify & addition by watching configmap
-    for any changes. There is no need to restart simapp after configmap change. New config will
-    be automatically reloaded.
+    Operator can add multiple devices, device groups & slices in the initial config.
+
+Configuration Modification through Simapp interface
+---------------------------------------------------
+If simapp is already running then ``kubectl edit configmap simapp -n <namespace>`` can be used to update
+the simapp configuration. Simapp handles config delete, modify & addition by watching configmap
+for any changes. There is no need to restart simapp after configmap change. New config will be automatically
+reloaded and updated configuration is passed to SD-Core.