Use release notes

RELEASING.md

@@ -13,10 +13,10 @@ When making a `.0` release, you will need to specify the minimum supported versi
 Prior to making a release,
 
 1. Go through the list of open pull requests and merge any that are ready for merging.
-2. Go through the list of closed pull requests since the last release and ensure those that should be included in the changelog:
+2. Go through the list of closed pull requests since the last release and ensure those that should be included in the release notes:
   - have a "bug", "enhancement" or "feature" label,
   - have a title that clearly describes the changes in that pull request. Reword if necessary.
-3. Perform a dry run (add `--dry-run` to one of the commands below) and verify the version strings are going to be changed and verify the changelog and release content.
+3. Perform a dry run (add `--dry-run` to one of the commands below) and verify the version strings are going to be changed and verify the release notes.
 
 ## Automatic Process from chatops (internal to GitHub only)
 
@@ -56,6 +56,6 @@ Immediately after making a release using one of the methods above, verify the re
 
 - latest release at https://github.com/github/backup-utils/releases is correct,
 - release at https://github.com/github/backup-utils/releases is linked to the vX.Y.Z tag,
-- release has the changelog notes you expect to see,
+- release has the notes you expect to see,
 - asset download links for the latest release at https://github.com/github/backup-utils/releases all download the correct version of Backup Utilities,
 - the stable branch is inline with master - https://github.com/github/backup-utils/compare/stable...master.