From 59533792b4fa83101079857bd8b05657b4892278 Mon Sep 17 00:00:00 2001 From: John B Nelson Date: Fri, 11 Sep 2020 09:32:15 -0700 Subject: [PATCH] Add missing word to examples doc explainer --- docs/examples/micropayment.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/examples/micropayment.rst b/docs/examples/micropayment.rst index 2ff293f48..4b0e81a89 100644 --- a/docs/examples/micropayment.rst +++ b/docs/examples/micropayment.rst @@ -61,12 +61,11 @@ For a contract that fulfils payments, the signed message must include: 2. The amount to be transferred. 3. Protection against replay attacks. -A replay attack is when a signed message is reused to claim authorization for -a second action. -To avoid replay attacks we use the same as in Ethereum transactions -themselves, a so-called nonce, which is the number of transactions sent by an -account. -The smart contract checks if a nonce is used multiple times. +A replay attack is when a signed message is reused to claim +authorization for a second action. To avoid replay attacks +we use the same technique as in Ethereum transactions themselves, +a so-called nonce, which is the number of transactions sent by +an account. The smart contract checks if a nonce is used multiple times. Another type of replay attack can occur when the owner deploys a ``ReceiverPays`` smart contract, makes some