update links to versioning doc

zeke · zeke · commit fa09ff3cbb07 · 2017-12-06T15:01:09.000-08:00
diff --git a/docs/README.md b/docs/README.md
@@ -19,7 +19,7 @@ an issue:
 * [Glossary of Terms](glossary.md)
 * [Supported Platforms](tutorial/supported-platforms.md)
 * [Security](tutorial/security.md)
-* [Versioning](tutorial/versioning.md)
+* [Versioning](tutorial/electron-versioning.md)
 * [Application Distribution](tutorial/application-distribution.md)
 * [Mac App Store Submission Guide](tutorial/mac-app-store-submission-guide.md)
 * [Windows Store Guide](tutorial/windows-store-guide.md)
diff --git a/docs/development/releasing.md b/docs/development/releasing.md
@@ -11,7 +11,7 @@ This document describes the process for releasing a new version of Electron.
 Run `npm run prepare-release -- --notesOnly` to view auto generated release
 notes.  The notes generated should help you determine if this is a major, minor,
 patch, or beta version change. Read the
-[Version Change Rules](../tutorial/versioning.md#semver) for more information.
+[Version Change Rules](../tutorial/electron-versioning.md#semver) for more information.
 
 ## Run the prepare-release script
 The prepare release script will do the following:
@@ -206,7 +206,7 @@ release to npm.
 
 [the releases page]: https://github.com/electron/electron/releases
 [this bump commit]: https://github.com/electron/electron/commit/78ec1b8f89b3886b856377a1756a51617bc33f5a
-[versioning]: /docs/tutorial/versioning.md
+[versioning]: /docs/tutorial/electron-versioning.md
 
 ## Fix missing binaries of a release manually
 
