From e19adedc38e5e3e11d224bbcf3ee861e1ec3c54b Mon Sep 17 00:00:00 2001
From: Steve Martinelli <s.martinelli@gmail.com>
Date: Wed, 8 Feb 2017 00:29:01 -0500
Subject: [PATCH] use the correct bp link for shadow-mapping rel note

Change-Id: I4531aeea8fd2b3648be1f3f9fab4ed1258be44e4
---
 releasenotes/notes/bp-shadow-mapping-06fc7c71a401d707.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/releasenotes/notes/bp-shadow-mapping-06fc7c71a401d707.yaml b/releasenotes/notes/bp-shadow-mapping-06fc7c71a401d707.yaml
index 9571b91ce7..03b61c648f 100644
--- a/releasenotes/notes/bp-shadow-mapping-06fc7c71a401d707.yaml
+++ b/releasenotes/notes/bp-shadow-mapping-06fc7c71a401d707.yaml
@@ -1,7 +1,7 @@
 ---
 features:
   - >
-    [`blueprint manage-migration <https://blueprints.launchpad.net/keystone/+spec/manage-migration>`_]
+    [`blueprint shadow-mapping <https://blueprints.launchpad.net/keystone/+spec/shadow-mapping>`_]
     The federated identity mapping engine now supports the ability to
     automatically provision ``projects`` for ``federated users``. A role assignment
     will automatically be created for the user on the specificed proejct. If the