From a3969a563653045826d744de5fbe46a495b76cc2 Mon Sep 17 00:00:00 2001
From: jrstorment <66805995+jrstorment@users.noreply.github.com>
Date: Tue, 9 Mar 2021 13:12:03 -0800
Subject: [PATCH] Clarifying that Consultants cannot be practitioners

---
 practitioner_definition.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/practitioner_definition.md b/practitioner_definition.md
index 3a7257b..a8e6744 100644
--- a/practitioner_definition.md
+++ b/practitioner_definition.md
@@ -2,6 +2,6 @@
 
 This file outlines the criteria for joining the FinOps Foundation as a Practitioner member.
 
-> Practitioners must: (i) be actively working in FinOps: (a) in an executive capacity, such as a Chief Information Officer or Chief Technology Officer; (b) in IT/engineering and operations; (c) in finance and/or procurement; (d) as a FinOps practitioner; or (e) in a similar capacity (regardless of title); (ii) not be employed by a FinOps, cloud, or cloud management vendor; and (iii) not have FinOps-related sales, marketing, or business development as their primary business. 
+> Practitioners must: (i) be actively working in FinOps or cloud financial management related work: (a) in an executive capacity, such as a Chief Information Officer or Chief Technology Officer; (b) in IT/engineering and operations; (c) in finance and/or procurement; (d) as a FinOps practitioner; or (e) in a similar capacity (regardless of title); (ii) not be employed by a FinOps, cloud, or cloud management vendor or company offering consultancy or advisory services; and (iii) not have FinOps-related sales, marketing, or business development as their primary business, regardless of the company they are in. 
 
 This definition is owned by the Technical Advisory Council and may evolve over time.