diff --git a/docs/next/hermes.html b/docs/next/hermes.html
index 911a4823ce0..c2a988c1561 100644
--- a/docs/next/hermes.html
+++ b/docs/next/hermes.html
@@ -111,7 +111,7 @@
 <p>This will compile JavaScript to bytecode during build time which will improve your app's startup speed on device.</p>
 <h2><a class="anchor" aria-hidden="true" id="debugging-hermes-using-google-chromes-devtools"></a><a href="#debugging-hermes-using-google-chromes-devtools" 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>Debugging Hermes using Google Chrome's DevTools</h2>
 <p>Hermes supports the Chrome debugger by implementing the Chrome inspector protocol. This means Chrome's tools can be used to directly debug JavaScript running on Hermes, on an emulator or device.</p>
-<p>Chrome connects to Hermes running on device via Metro, so you'll need to know where Metro is listening. Typically this will be on <code>localhost:8081</code>, but this is <a href="https://facebook.github.io/metro/docs/en/configuration">configurable</a>. When running <code>yarn start</code> the address is written to stdout on startup.</p>
+<p>Chrome connects to Hermes running on device via Metro, so you'll need to know where Metro is listening. Typically this will be on <code>localhost:8081</code>, but this is <a href="https://facebook.github.io/metro/docs/configuration">configurable</a>. When running <code>yarn start</code> the address is written to stdout on startup.</p>
 <p>Once you know where the Metro server is listening, you can connect with Chrome using the following steps:</p>
 <ol>
 <li><p>Navigate to <code>chrome://inspect</code> in a Chrome browser instance.</p></li>
diff --git a/docs/next/hermes/index.html b/docs/next/hermes/index.html
index 911a4823ce0..c2a988c1561 100644
--- a/docs/next/hermes/index.html
+++ b/docs/next/hermes/index.html
@@ -111,7 +111,7 @@
 <p>This will compile JavaScript to bytecode during build time which will improve your app's startup speed on device.</p>
 <h2><a class="anchor" aria-hidden="true" id="debugging-hermes-using-google-chromes-devtools"></a><a href="#debugging-hermes-using-google-chromes-devtools" 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>Debugging Hermes using Google Chrome's DevTools</h2>
 <p>Hermes supports the Chrome debugger by implementing the Chrome inspector protocol. This means Chrome's tools can be used to directly debug JavaScript running on Hermes, on an emulator or device.</p>
-<p>Chrome connects to Hermes running on device via Metro, so you'll need to know where Metro is listening. Typically this will be on <code>localhost:8081</code>, but this is <a href="https://facebook.github.io/metro/docs/en/configuration">configurable</a>. When running <code>yarn start</code> the address is written to stdout on startup.</p>
+<p>Chrome connects to Hermes running on device via Metro, so you'll need to know where Metro is listening. Typically this will be on <code>localhost:8081</code>, but this is <a href="https://facebook.github.io/metro/docs/configuration">configurable</a>. When running <code>yarn start</code> the address is written to stdout on startup.</p>
 <p>Once you know where the Metro server is listening, you can connect with Chrome using the following steps:</p>
 <ol>
 <li><p>Navigate to <code>chrome://inspect</code> in a Chrome browser instance.</p></li>