diff --git a/docs/data/how.md b/docs/data/how.md
index 2d9a1aeff24b5198fdbf8233420d9b8fd54919ce..0bfe0514139473385a52f787748914d2ee116d61 100644
--- a/docs/data/how.md
+++ b/docs/data/how.md
@@ -27,7 +27,7 @@ After these stages have been considered, one or a combination of the below [repo
 ## Contributor attribution
 Before you publish your data you should have an open and honest conversation about who has contributed to the data collection and processing, and agree how these individuals will be recognised and attributed for their work. This need not be the same list of individuals who are authors on any manuscript which references your data, indeed this can be a valuable opportunity to recognise the contributions of those who do not traditionally receive authorship on journal manuscripts (for example project managers, software engineers or data stewards).
 
-Consider creating a [Contributor Roles Taxonomy - CRediT](https://casrai.org/credit/) statement and sharing this with your published data. [Tenzing](https://rollercoaster.shinyapps.io/tenzing/) is a useful tool for collecting contributor information and generating the CRediT statement.
+Consider creating a [Contributor Roles Taxonomy - CRediT](https://credit.niso.org) statement and sharing this with your published data. [Tenzing](https://rollercoaster.shinyapps.io/tenzing/) is a useful tool for collecting contributor information and generating the CRediT statement.
 
 Aim to include the [ORCID](https://orcid.org) of all your contributors in your published metadata, so contributions can be traced back to the individual.