From 81e4cde6bef76b2ef3dcb34772e392258f7b4746 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Lesaege?= Date: Thu, 12 Oct 2017 22:25:42 +0200 Subject: [PATCH] Fix misspelling in "compatibility" --- EIPS/eip-20-token-standard.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-20-token-standard.md b/EIPS/eip-20-token-standard.md index e1086c39..4b209dcd 100644 --- a/EIPS/eip-20-token-standard.md +++ b/EIPS/eip-20-token-standard.md @@ -128,7 +128,7 @@ Allows `_spender` to withdraw from your account multiple times, up to the `_valu **NOTE**: To prevent attack vectors like the one [described here](https://docs.google.com/document/d/1YLPtQxZu1UAvO9cZ1O2RPXBbT0mooh4DYKjA_jp-RLM/) and discussed [here](https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729), clients SHOULD make sure to create user interfaces in such a way that they set the allowance first to `0` before setting it to another value for the same spender. -THOUGH The contract itself shouldn't enforce it, to allow backwards compatilibilty with contracts deployed before +THOUGH The contract itself shouldn't enforce it, to allow backwards compatibility with contracts deployed before ``` js function approve(address _spender, uint256 _value) returns (bool success)