diff --git a/docs/next/upgrading.html b/docs/next/upgrading.html index e1bbd9b0e78..5a19e8e32b6 100644 --- a/docs/next/upgrading.html +++ b/docs/next/upgrading.html @@ -111,7 +111,7 @@ npm WARN peerDependencies The peer dependency react@~R included from react-nativ
The new npm package may contain updates to the files that are normally generated when you run react-native init, like the iOS and the Android sub-projects.
You may consult rn-diff to see if there were changes in the project template files. In case there weren't any, simply rebuild the project and continue developing. In case of minor changes, you may update your project manually and rebuild.
+You may consult rn-diff-purge to see if there were changes in the project template files. In case there weren't any, simply rebuild the project and continue developing. In case of minor changes, you may update your project manually and rebuild.
If there were major changes, run this in a terminal to get these:
$ react-native upgrade
diff --git a/docs/next/upgrading/index.html b/docs/next/upgrading/index.html
index e1bbd9b0e78..5a19e8e32b6 100644
--- a/docs/next/upgrading/index.html
+++ b/docs/next/upgrading/index.html
@@ -111,7 +111,7 @@ npm WARN peerDependencies The peer dependency react@~R included from react-nativ
The new npm package may contain updates to the files that are normally generated when you run react-native init, like the iOS and the Android sub-projects.
You may consult rn-diff to see if there were changes in the project template files. In case there weren't any, simply rebuild the project and continue developing. In case of minor changes, you may update your project manually and rebuild.
+You may consult rn-diff-purge to see if there were changes in the project template files. In case there weren't any, simply rebuild the project and continue developing. In case of minor changes, you may update your project manually and rebuild.
If there were major changes, run this in a terminal to get these:
$ react-native upgrade