From c3cab5798af6ebf95fe8571360ae0396589d37c7 Mon Sep 17 00:00:00 2001 From: Roland Kofler Date: Thu, 2 Jun 2016 10:35:37 +0200 Subject: [PATCH] typo that might lead to missleading interpretation --- EIPS/eip-1.mediawiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-1.mediawiki b/EIPS/eip-1.mediawiki index d29cf9d2..05625c15 100644 --- a/EIPS/eip-1.mediawiki +++ b/EIPS/eip-1.mediawiki @@ -52,7 +52,7 @@ EIP authors are responsible for collecting community feedback on a EIP before su For a EIP to be accepted it must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the protocol unduly. -Once a EIP has been accepted, the implementations must be completed. When the implementation is complete in at least to viable clients and accepted by the community, the status will be changed to "Final". An update to the [https://github.com/ethereum/yellowpaper formal specification] should accompany the "Final" status change. +Once a EIP has been accepted, the implementations must be completed. When the implementation is complete in at least two viable clients and accepted by the community, the status will be changed to "Final". An update to the [https://github.com/ethereum/yellowpaper formal specification] should accompany the "Final" status change. A EIP can also be assigned status "Deferred". The EIP author or editor can assign the EIP this status when no progress is being made on the EIP. Once a EIP is deferred, the EIP editor can re-assign it to draft status.