diff --git a/doc/source/specs/pluggable_protection_provider.rst b/doc/source/specs/pluggable_protection_provider.rst
index 9e0c2cf1..3792f468 100644
--- a/doc/source/specs/pluggable_protection_provider.rst
+++ b/doc/source/specs/pluggable_protection_provider.rst
@@ -252,5 +252,5 @@ use this mechanism to only return tasks when appropriate for it's scheme.
 
 References
 ==========
-1. `Class Diagram Source <http://raw.githubusercontent.com/openstack/karbor/master/doc/images/specs/pluggable_protection_provider.pu>`_
+1. `Class Diagram Source <https://github.com/openstack/karbor/blob/master/doc/source/specs/pluggable_protection_provider.pu>`_
 2. `Dependency graph building algorithm <https://docs.google.com/document/d/1Mkd9RgUVdiRL6iei8Nqzzx4xteKIcd-yjMLEkV4Jc9s/edit#>`_
diff --git a/doc/source/specs/protection-service/restore-design-spec.rst b/doc/source/specs/protection-service/restore-design-spec.rst
index 8b2f532b..53ac1e00 100644
--- a/doc/source/specs/protection-service/restore-design-spec.rst
+++ b/doc/source/specs/protection-service/restore-design-spec.rst
@@ -29,7 +29,7 @@ holds our protection data, is high available and reliable.
 Restore from what point
 =======================
 
-In `document protection service design <https://raw.githubusercontent.com/openstack/karbor/master/doc/source/spes/protection-service/protection-service.rst>`_
+In `document protection service design <https://github.com/openstack/karbor/blob/master/doc/source/specs/protection-service/protection-service.rst>`_
 , we have described the procedure to protect resource, where for each protection
 plan execution, we will persist a checkpoint in bank.