diff --git a/packaging/building-a-package/en.md b/packaging/building-a-package/en.md
index 490004f..92e3b89 100644
--- a/packaging/building-a-package/en.md
+++ b/packaging/building-a-package/en.md
@@ -42,7 +42,7 @@ To update solbuild, run: `sudo solbuild update`
 
 Next you need to set up `common`, a set of make scripts that enables you to more easily manage, build, check, and publish packages.
 
-You need to clone the common repository with git `sudo eopkg it git` by doing `git clone https://git.solus-project.com/common` in the same directory you will have sub-folders for packages you are building.
+You need to clone the common repository with git `sudo eopkg it git` by doing `git clone https://dev.solus-project.com/source/common.git` in the same directory you will have sub-folders for packages you are building.
 
 Next you need to set up symlinks. Do this from the same directory you executed the `git` command:
 
@@ -77,7 +77,7 @@ make
 
 You will be prompted to enter your password by sudo so dependencies may be downloaded and the necessary eopkg files may be generated.
 
-You may find other `common` commands [here](https://git.solus-project.com/common/about/).
+You may find other `common` commands [here](https://dev.solus-project.com/source/common/browse/master/about/).
 
 Once you’ve achieved a successful build, the resulting `.eopkg` files will be moved to the current directory, along with the machine file, `pspec_*.xml` (currently `pspec_x86_64.xml`). We recommending checking the contents of your 
-generated eopkg file(s) to ensure everything is located in the appropriate locations. You can do this by using `lseopkg file_name.eopkg`.
\ No newline at end of file
+generated eopkg file(s) to ensure everything is located in the appropriate locations. You can do this by using `lseopkg file_name.eopkg`.
diff --git a/packaging/updating-an-existing-package/en.md b/packaging/updating-an-existing-package/en.md
index 736d66d..5ac0119 100644
--- a/packaging/updating-an-existing-package/en.md
+++ b/packaging/updating-an-existing-package/en.md
@@ -5,7 +5,7 @@ title = "Updating an Existing Package"
 
 This article will go over updating a package that is already in the Solus git repository.
 
-The instructions below assume you have cloned the package's repository using the http link provided on the respective git page, [for example nano](https://git.solus-project.com/packages/nano). The process for submitting an updated package is the same as if it is a new package. Follow the steps [here](/articles/packaging/submitting-a-package/en).
+The instructions below assume you have cloned the package's repository using the http link provided on the respective git page, [for example nano](https://dev.solus-project.com/source/nano/). The process for submitting an updated package is the same as if it is a new package. Follow the steps [here](/articles/packaging/submitting-a-package/en).
 
 ## Bumping a packaging
 
@@ -32,4 +32,4 @@ Example:
 
 ``` bash
 /usr/share/ypkg/yupdate.py 1.0 http://example.com/example-1.0.tar.xz
-```
\ No newline at end of file
+```
diff --git a/software/powerline-shell-prompt/en.md b/software/powerline-shell-prompt/en.md
index c6716b2..88b48a0 100644
--- a/software/powerline-shell-prompt/en.md
+++ b/software/powerline-shell-prompt/en.md
@@ -7,8 +7,8 @@ title = "Powerline Shell Prompt"
 
 ## Installation 
 
-Powerline has two components, the plugin system itself ([powerline](https://git.solus-project.com/packages/powerline/)) and the 
-fonts ([powerline-fonts](https://git.solus-project.com/packages/powerline-fonts)). Both are available in the Software Center or via eopkg in a terminal:
+Powerline has two components, the plugin system itself ([powerline](https://dev.solus-project.com/source/powerline/)) and the 
+fonts ([powerline-fonts](https://dev.solus-project.com/source/powerline-fonts/)). Both are available in the Software Center or via eopkg in a terminal:
 
 ``` bash
 sudo eopkg it powerline powerline-fonts