diff --git a/doc/source/oslo.rst b/doc/source/oslo.rst
index 24e534d..a478176 100644
--- a/doc/source/oslo.rst
+++ b/doc/source/oslo.rst
@@ -49,9 +49,9 @@ team:
   which in turn makes it easier to post-process the logs with tools
   like Logstash.
 
-.. _oslo.config: http://docs.openstack.org/developer/oslo.config/
-.. _oslo.messaging: http://docs.openstack.org/developer/oslo.messaging/
-.. _oslo.log: http://docs.openstack.org/developer/oslo.log/
+.. _oslo.config: https://docs.openstack.org/oslo.config/latest/
+.. _oslo.messaging: https://docs.openstack.org/oslo.messaging/latest/
+.. _oslo.log: https://docs.openstack.org/oslo.log/latest
 
 Brief History
 =============
diff --git a/doc/source/release-management.rst b/doc/source/release-management.rst
index c6255fd..2a61a93 100644
--- a/doc/source/release-management.rst
+++ b/doc/source/release-management.rst
@@ -584,7 +584,7 @@ will be no merge conflicts as the fix is backported. For example:
 After the new file is created, edit it to remove any sections that are
 not relevant and to add notes under the appropriate sections. Refer to
 the `Editing a Release Note
-<https://docs.openstack.org/developer/reno/user/usage.html#creating-new-release-notes>`__
+<https://docs.openstack.org/reno/latest/#creating-new-release-notes>`__
 section of the reno documentation for details about what should go in
 each section of the YAML file and for tips on formatting notes.