diff --git a/docs/docsite/.templates/banner.html b/docs/docsite/.templates/banner.html
index 388152211d5..698870fedc1 100644
--- a/docs/docsite/.templates/banner.html
+++ b/docs/docsite/.templates/banner.html
@@ -20,7 +20,10 @@
       '<div id="latest_extra_banner_id" class="admonition important">' +
       '<br>' +
       '<p>' +
-        'Continue building on your automation knowledge, visit the <a href="https://events.experiences.redhat.com/widget/redhat/rhaf22/SessionCatalog2022">AnsibleFest content hub!</a>  ' +
+        '<b>Experience AnsibleFest at Red Hat Summit</b>' +
+      '</p>' +
+      '<p>' +
+        'We\'re bringing AnsibleFest to Red Hat Summit in Boston, May 23-25. It\'s the best of Fest combined with Red Hat Summit for even more learning and technical engagement. <a href="https://www.redhat.com/en/summit/ansiblefest?intcmp=7013a0000034lvhAAA">Learn more.</a>  ' +
       
       '</p>' +
       '<br>' +
diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_7.rst b/docs/docsite/rst/roadmap/COLLECTIONS_7.rst
index ca763408759..dcd9262142b 100644
--- a/docs/docsite/rst/roadmap/COLLECTIONS_7.rst
+++ b/docs/docsite/rst/roadmap/COLLECTIONS_7.rst
@@ -46,7 +46,7 @@ Release schedule
 Ansible minor releases
 =======================
 
-Ansible 7.x minor releases will occur approximately every four weeks if changes to collections have been made or to align to a later ansible-core-2.14.x.  Ansible 7.x minor releases may contain new features but not backwards incompatibilities.  In practice, this means we will include new collection versions where either the patch or the minor version number has changed but not when the major number has changed. For example, if Ansible-7.0.0 ships with community.crypto 2.3.0; Ansible-6.1.0 may ship with community.crypto 2.4.0 but would not ship with community.crypto 3.0.0.
+Ansible 7.x minor releases will occur approximately every four weeks if changes to collections have been made or to align to a later ansible-core-2.14.x.  Ansible 7.x minor releases may contain new features but not backwards incompatibilities.  In practice, this means we will include new collection versions where either the patch or the minor version number has changed but not when the major number has changed. For example, if Ansible-7.0.0 ships with community.crypto 2.3.0; Ansible-7.1.0 may ship with community.crypto 2.4.0 but would not ship with community.crypto 3.0.0.
 
 
 .. note::