doc: wrap releases.md at 80 chars · nodejs/node@9e994cb
@@ -88,8 +88,8 @@ least one business day in advance of the expected release. Coordinating with
8888Build is essential to make sure that the CI works, release files are published,
8989and the release blog post is available on the project website.
909091-Build can be contacted best by opening up an issue on the [Build issue tracker][],
92-and by posting in `#node-build` on [webchat.freenode.net][].
91+Build can be contacted best by opening up an issue on the [Build issue
92+tracker][], and by posting in `#node-build` on [webchat.freenode.net][].
93939494When preparing a security release, contact Build at least two weekdays in
9595advance of the expected release. To ensure that the security patch(es) can be
@@ -524,7 +524,8 @@ To announce the build on Twitter through the official @nodejs account, email
524524525525To ensure communication goes out with the timing of the blog post, please allow
52652624 hour prior notice. If known, please include the date and time the release
527-will be shared with the community in the email to coordinate these announcements.
527+will be shared with the community in the email to coordinate these
528+announcements.
528529529530### 16. Cleanup
530531