Edited 09smart-contracts-security.asciidoc with Atlas code editor

09smart-contracts-security.asciidoc

@@ -2434,7 +2434,7 @@ mathematical operations. It may be the case that it is better to keep
 all variables in high precision in Solidity and convert back to lower
 precisions in external apps (this is essentially how the `decimals`
 variable works in ERC20 token
-contracts). To see an example of how this can be done, we recommend looking at https://github.com/dapphub/ds-math[DS-Math]. They use some
+contracts). To see an example of how this can be done, we recommend looking at https://github.com/dapphub/ds-math[DS-Math]. It uses some
 funky naming (“wads” and “rays”), but the concept is useful.
 
 ==== Real-World Example: Ethstick
@@ -2521,7 +2521,7 @@ contract AttackContract {
 The attacker might disguise this contract as their own private address and socially engineer the victim (the owner of the +Phishable+ contract) to send some form of transaction to the address—perhaps sending this contract some amount of ether. The attacker might disguise this contract as their own private
 address and socially engineer the victim to send some form of transaction
 to the address. The victim, unless careful, may not notice that
-there is code at the attacker’s address, or the attacker may pass it off
+there is code at the attacker’s address, or the attacker might pass it off
 as being a multisignature wallet or some advanced storage wallet (remember
 that the source code of public contracts is not available by default).