Merge branch 'update-10-02-2020' into 'master'

Update best_practices.md

See merge request zcash-docs/zcash-docs!226

source/rtd_pages/best_practices.md

@@ -4,7 +4,7 @@ We pledge to respect all contributors. In the interest of fostering an open and
 
 ## Development workflow
 
-The [Development workflow and guidelines](https://zcash.readthedocs.io/en/latest/rtd_pages/development_guidelines.html) will get you up to speed and contribute to Zcash projects. It talks about the Zcash Github workflow, which has a few quirks from the general git flow, how Zcash core developers code and test, and the nuts and bolts of operation (CI, versioning, and release process). 
+The [Development workflow and guidelines](development_guidelines.html) will get you up to speed and contribute to Zcash projects. It talks about the Zcash Github workflow, which has a few quirks from the general git flow, how Zcash core developers code and test, and the nuts and bolts of operation (CI, versioning, and release process). 
 
 ## Handling Zcash features
-The [Zcash feature UX checklist](https://zcash.readthedocs.io/en/latest/rtd_pages/ux_wallet_checklist.html) will give you an idea of how Zcash features are standardly treated, and how you should design for them. For instance, shielded addresses should be used long term, since using a new one per transaction (industry standard) does not provide additional privacy. These lessons learned over time will save you some technical complexity and support calls if you follow these guidelines. 
+The [Zcash feature UX checklist](ux_wallet_checklist.html) will give you an idea of how Zcash features are standardly treated, and how you should design for them. For instance, shielded addresses should be used long term, since using a new one per transaction (industry standard) does not provide additional privacy. These lessons learned over time will save you some technical complexity and support calls if you follow these guidelines.