From b1593373d63c1a425666d3a58fd010e5659b3703 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Mon, 12 Feb 2024 21:35:37 -0500
Subject: [PATCH] Update README.md

---
 README.md | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 8a650e1..8399497 100644
--- a/README.md
+++ b/README.md
@@ -4,13 +4,12 @@
 
 ## RFC Process
 
-This repository contains specifications from the [Vac](https://vac.dev), [Waku](https://waku.org/), [Nomos](https://nomos.tech/), [Codex](https://codex.storage/), and [Status](https://status.app/) software teams.
+This repository contains specifications from the [Waku](https://waku.org/), [Nomos](https://nomos.tech/), 
+[Codex](https://codex.storage/), and [Status](https://status.app/) projects that are apart of the [IFT portfolio](https://free.technology/).
+[Vac](https://vac.dev) is an [IFT service](https://free.technology/services) that will manage the RFC process within this repository.
 The goal of the RFC, [Request for Comments](https://en.wikipedia.org/wiki/Request_for_Comments),
 process is to standardize techincal specification. 
-This repository will track specifications that adhere to 1/COSS.
-RFCs will be managed by the Vac team when specifcations have reached a rough consensus towards stabilization within each team.
-
-Vac is an R&D org creating modular p2p protocols for private, secure, and censorship-resistant communication.
+Specifications will adhere to 1/COSS by obtianing rough consensus within each project.
 
 **See [rfc.vac.dev](https://rfc.vac.dev) for an easy to browse index of all RFCs.**