diff --git a/HACKING.rst b/HACKING.rst
index da6bfb6..5cfac09 100644
--- a/HACKING.rst
+++ b/HACKING.rst
@@ -1,4 +1,4 @@
 fuxi Style Commandments
 ===============================================
 
-Read the OpenStack Style Commandments https://docs.openstack.org/developer/hacking/
+Read the OpenStack Style Commandments https://docs.openstack.org/hacking/latest/
diff --git a/README.rst b/README.rst
index 0b08335..41ea4bf 100644
--- a/README.rst
+++ b/README.rst
@@ -20,7 +20,7 @@ the unified persistence storage provider for virtual machine, baremetal
 and Docker container.
 
 * Free software: Apache license
-* Documentation: https://docs.openstack.org/developer/fuxi
+* Documentation: https://docs.openstack.org/fuxi/latest/
 * Source: https://git.openstack.org/cgit/openstack/fuxi
 * Bugs: https://bugs.launchpad.net/fuxi
 * Blueprints: https://blueprints.launchpad.net/fuxi
diff --git a/doc/source/devref/manila_provider.rst b/doc/source/devref/manila_provider.rst
index 32c0249..250437b 100644
--- a/doc/source/devref/manila_provider.rst
+++ b/doc/source/devref/manila_provider.rst
@@ -98,4 +98,4 @@ References
 
 * `Manila share features support mapping`_
 
-.. _Manila share features support mapping: https://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html
+.. _Manila share features support mapping: https://docs.openstack.org/manila/latest/devref/share_back_ends_feature_support_mapping.html
diff --git a/doc/source/reno.rst b/doc/source/reno.rst
index 4db8ab6..06db887 100644
--- a/doc/source/reno.rst
+++ b/doc/source/reno.rst
@@ -4,7 +4,7 @@ Release Notes
 What is reno ?
 --------------
 
-Fuxi uses `reno <http://docs.openstack.org/developer/reno/usage.html>`_ for
+Fuxi uses `reno <https://docs.openstack.org/reno/latest/user/usage.html>`_ for
 providing release notes in-tree. That means that a patch can include a *reno
 file* or a series can have a follow-on change containing that file explaining
 what the impact is.
@@ -19,7 +19,7 @@ generated using the reno tool this way:
 where usually ``<name-your-file>`` can be ``bp-<blueprint_name>`` for a
 blueprint or ``bug-XXXXXX`` for a bugfix.
 
-Refer to the `reno documentation <http://docs.openstack.org/developer/reno/usage.html#editing-a-release-note>`_
+Refer to the `reno documentation <https://docs.openstack.org/reno/latest/user/usage.html#editing-a-release-note>`_
 for the full list of sections.