diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index cbc411b0aa..bb79ae2684 100644
--- a/docs/internals/howto-release-django.txt
+++ b/docs/internals/howto-release-django.txt
@@ -133,7 +133,7 @@ OK, this is the fun part, where we actually push out a release!
 #. Check `Jenkins`__ is green for the version(s) you're putting out. You
    probably shouldn't issue a release until it's green.
 
-   __ http://ci.djangoproject.com
+   __ http://djangoci.com
 
 #. A release always begins from a release branch, so you should make sure
    you're on a stable branch and up-to-date. For example::
diff --git a/docs/intro/contributing.txt b/docs/intro/contributing.txt
index 2e828de40d..b1fb7b0ef6 100644
--- a/docs/intro/contributing.txt
+++ b/docs/intro/contributing.txt
@@ -189,7 +189,7 @@ present in Django's official builds. If you click to view a particular build,
 you can view the "Configuration Matrix" which shows failures broken down by
 Python version and database backend.
 
-__ http://ci.djangoproject.com/
+__ http://djangoci.com
 
 .. note::