From e4ef46095651b527be226c62bb82cbbe2a40735f Mon Sep 17 00:00:00 2001 From: melissaml Date: Mon, 24 Sep 2018 18:51:16 +0800 Subject: [PATCH] Update the URL in doc Change-Id: I2bb2683a53b22e8aefffb3a7aa6c9cc1303ded7e --- HACKING.rst | 2 +- doc/source/contributor/coding.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/HACKING.rst b/HACKING.rst index bccc1b455..bda11bcbd 100644 --- a/HACKING.rst +++ b/HACKING.rst @@ -2,7 +2,7 @@ openstacksdk Style Commandments =============================== Read the OpenStack Style Commandments -http://docs.openstack.org/developer/hacking/ +https://docs.openstack.org/hacking/latest/ Indentation ----------- diff --git a/doc/source/contributor/coding.rst b/doc/source/contributor/coding.rst index 7ee1f557b..14ab10ff8 100644 --- a/doc/source/contributor/coding.rst +++ b/doc/source/contributor/coding.rst @@ -18,7 +18,7 @@ Below are the patterns that we expect openstacksdk developers to follow. Release Notes ============= -openstacksdk uses `reno `_ for +openstacksdk uses `reno `_ for managing its release notes. A new release note should be added to your contribution anytime you add new API calls, fix significant bugs, add new functionality or parameters to existing API calls, or make any