diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3765106bc4ccc..dbc416a8d278c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,9 @@
+## [Unreleased]
+<details>
+ <summary>Changes that have landed in master but are not yet released.</summary>
+  Nothing yet! TODO: backfill this section.
+</details>
+
 ## 15.5.0 (April 7, 2017)
 
 ### React
diff --git a/docs/contributing/how-to-contribute.md b/docs/contributing/how-to-contribute.md
index 3403ca379e407..aa04d41666471 100644
--- a/docs/contributing/how-to-contribute.md
+++ b/docs/contributing/how-to-contribute.md
@@ -79,12 +79,13 @@ The core team is monitoring for pull requests. We will review your pull request
 1. Fork [the repository](https://github.com/facebook/react) and create your branch from `master`.
 2. If you've added code that should be tested, add tests!
 3. If you've changed APIs, update the documentation.
-4. Ensure the test suite passes (`npm test`).
-5. Make sure your code lints (`npm run lint`).
-6. Format your code with [prettier](https://github.com/prettier/prettier) (`npm run prettier`).
-7. Run the [Flow](https://flowtype.org/) typechecks (`npm run flow`).
-8. If you added or removed any tests, run `./scripts/fiber/record-tests` before submitting the pull request, and commit the resulting changes.
-9. If you haven't already, complete the CLA.
+4. If you have made any significant change then please [add an update to the "Unreleased" section of the change log](https://github.com/facebook/react/blob/master/CHANGELOG.md#unreleased). You may skip this step if you made documentation or dependency updates.
+5. Ensure the test suite passes (`npm test`).
+6. Make sure your code lints (`npm run lint`).
+7. Format your code with [prettier](https://github.com/prettier/prettier) (`npm run prettier`).
+8. Run the [Flow](https://flowtype.org/) typechecks (`npm run flow`).
+9. If you added or removed any tests, run `./scripts/fiber/record-tests` before submitting the pull request, and commit the resulting changes.
+10. If you haven't already, complete the CLA.
 
 ### Contributor License Agreement (CLA)