diff --git a/docs/core/release-process.md b/docs/core/release-process.md
index 667e0ac6200f46da43bdabaf0e603dd2b96461e5..86917be057abea97fafd904fe1230349caf14eed 100644
--- a/docs/core/release-process.md
+++ b/docs/core/release-process.md
@@ -1,10 +1,6 @@
 # Review/Release Process
 
-Releases are developed on a monthly cycle.  At the start of the month, the
-release-manager will send an invitation to developers who have open PRs,
-encouraging them to participate in the release-cycle.  Participation
-provides a way to exchange feedback with other developers, get PRs merged,
-and ensure the next release works -- all with a predictable timeline.
+Releases are developed on a monthly cycle.  At the start of the month, the release-manager will send an invitation to developers who have open PRs, encouraging them to participate in the release-cycle.  Participation provides a way to exchange feedback with other developers, get PRs merged, and ensure the next release works -- all with a predictable timeline.
 
 * For a high-level summary of the release process, see the [Release Management README](https://github.com/civicrm/release-management/blob/master/README.md).
 * For an example invitation, see the previous [invitation for the April-May 2016](https://github.com/civicrm/release-management/issues/1).