From cac275d5cf2766ee39d49dc39bff04f5b8879c0c Mon Sep 17 00:00:00 2001
From: yinzeus <50434320+yinzeus@users.noreply.github.com>
Date: Wed, 21 Aug 2019 11:03:00 -0400
Subject: [PATCH] Update fip-1.md

update to Last Call section to add verbiage for voting requirements.
---
 fips/fip-1.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/fips/fip-1.md b/fips/fip-1.md
index a0f4b9a..05649b0 100644
--- a/fips/fip-1.md
+++ b/fips/fip-1.md
@@ -57,10 +57,10 @@ Parties involved in the process are you, the champion, owner, or *FIP author*, t
   * :x: -- A request for Last Call status will be denied if material changes are still expected to be made to the draft. FIPs should only enter *Last Call* once.
   * :arrow_right: -- *LAST CALL* -- Once the champion believes there are no material changes left to the FIP, an FIP editor will assign *Last Call* status and set a review end date (`review_period_end`), normally the next FOAM Community Workshop Call. 
   
-**LAST CALL**- finalized version is brought to a FOAM Community Call and argued for by the champion. Vote takes place on the call to assess community support for the FIP. These FIPs will be listed prominently on the https://fips.foam.space/ website.
-  * :x: -- A request which results in material changes or substantial unaddressed functional complaints will cause the FIP to revert to *Draft*. A *Last Call* which does not pass the formal community vote with (x) number of people on the call or (y) percentage of call members in favor of the FIP will revert to *Draft*.
-  * :arrow_right: -- *ACCEPTED* (Standard track FIPs only) -- A successful *Last Call* without material changes or unaddressed technical complaints that also passes the formal community vote with (x) number of people on the call and (y) percentage of call members in favor of the FIP will be considered *Accepted*.
-  * :arrow_right: -- *ACTIVE* -- (Informational and meta FIPs only) -- A successful *Last Call* without material changes or unaddressed technical complaints that also passes the formal community vote with (x) number of people on the call and (y) percentage of call members in favor of the FIP will be considered *Completed*.
+**LAST CALL** - finalized version is brought to a FOAM Community Call and argued for by the champion. Vote takes place on the call to assess community support for the FIP. These FIPs will be listed prominently on the https://fips.foam.space/ website.
+  * :x: -- A request which results in material changes or substantial unaddressed functional complaints will cause the FIP to revert to Draft. A Last Call which does not pass the formal community vote with a minimum of six people on the call AND 66% of call members in favor of the FIP will revert to *Draft*.
+  * :arrow_right: -- *ACCEPTED* (Standard track FIPs only) -- A successful Last Call without material changes or unaddressed technical complaints that also passes the formal community vote with a minimum of six people on the call AND 66% of call members in favor of the FIP will be considered *Accepted*.
+  * :arrow_right: -- *ACTIVE* -- (Informational and meta FIPs ONLY) -- A successful Last Call without material changes or unaddressed technical complaints that also passes the formal community vote with a minimum of six people on the call AND 66%  of call members in favor of the FIP will be considered *Active*.
   
 **ACCEPTED**- at this point, the relevant stakeholders in the FOAM ecosystem should move forward with making any accomodations to their systems or processes as they relate to this FIP. If the FIP is for a community governance vote on a change to a TCR parameter, then a vote may be initiated at this stage.
   * :arrow_right: -- *COMPLETED* -- (Standard track FIPs) -- A successful *Accepted* that has been fully implemented to production will become *Completed*.