From d0da0b032346a6739609185dfd6ae4decafa0d68 Mon Sep 17 00:00:00 2001 From: melissaml Date: Mon, 24 Sep 2018 16:50:26 +0800 Subject: [PATCH] Update the url in doc Change-Id: Ifb2183870cff73c03c668926bad47bc131979918 --- 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 82e34ce37..099d3b80f 100644 --- a/HACKING.rst +++ b/HACKING.rst @@ -2,7 +2,7 @@ shade 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 26aa50cc7..5014d8d1d 100644 --- a/doc/source/contributor/coding.rst +++ b/doc/source/contributor/coding.rst @@ -18,7 +18,7 @@ Below are the patterns that we expect Shade developers to follow. Release Notes ============= -Shade uses `reno `_ for +Shade 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