aboutsummaryrefslogtreecommitdiffstats
path: root/docs/introduction-to-smart-contracts.rst
diff options
context:
space:
mode:
authorDenton Liu <liu.denton+github@gmail.com>2016-08-17 02:13:23 +0800
committerDenton Liu <liu.denton+github@gmail.com>2016-08-24 23:43:56 +0800
commit89004edb2f4ad02fc06546d1c88f4c91b78388e5 (patch)
tree14a5535f3e7eeafd1d4fcdfce80bcc6dcc66d4df /docs/introduction-to-smart-contracts.rst
parent41ad2110c276ec78b403c0ee96a11a96407e0d1b (diff)
downloaddexon-solidity-89004edb2f4ad02fc06546d1c88f4c91b78388e5.tar.gz
dexon-solidity-89004edb2f4ad02fc06546d1c88f4c91b78388e5.tar.zst
dexon-solidity-89004edb2f4ad02fc06546d1c88f4c91b78388e5.zip
Add comma
Diffstat (limited to 'docs/introduction-to-smart-contracts.rst')
-rw-r--r--docs/introduction-to-smart-contracts.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/introduction-to-smart-contracts.rst b/docs/introduction-to-smart-contracts.rst
index 65019e2b..fbce4244 100644
--- a/docs/introduction-to-smart-contracts.rst
+++ b/docs/introduction-to-smart-contracts.rst
@@ -220,7 +220,7 @@ only the person holding the keys to the account can transfer money from it.
Blocks
======
-One major obstacle to overcome is what in Bitcoin terms is called "double-spend attack":
+One major obstacle to overcome is what, in Bitcoin terms, is called "double-spend attack":
What happens if two transactions exist in the network that both want to empty an account,
a so-called conflict?