Small fix in ethers page (#31)

Author: kianenigma

docs/index.md

@@ -10,7 +10,7 @@ to gather feedback during development.
 
 Our solution is Ethereum-compatible: You can write your contracts in Solidity and interact with the node
 using Ethereum JSON RPC alongside an Ethereum wallet like MetaMask. Under the hood, we recompile the
-contracts from YUL (EVM assembly) to RISC-V to run them using PolkaVM instead of EVM.
+contracts from YUL (EVM assembly) to RISC-V to run them using [PolkaVM](https://wiki.polkadot.network/docs/learn-jam-chain#polkadot-virtual-machine-pvm) instead of EVM.
 
 To keep things simple for now, you need to use our [REMIX](https://remix.polkadot.io) web frontend to compile
 your contracts to RISC-V and deploy them to Westend. Eventually, we will provide tools to accomplish this process locally.

docs/tutorial/3-getting-started-with-ethers.js.md

@@ -143,16 +143,22 @@ Once compiled, you can deploy your contract, as shown below.
 ```ts
 import { ContractFactory } from 'ethers'
 import { compile } from '@parity/revive'
+import { readFileSync } from 'fs'
 
-// Compile the solidity contract to Polkavm bytecode.
+// Update the following two based on your contract. Ensure `ContractName` is same as defined in `*.sol`.
 const contract = './path/MyContract.sol'
 const contractName = 'MyContract'
+// Compile the solidity contract to Polkavm bytecode.
 const res = await compile({
   [contract]: {
     content: readFileSync(contract, 'utf8'),
   },
 })
 
+// print list of contract paths and names.
+console.log('Contracts compiled:')
+console.log(Object.keys(res.contracts))
+
 // Get the contract's abi and bytecode.
 const {
   abi,