Update en/20/07.md

Co-authored-by: Andrei Popescu <[email protected]>

en/20/07.md

@@ -120,7 +120,7 @@ We aren't going to go deep into the proofs the many researchers have done to ens
 
 In brief, a smart contract requests randomness by specifying a hash used to uniquely identify a Chainlink oracle. That has is used by the Chainlink node with it's own secret key to generate a random number, which is then returned to the contract on-chain, along with a cryptographic proof. An on-chain contract (called the `VRF Coordinator`) takes the random number along with the proof, and is verified using the oracle’s public key. Relying on the widely accepted signature and proof verification capabilities of a blockchain, this enables contracts to consume only randomness that has also been verified by the same on-chain environment running the contract itself.
 
-You can check out the [Chainlink VRF contracts](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.6/VRFCoordinator.sol) to see the exact functions the system is using. 
+You can check out the <a href="https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.6/VRFCoordinator.sol" target=_new>Chainlink VRF contracts</a> to see the exact functions the system is using. 
 
 Wow, ok, there is a lot of big brained concepts here! Let's finally dive into learning how to pull a random number into our smart contract. We can get started, by once again pulling the Chainlink VRF contract code from NPM / Github that allows us to interact with a Chainlink VRF node. We are going to `inherit` the functionality of this VRFConsumerbase contract code into our code to emit events, and define what functions the Chainlink node is going to callback (respond) to.