From ed6a5ff4b43130c4cd0684e7ebb2af7c18ff7d16 Mon Sep 17 00:00:00 2001 From: ChngYekKhai Date: Wed, 1 Aug 2018 07:10:42 -0700 Subject: [PATCH] Fix typo in Releases.md (#20487) Summary: Thank you for sending the PR! We appreciate you spending the time to work on these changes. Help us understand your motivation by explaining why you decided to make this change. If this PR fixes an issue, type "Fixes #issueNumber" to automatically close the issue when the PR is merged. Pull Request resolved: https://github.com/facebook/react-native/pull/20487 Differential Revision: D9117645 Pulled By: hramos fbshipit-source-id: f1fc725b28ed606175baba19fa165a7add12da43 --- Releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Releases.md b/Releases.md index 0e9492cfd..f9bab35ab 100644 --- a/Releases.md +++ b/Releases.md @@ -65,7 +65,7 @@ Circle CI will automatically run the tests and publish to npm with the version y ### Step 3: Write the release notes -Write the release notes, or post in [React Native Core Contributors](https://www.facebook.com/groups/reactnativeoss/) that the RC is ready to find a voluteer. You can also use [react-native-release-notes](https://github.com/knowbody/react-native-release-notes) to generate a draft of release notes. +Write the release notes, or post in [React Native Core Contributors](https://www.facebook.com/groups/reactnativeoss/) that the RC is ready to find a volunteer. You can also use [react-native-release-notes](https://github.com/knowbody/react-native-release-notes) to generate a draft of release notes. To go through all the commits that went into a release, one way is to use the GitHub compare view: