diff --git a/docs/next/performance.html b/docs/next/performance.html
index 45ba5302fac..d8a6adfae24 100644
--- a/docs/next/performance.html
+++ b/docs/next/performance.html
@@ -360,7 +360,7 @@ fs.writeFile(<span class="hljs-string">'./packager/modulePaths.js'</span>, fileD
   <span class="hljs-built_in">console</span>.log(<span class="hljs-string">'Done'</span>);
 });
 </code></pre>
-<p>You can run via <code>node packager/modulePaths.js</code>.</p>
+<p>You can run via <code>node packager/generateModulePaths.js</code>.</p>
 <p>This script attempts to map from the module names to module paths. Its not foolproof though, for instance, it ignores platform specific files (*ios.js, and *.android.js). However based on initial testing, it handles 95% of cases. When it runs, after some time it should complete and output a file named <code>packager/modulePaths.js</code>. It should contain paths to module files that are relative to your projects root. You can commit modulePaths.js to your repo so it is transportable.</p>
 <h3><a class="anchor" aria-hidden="true" id="updating-the-configjs"></a><a href="#updating-the-configjs" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Updating the config.js</h3>
 <p>Returning to packager/config.js we should update it to use our newly generated modulePaths.js file.</p>
diff --git a/docs/next/performance/index.html b/docs/next/performance/index.html
index 45ba5302fac..d8a6adfae24 100644
--- a/docs/next/performance/index.html
+++ b/docs/next/performance/index.html
@@ -360,7 +360,7 @@ fs.writeFile(<span class="hljs-string">'./packager/modulePaths.js'</span>, fileD
   <span class="hljs-built_in">console</span>.log(<span class="hljs-string">'Done'</span>);
 });
 </code></pre>
-<p>You can run via <code>node packager/modulePaths.js</code>.</p>
+<p>You can run via <code>node packager/generateModulePaths.js</code>.</p>
 <p>This script attempts to map from the module names to module paths. Its not foolproof though, for instance, it ignores platform specific files (*ios.js, and *.android.js). However based on initial testing, it handles 95% of cases. When it runs, after some time it should complete and output a file named <code>packager/modulePaths.js</code>. It should contain paths to module files that are relative to your projects root. You can commit modulePaths.js to your repo so it is transportable.</p>
 <h3><a class="anchor" aria-hidden="true" id="updating-the-configjs"></a><a href="#updating-the-configjs" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Updating the config.js</h3>
 <p>Returning to packager/config.js we should update it to use our newly generated modulePaths.js file.</p>