aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Ward <chris.ward@ethereum.org>2018-12-17 20:30:06 +0800
committerChris Ward <chris.ward@ethereum.org>2018-12-17 20:30:06 +0800
commit2e8114f3125b3d29cbeb03203fceebc77bc899cc (patch)
tree61d45ff7eace159d3a91a8e0c0a2d8d8065334be
parent8d3617b7c522d74bcc36a1fbc1eb7c16bf96ad4d (diff)
downloaddexon-solidity-2e8114f3125b3d29cbeb03203fceebc77bc899cc.tar.gz
dexon-solidity-2e8114f3125b3d29cbeb03203fceebc77bc899cc.tar.zst
dexon-solidity-2e8114f3125b3d29cbeb03203fceebc77bc899cc.zip
Fix italics formatting issue
-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 34ef012e..7daae06a 100644
--- a/docs/introduction-to-smart-contracts.rst
+++ b/docs/introduction-to-smart-contracts.rst
@@ -41,7 +41,7 @@ source code (e.g. `pragma once <https://en.wikipedia.org/wiki/Pragma_once>`_).
A contract in the sense of Solidity is a collection of code (its *functions*) and
data (its *state*) that resides at a specific address on the Ethereum
blockchain. The line ``uint storedData;`` declares a state variable called ``storedData`` of
-type ``uint`` (*u*nsigned *int*eger of *256* bits). You can think of it as a single slot
+type ``uint`` (*u*\nsigned *int*\eger of *256* bits). You can think of it as a single slot
in a database that can be queried and altered by calling functions of the
code that manages the database. In the case of Ethereum, this is always the owning
contract. And in this case, the functions ``set`` and ``get`` can be used to modify