From bddc2486fccd764cc9a004340471d7c35f932b67 Mon Sep 17 00:00:00 2001 From: CRob <69357996+SecurityCRob@users.noreply.github.com> Date: Thu, 16 Nov 2023 10:50:05 -0500 Subject: [PATCH] Update README.md typo & spacing correction Signed-off-by: CRob <69357996+SecurityCRob@users.noreply.github.com> --- process/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/process/README.md b/process/README.md index de318dfc..6db3c512 100644 --- a/process/README.md +++ b/process/README.md @@ -24,14 +24,14 @@ The process is designed to be flexible to enable a Project to move in and out of # II. Lifecycle -Technical Initiatives (TIs) include Working Groups (WGs), Special Interest Groups (SIGs) and Projects(both code and specificiations). All TIs follow a common lifecyle, with 4 stages: +Technical Initiatives (TIs) include Working Groups (WGs), Special Interest Groups (SIGs) and Projects (both code and specificiations). All TIs follow a common lifecyle, 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 occuring -Each TI will haved equivellent, but slighly different requirements and benefits, depending on their stage in the lifecyle and are defined below: +Each TI will haved equivellent, but slightly different requirements and benefits, depending on their stage in the lifecyle and are defined below: * [Working Group Life Cycle](working-group-lifecycle.md) * [Project Life Cycle](project-lifecycle.md)