diff --git a/configuration/config.rst b/configuration/config.rst
index 6d9c11e..2189179 100644
--- a/configuration/config.rst
+++ b/configuration/config.rst
@@ -1,10 +1,47 @@
 Overview
---------
-Network Slice Configuration
----------------------------
+========
 
-Device Group Configuration
---------------------------
+Reference helm chart
+--------------------
 
-UE Provisioning
----------------
+    - `SD-Core Helm Chart Repository <https://gerrit.opencord.org/admin/repos/sdcore-helm-charts>`_
+
+Configuration Methods
+---------------------
+SD-Core supports 2 ways to configure network functions and micro services.
+
+    - Helm Chart
+
+        - Each individual network function and microservice has its own helm chart.
+        - User needs to provide override values and deploy the network functions as per their need.
+
+    - REST Config Interface
+
+        - Basic static configuration is passed through helm chart
+        - Dynamic slice creation 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.
+
+Configuration
+-------------
+
+    - Network Slice Configuration
+
+        - Configuration to create a slice of network
+        - Slice contains the QoS configuration
+        - Group of devices assigned to network slice
+        - Site configuration including UPF, eNBs/gNB assigned to the slice
+
+    - Device Group Configuration
+
+        - Configuration of group of UEs
+        - QoS required for the device group
+        - IP domain configuration for the group of devices
+
+    - UE Provisioning
+
+        - Configuration of IMSI and its security keys configuration
+
+Sample Configuration
+--------------------
+
diff --git a/dict.txt b/dict.txt
index cc26e7b..f6362f4 100644
--- a/dict.txt
+++ b/dict.txt
@@ -51,3 +51,12 @@
 gpp
 pcrfdb
 Deregistration
+Analytics
+gNodeB
+eNodeB
+iUPF
+tunnelling
+microservice
+QoS
+eNBs
+gNBs
diff --git a/glossary.rst b/glossary.rst
index ecc4dce..00ebcb0 100644
--- a/glossary.rst
+++ b/glossary.rst
@@ -3,28 +3,42 @@
 
 Protocols
 ---------
-- NGAP
-- S1AP
-- Diameter
-- NAS
-- PFCP
+- NGAP: NG Application Protocol used over N2 interface
+- S1AP: S1 Application Protocol used over S1-AP interface
+- Diameter: S6a
+- NAS: Non-Access-Stratum used between UE & MME/AMF.
+- PFCP: Packet Forwarding Control Protocol
 - GTPv1
 - GTPv2
 
 Network Functions
 -----------------
 
-- AMF: Access Management Function
+- AMF: Access and Mobility Management Function
 - UPF: User Plane Function
 - SMF: Session Management Function
 - NRF: Network Repository Function
 - NSSF: Network Slice Selection Function
 - PCF: Policy & Charging Function
-- AUSF: Authentication Function
-- UDM: Unified Data Management Function
-- UDR: Unified Data Repository Function
+- AUSF: Authentication Server Function
+- UDM: Unified Data Management
+- UDR: Unified Data Repository
+- CHF: Charging Function
+- NWDAF: Network Data Analytics Function
+- NEF: Network Exposure Function
+- MME:  Mobility Management Entity
+- SGW: Serving Gateway
+- PGW: PDN Gateway
+- HSS: Home Subscriber Server
+- PCRF: Policy and Charging Rule Function
 
 3gpp Interfaces
 ---------------
-- N4 : SMF to UPF
+- N2: gNodeB to AMF interface
+- N4: SMF to UPF interface
 - SBI interface
+- S1AP: eNodeB to MME interface
+
+Misc
+----
+SA: Standalone Architecture
diff --git a/index.rst b/index.rst
index 2eae763..c78612f 100644
--- a/index.rst
+++ b/index.rst
@@ -38,7 +38,7 @@
    overview/3gpp-compliance-5g.rst
    overview/3gpp-compliance-4g.rst
    overview/faq.rst
-   glossary
+   glossary.rst
 
 .. toctree::
    :maxdepth: 2
diff --git a/release/process.rst b/release/process.rst
index bd65cf4..f4cc7a2 100644
--- a/release/process.rst
+++ b/release/process.rst
@@ -65,7 +65,7 @@
 release can easily be created).
 
 The same should be done on Helm charts in the chart repos post release, but the
-versions there shouldn't include a ``-dev`` suffix because chart publishing
+versions there should not include a ``-dev`` suffix because chart publishing
 requires that every new chart version be unique and unsuffixed SemVer is a
 more consistent release numbering pattern.
 
@@ -105,7 +105,7 @@
 1. Develop a fix to the issue on the master branch, get it approved after
    passing master tests.
 
-2. If it doesn't exist, create an **sdcore-1.0** branch on the component repo,
+2. If it does not exist, create an **sdcore-1.0** branch on the component repo,
    starting at the commit where the **VERSION** of the component used in 1.0 was
    created - this is known as "lazy branching".