diff --git a/process/README.md b/process/README.md
index b768de52..d90baa78 100644
--- a/process/README.md
+++ b/process/README.md
@@ -1,11 +1,11 @@
 
 # I. Overview
 
-This document describes the Open Source Security Foundation (OpenSSF) life cycle process for Technical Initiatives, inclusive of Working Groups, Projects, and Special Interest Groups (SIG).
+This document describes the Open Source Security Foundation (OpenSSF) lifecycle process for Technical Initiatives (TI) which include Working Groups (WG), Projects (developing code or specifications), and Special Interest Groups (SIG).
 
 The authority that governs this process is as follows:
 
-The parent organizational structure grants governance to the downward in the organizational structure.  In turn the receiving Working Group, Project, or SIG reports health, participation, outcomes, statuses, etc up the chain.
+The parent organizational structure grants governance to the downward entity in the organizational structure.  In turn the receiving Working Group, Project, or SIG reports health, participation, outcomes, statuses, etc up the chain.
 
 ```mermaid
 flowchart TD
@@ -23,7 +23,21 @@ The process is designed to be flexible to enable a Project to move in and out of
 
 # II. Lifecycle
 
-Working Groups and Projects have a different lifecycle as defined below:
+All Technical Initiatives follow a common lifecycle, with 4 stages: 
+
+- Sandbox - for new efforts within the Foundation seeking to get started out within a community of like-minded contributors
+- Incubating - for more mature and organized groups that have participated in the community for some period of time
+- Graduated - for mature efforts that have a proven track-record of deliverables and adding value to the community
+- Archived - for groups that either are feature-complete and retired, or that no longer has active contributions occurring
+
+```mermaid
+flowchart LR
+    A[Sandbox] --> B[Incubating]
+    B --> C[Graduated]
+    C --> D[Archived]
+```
+
+Each type of TI has equivalent, but slightly different requirements and benefits, depending on their stage in the lifecycle as defined below:
 
 * [Working Group Life Cycle](working-group-lifecycle.md)
 * [Project Life Cycle](project-lifecycle.md)
diff --git a/process/TI-lifecycle-stages.png b/process/TI-lifecycle-stages.png
deleted file mode 100644
index bfc8cf4e..00000000
Binary files a/process/TI-lifecycle-stages.png and /dev/null differ