Update README

README.md

@@ -1,12 +1,12 @@
-### lunchcoin
+## lunchcoin
 
-## NB Accessing the app on heroku gives heroku's 'Application error' when starting cold. Just refresh the page!
+#### NB Accessing the app on heroku gives heroku's 'Application error' when starting cold. Just refresh the page!
 
-[Fake Rep mining page (this will eventually be done by accredited 'stars')](https://lunchcoin-v1.herokuapp.com/mine)
+[Rep 'mining' page (this will eventually be replaced by using accredited 'stars')](https://lunchcoin.xyz/mine)
 
-[Fake Rep staking page (this will eventually be done using the Doodle overlay proxy)](https://lunchcoin-v1.herokuapp.com/stake)
+[Rep staking page (this will eventually be done using the Doodle overlay proxy)](https://lunchcoin.xyz/stake)
 
-[App](https://lunchcoin-v1.herokuapp.com/)
+[App](https://lunchcoin.xyz/)
 
 #### Installation
 Let's assume you'll want truffle and ganache-cli installed globally
@@ -49,16 +49,17 @@ Don't attempt to deploy the entire branch, as it will be a pain to remove. You n
 
 
 #### Troubleshooting
-If the app chokes on on network constants being undefined, check your `network` in `truffle-config.js` (if set), check whether React components use `app/src/src_testing/Web3/adminPanel.js` or `app/src/Web3/accessChain.js` (usually the correct one ;) and whether that file and `providerUrl` match your ganache URL (which is running, right? You do have a blockchain running?)
-Alternatively, this may be a migration problem (eg due to async errors) which can fail silently during migration or remigration. Look in the console for whether all, or only some, artifacts are missing the correct network. After fixing any possbile problems, make sure to use ```truffle migrate --reset``` to explicitly rebuild.
+* If the app chokes on on network constants being undefined, check your `network` in `truffle-config.js` (if set), check whether React components use `app/src/src_testing/Web3/adminPanel.js` or `app/src/Web3/accessChain.js` (usually the correct one ;) and whether that file and `providerUrl` match your ganache URL (which is running, right? You do have a blockchain running?)
 
-If only the function accessor frontend shows, check index.html and index.js. They may be pointing to `<TestingApp>`.
+* Alternatively, this may be a migration problem (eg due to async errors) which can fail silently during migration or remigration. Look in the console for whether all, or only some, artifacts are missing the correct network. After fixing any possbile problems, make sure to use ```truffle migrate --reset``` to explicitly rebuild.
 
-If, after editing the metacode of a contract (ie types, visibility, rather than instructions) and recompiling, the contract gives the same erros as previously, or new VM errors, you must run `truffle compile --all` and not just `truffle migrate --reset`. Check in the output that recompliation is actually happening and if not, remove the artifacts of any contracts which were changed from `app/src/contracts` before migrating again (`./rm_app_src_contracts` will do this if it has appropriate file permissions)
+* If only the function accessor frontend shows, check index.html and index.js. They may be pointing to `<TestingApp>`.
 
-Consider always passing explicit compiler and EVM versions to truffle (as well as to compiler) as there have been unexplained VM errors.
+* If, after editing the metacode of a contract (ie types, visibility, rather than instructions) and recompiling, the contract gives the same erros as previously, or new VM errors, you must run `truffle compile --all` and not just `truffle migrate --reset`. Check in the output that recompliation is actually happening and if not, remove the artifacts of any contracts which were changed from `app/src/contracts` before migrating again (`./rm_app_src_contracts` will do this if it has appropriate file permissions)
 
-Oops, I pushed the whole branch, not the subtree :open_mouth:
+* Consider always passing explicit compiler and EVM versions to truffle (as well as to compiler) as there have been unexplained VM errors.
+
+* 'Oops, I pushed the whole branch, not the subtree :open_mouth:'   ...   then run:
 ```
 git push heroku `git subtree split --prefix app master`:master --force
 ```