Never mind, this looks correct

EIPS/eip-712.md

@@ -42,8 +42,8 @@ Here we outline a scheme to encode data along with its structure which allows it
 ## Specification
 
 The set of signable messages is extended from transactions and bytestrings `𝕋 ∪ 𝔹⁸ⁿ` to also include structured data `𝕊`. The new set of signable messages is thus `𝕋 ∪ 𝔹⁸ⁿ ∪ 𝕊`. They are encoded to bytestrings suitable for hashing and signing as follows:
-=*   `encode(transaction : 𝕋) = RLP_encode(transaction)`
-*   `encode(message : 𝔹⁸ⁿ) = ""\x19\x01" ‖ domainSeparator ‖ hashStruct(message)`
+*   `encode(transaction : 𝕋) = RLP_encode(transaction)`
+*   `encode(message : 𝔹⁸ⁿ) = "\x19Ethereum Signed Message:\n" ‖ len(message) ‖ message` where `len(message)` is the _non-zero-padded_ ascii-decimal encoding of the number of bytes in `message`.
 *   `encode(domainSeparator : 𝔹²⁵⁶, message : 𝕊) = "\x19\x01" ‖ domainSeparator ‖ hashStruct(message)` where `domainSeparator` and `hashStruct(message)` are defined below.
 
 This encoding is deterministic because the individual components are. The encoding is injective because the three cases always differ in first byte. (`RLP_encode(transaction)` does not start with `\x19`.)