README: parallel build example link, zeppelin E2E dev note

docs/faq.md

@@ -43,7 +43,7 @@ before_script:
 after_script:                                               
   - npm run coverage && cat coverage/lcov.info | coveralls
 ```
-**NB:** It's probably best practice to run coverage in CI as an `after_script` rather than assume its equivalence to `truffle test`. Solidity-coverage's `testrpc` uses gasLimits far above the current blocklimit and rewrites your contracts in ways that might affect their behavior. It's also less robust than Truffle and may fail more frequently. 
+**NB:** It's probably best practice to run coverage in CI as an `after_script` or in a [parallel build](https://github.com/OpenZeppelin/zeppelin-solidity/blob/master/.travis.yml) rather than assume its equivalence to `truffle test`. Solidity-coverage's `testrpc` uses gasLimits far above the current blocklimit and rewrites your contracts in ways that might affect their behavior. It's also less robust than Truffle and may fail more frequently. 
 
 **Step 4: Toggle the project on at Travis and Coveralls and push.** 
 

docs/testrpc-sc.md

@@ -59,7 +59,15 @@ also contains things like the runState and the logs: ex: `results.vm.runState.lo
 There's no reason to worry about changing ethereumjs-vm-sc at master. If that affects anyone (unlikely)
 they have safe harbour at any solidity-coverage installation @0.1.9 and up. They can update. 
 
+### E2E Testing
 
+[sc-forks/zeppelin-solidity](https://github.com/sc-forks/zeppelin-solidity) has been configured to 
+serve as a simple pre-publication E2E test. By default the package pulls solidity-coverage from the repo's master branch. 
+You can trigger a [CI build](https://travis-ci.org/sc-forks/zeppelin-solidity) and [Coveralls report](https://coveralls.io/github/sc-forks/zeppelin-solidity) by running:
+
+```
+$ npm run ci
+```