Continuous-Integration-setup.md

 Continuous Integration (or CI for short) is the automated checking of code as it is added to the repository. For WP43 we attempt to build the simulator for Windows, macOS, and Ubuntu; build the firmware for the DM42; build and run the tests; and check that the code documentation can be built. This is done for every commit added to the repository on any branch. If any of these fail an e-mail is sent to the relevant person who added the commit so they know that there is a problem with their commit that they need to fix.
 
-The [CI page for the project](https://gitlab.com/Over_score/wp43s/-/pipelines) shows the build process for each commit (the 'pipeline') and the individual steps can be seen by selecting a pipeline. This process relies on 'runners' which are machines that have been set-up to perform these steps. GitLab supplies some 'shared runners', but these are not easily adapted to our needs, so instead we rely on WP43 developers to allow their machines to be always on and running the GitLab runner so these tasks can be performed. The load on the machines is very small, but we ideally need two for macOS and Windows to ensure every platform can be built.
+The [CI page for the project](https://gitlab.com/wpcalculators/wp43/-/pipelines) shows the build process for each commit (the 'pipeline') and the individual steps can be seen by selecting a pipeline. This process relies on 'runners' which are machines that have been set-up to perform these steps. GitLab supplies some 'shared runners', but these are not easily adapted to our needs, so instead we rely on WP43 developers to allow their machines to be always on and running the GitLab runner so these tasks can be performed. The load on the machines is very small, but we ideally need two for macOS and Windows to ensure every platform can be built.
 
 The Linux build, DM42 firmware, tests, and code documentation can all be built on GitLab shared runners.