community-translations-standard moved

Author: ericherman

activities/releasing-the-standard/index.md

@@ -27,5 +27,5 @@ Follow the [instructions](https://github.com/publiccodenet/standard/blob/develop
 * Bring up as news in the next [community call](../community-calls/index.md).
 * Send new printed standards to firesouls.
 * Offer to mail a printed copy to each new contributor.
-* Give guidance on how to update the [community translations of the standard](https://github.com/publiccodenet/community-translations-standard) by sending a link with the comparison of the latest tag and the tag of the current translation.
+* Give guidance on how to update the [community translations of the standard](https://github.com/standard-for-public-code/community-translations-standard) by sending a link with the comparison of the latest tag and the tag of the current translation.
 * Update the [Community implementation guide](https://github.com/publiccodenet/community-implementation-guide-standard). The patch for the [assessment update](assessment-update.md) might be useful.

organization/annual-reports/annual-report-2021.md

@@ -81,7 +81,7 @@ As a public benefit organization and with the [KBFUS Public Code US fund](https:
 
 ### The Standard for Public Code
 
-In 2021, the Standard continued to prove its value to public code communities. Developers from three codebases worked with Foundation for Public Code stewards to evaluate their codebases with the Standard. Additionally, the stewards  discussed the self evaluations performed by developers of two other codebases. Responding to community requests, we established a [process for unofficial community translations of the Standard](https://publiccodenet.github.io/community-translations-standard/README.html) into other languages. It is already [translated into Spanish](https://publiccodenet.github.io/community-translations-standard/es/).
+In 2021, the Standard continued to prove its value to public code communities. Developers from three codebases worked with Foundation for Public Code stewards to evaluate their codebases with the Standard. Additionally, the stewards  discussed the self evaluations performed by developers of two other codebases. Responding to community requests, we established a [process for unofficial community translations of the Standard](https://standard-for-public-code.github.io/community-translations-standard/README.html) into other languages. It is already [translated into Spanish](https://standard-for-public-code.github.io/community-translations-standard/es/).
 
 In July, the Standard for Public Code was recognized as a [Digital Public Goods](https://digitalpublicgoods.net/) by the Digital Public Goods Alliance, a multi-stakeholder initiative endorsed by the United Nations Secretary-General’s Roadmap for Digital Cooperation.
 

organization/annual-reports/annual-report-2022.md

@@ -62,7 +62,7 @@ In 2022, we:
 
 * [launched a community-built implementation guide](https://blog.publiccode.net/news/2022/09/13/launching-community-built-implementation-guide.html)
 * released 4 iterations, going from version 0.2.3 to 0.4.1 - including adding a new findability criterion and clarifying that policy doesn’t need to be fully translated to English, both based on community feedback
-* launched [a home for community translations of the Standard](https://publiccodenet.github.io/community-translations-standard/)
+* launched [a home for community translations of the Standard](https://standard-for-public-code.github.io/community-translations-standard/)
 * launched a simple [assessment eligibility tool](https://publiccodenet.github.io/assessment-eligibility)
 * had 3 new contributors