diff --git a/erc777/README.md b/erc777/README.md
index 4d2574f..a2c8d33 100644
--- a/erc777/README.md
+++ b/erc777/README.md
@@ -2,17 +2,20 @@
 
 The [ERC777 Token Standard](https://eips.ethereum.org/EIPS/eip-777) improves upon the popular [ERC20](https://contracts.vyperhub.io/contracts/erc20) standard.
 
-Its most defining feature is the use of the new [ERC1820](http://eips.ethereum.org/EIPS/eip-1820) interface standard which it uses in such a way, that each time tokens are sent two things happen: 
-1. The ERC777 contract It checks whether the sender of the transaction is a contract and whether that contract implements a `tokensToSend(_operator, _from, _to, _amount, _data, _operatorData)` function.
+Its most defining feature is the use of the new [ERC1820](http://eips.ethereum.org/EIPS/eip-1820) interface standard which it uses in such a way, that each time tokens are sent the ERC777 contract does two things: 
+1. It checks whether the sender of the transaction is a contract and whether that contract implements a `tokensToSend(_operator, _from, _to, _amount, _data, _operatorData)` function.
 2. It checks whether the receiver of the transaction is a contract and whether that contract implements a `tokensToSend(_operator, _from, _to, _amount, _data, _operatorData)` function.
 
 If the functions exist, then the code inside of both functions is executed. 
 The exciting part is, that there are no restrictions on what the code inside of the two functions looks like or what it does.
 
 ## Tests
+
 ### Run local tests
+
 ```bash
 $ truffle test --network ganache
 ```
 ### More tests
+
 Further tests for this implementation may be found [here](https://github.com/0xjac/ERC777/tree/master/test).