diff --git a/doc/source/gmr.rst b/doc/source/gmr.rst
index 4fadd56cc9e9..93250be45466 100644
--- a/doc/source/gmr.rst
+++ b/doc/source/gmr.rst
@@ -47,7 +47,7 @@ Adding Support for GMRs to New Executables
 
 Adding support for a *GMR* to a given executable is fairly easy.
 
-First import the module (currently residing in oslo-incubator), as well as the Nova version module:
+First import the module, as well as the Nova version module:
 
 .. code-block:: python
 
diff --git a/doc/source/policy_enforcement.rst b/doc/source/policy_enforcement.rst
index 5f9c96f37425..732731448acc 100644
--- a/doc/source/policy_enforcement.rst
+++ b/doc/source/policy_enforcement.rst
@@ -92,7 +92,7 @@ layer to guarantee it won't break the back-compatibility. That may ugly
 some hard-code permission check in API layer, but V2 API will be removed
 once V2.1 API ready, so our choice will reduce the risk.
 
-Port policy.d from oslo-incubator into nova
+Port policy.d into nova
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 This feature make deployer can override default policy rule easily. And