doc: move spec to separate folder

Author: perama-v

src/eth/addresses.md renamed to specs/appearances.md

@@ -4,17 +4,17 @@ Specification for addresses appearances returned by `eth_getAddressesInBlock`
 
 ## Introduction
 
-An address may "appear" in a Ethereum transaction. If an address appears in a transaction, that
+An address may "appear" in an Ethereum transaction. If an address appears in a transaction, that
 transaction could be meaningful to examine as a historical record.
 
 For example, an appearance may be "an address that is a recipient of a transfer of Ether during
-the EVM execution". Such an appeaarance (the presence of the address in that transaction in that
+the transaction execution". Such an appeaarance (the presence of the address in that transaction in that
 way) makes that transaction meaningful in an examination of the historical balances of that
 address.
 
 A collection of "address appearances" (defined in subsequent section) consistutes a set of transactions
 that are sufficient to form a complete historical analysis of "activity" for that address.
-This "activity" may take many meanings (programs in the EVM may do arbitrary things), but can
+This "activity" may take many meanings (programs in the Ethereum may do arbitrary things), but can
 be identified structurally as will be shown.
 
 ## Overview
@@ -54,7 +54,7 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S
 
 An address is informally defined as 40 hexadecimal characters that
 - May include some leading or trailing zeros (for vanity addresses)
-- Appears in the EVM environment in a 32 byte section with left padding.
+- Appears in a transaction within a 32 byte section with left padding.
 or example, in transaction calldata, in this case the calldata is trimmed to a 32 byte multiple,
 divided into 32 byte sections with checked separately for "address" or "not address" classification.
 
@@ -288,7 +288,7 @@ It can be seen in the example below (a subset of the response from the above cal
 
 ## Security Considerations
 
-The EVM allows for use of data that has the same structure as a 20 byte address.
+Ethereum allows for use of data that has the same structure as a 20 byte address.
 The algorithm used to find address appearances ideally minimises missing appearances
 (false negatives) and so may include false positives.