diff --git a/MinorReleases.md b/MinorReleases.md
index c08c99dd..2add7df9 100644
--- a/MinorReleases.md
+++ b/MinorReleases.md
@@ -12,7 +12,8 @@ The fix is developed for the main issue, which is closed when the fix is merged
 
 The child issue is assigned to the minor release milestone and labeled **CherryPickCandidate**, and its candidacy is discussed there. Once it is approved it transitions to **CherryPickApproved**. Release managers (a subset of the Go team that handles the release process) and/or code owners approve cherry-picks via an informal process.
 
-When the child issue is labeled **CherryPickApproved**, the original change author should immediately [create and mail a cherry-pick change](#making-cherry-pick-cls) against the release branch, which will be merged as soon as it is ready, closing the child issue.
+When the child issue is labeled **CherryPickApproved**, the original author of the change fixing
+that issue should immediately [create and mail a cherry-pick change](#making-cherry-pick-cls) against the release branch, which will be merged as soon as it is ready, closing the child issue.
 
 At release time, any open backport issue which is not release-blocker is pushed to the next minor release milestone, and a minor release is minted with the already merged changes.