diff --git a/doc/source/open-community.rst b/doc/source/open-community.rst
index 2223d99..96214e5 100644
--- a/doc/source/open-community.rst
+++ b/doc/source/open-community.rst
@@ -125,7 +125,8 @@ of elected technical positions in OpenStack:
 
 The *project team* guide naturally focuses on PTLs. More information about the
 TC can be found on the `Technical Committee website`_. You can reach out to
-TC members using the openstack-dev mailing-list (with the [tc] prefix), or
+TC members using the openstack-dev mailing-list (including the ``[tc]`` "tag"
+in your subject line will make it more likely for them to see the message), or
 on the #openstack-tc IRC channel (especially around `TC office hours`_).
 
 Each project team in OpenStack needs a PTL. The PTL is an elected leader who
diff --git a/doc/source/release-management.rst b/doc/source/release-management.rst
index ccee7e3..8daad66 100644
--- a/doc/source/release-management.rst
+++ b/doc/source/release-management.rst
@@ -109,7 +109,7 @@ the team decided to more directly handle release management.
 Projects following this model do not use intermediary development milestones.
 They may request publication of versions at any point in time during the
 development cycle. They do not use Feature Freeze, they do not go through a
-release candidate cycle. Every tag is a release supposed to be consumable by
+release candidate cycle. Every tag is a release that should be be consumable by
 users. They use a post-version semver-based numbering scheme, where every tag
 is a X.Y.Z version.