diff --git a/doc/source/install/configure-nova-flavors.rst b/doc/source/install/configure-nova-flavors.rst
index d35748bcee..1b699775c0 100644
--- a/doc/source/install/configure-nova-flavors.rst
+++ b/doc/source/install/configure-nova-flavors.rst
@@ -90,10 +90,10 @@ Note how ``baremetal.with-GPU`` in the node's ``resource_class`` field becomes
 Scheduling based on traits
 --------------------------
 
-Starting with the Queens release, the Compute service supports scheduling based
-on qualitative attributes using traits.  Starting with Bare Metal REST API
-version 1.37, it is possible to assign a list of traits to each bare metal
-node.  Traits assigned to a bare metal node will be assigned to the
+The Compute service supports scheduling based on qualitative attributes
+using traits.  Starting with Bare Metal REST API version 1.37,
+it is possible to assign a list of traits to each bare metal node.
+Traits assigned to a bare metal node will be assigned to the
 corresponding resource provider in the Compute service placement API.
 
 When creating a flavor in the Compute service, required traits may be specified
diff --git a/doc/source/install/configure-pxe.rst b/doc/source/install/configure-pxe.rst
index a02851582d..53b650c3d7 100644
--- a/doc/source/install/configure-pxe.rst
+++ b/doc/source/install/configure-pxe.rst
@@ -482,10 +482,10 @@ be aborted, and the node will be moved to the ``deploy failed`` state, after
 the deploy callback timeout. This timeout can be changed via the
 :oslo.config:option:`conductor.deploy_callback_timeout` configuration option.
 
-Starting with the Train release, the Bare Metal service can retry PXE boot if
-it takes too long. The timeout is defined via
-:oslo.config:option:`pxe.boot_retry_timeout` and must be smaller than the
-``deploy_callback_timeout``, otherwise it will have no effect.
+The Bare Metal service can retry PXE boot if it takes too long.
+The timeout is defined via :oslo.config:option:`pxe.boot_retry_timeout`
+and must be smaller than the ``deploy_callback_timeout``,
+otherwise it will have no effect.
 
 For example, the following configuration sets the overall timeout to 60
 minutes, allowing two retries after 20 minutes:
diff --git a/doc/source/install/enabling-drivers.rst b/doc/source/install/enabling-drivers.rst
index 81c1b91788..b96fb81129 100644
--- a/doc/source/install/enabling-drivers.rst
+++ b/doc/source/install/enabling-drivers.rst
@@ -12,9 +12,8 @@ in a vendor-specific way. There are generic **hardware types** (eg.
 ``irmc``).
 
 .. note::
-   Starting with the Rocky release, the terminologies *driver*,
-   *dynamic driver*, and *hardware type* have the same meaning
-   in the scope of Bare Metal service.
+   The terminologies *driver*, *dynamic driver*, and *hardware type*
+   have the same meaning in the scope of Bare Metal service.
 
 .. _enable-hardware-types: