aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorDenton Liu <liu.denton+github@gmail.com>2016-05-06 21:53:06 +0800
committerDenton Liu <liu.denton+github@gmail.com>2016-05-06 21:53:06 +0800
commit7f940e498e99346e7d9afa47e773dcd7ea9ebd18 (patch)
treeab3c4793a656a5da64d6696a41fbe0f43b89f2f7 /docs
parent7bc9777b70ff92bac078a38906a5d105e660fbea (diff)
downloaddexon-solidity-7f940e498e99346e7d9afa47e773dcd7ea9ebd18.tar.gz
dexon-solidity-7f940e498e99346e7d9afa47e773dcd7ea9ebd18.tar.zst
dexon-solidity-7f940e498e99346e7d9afa47e773dcd7ea9ebd18.zip
Removed trailing whitespace
Diffstat (limited to 'docs')
-rw-r--r--docs/style-guide.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/style-guide.rst b/docs/style-guide.rst
index f856e05a..bc32f891 100644
--- a/docs/style-guide.rst
+++ b/docs/style-guide.rst
@@ -25,7 +25,7 @@ solidity code. The goal of this guide is *consistency*. A quote from python's
captures this concept well.
A style guide is about consistency. Consistency with this style guide is important. Consistency within a project is more important. Consistency within one module or function is most important.
- But most importantly: know when to be inconsistent -- sometimes the style guide just doesn't apply. When in doubt, use your best judgment. Look at other examples and decide what looks best. And don't hesitate to ask!
+ But most importantly: know when to be inconsistent -- sometimes the style guide just doesn't apply. When in doubt, use your best judgment. Look at other examples and decide what looks best. And don't hesitate to ask!
***********
@@ -169,7 +169,7 @@ Immediately before a comma, semicolon:
Yes::
- function spam(uint i, Coin coin);
+ function spam(uint i, Coin coin);
No::