Deploy website - based on 1784e1a

Author: facebook-github-bot

404.html

@@ -23,9 +23,9 @@ Our recommended workflow is to use [`yarn link`][1] to register local `metro` pa
     From inside our `metro` clone, `yarn link` is responsible for registering local package folders to be linked to elsewhere.
 
     We recommend using `npm exec --workspaces` to register all packages in the `metro` repo — these can be individually linked into the target project later.
-
-        npm exec --workspaces -- yarn link
-
+    ```sh
+    npm exec --workspaces -- yarn link
+    ```
 2. **Use `yarn link` to replace Metro packages in your target project**
 
     From inside our target project folder, `yarn link <package-name>` can be used to apply our registered `metro` packages for that project only.
@@ -59,7 +59,9 @@ Our recommended workflow is to use [`yarn link`][1] to register local `metro` pa
 
     Now we should be able to run Metro within our target project. Remember to restart this command after any code changes you make to `metro` or to the target project's `metro.config.js` file.
 
-        yarn react-native start
+   ```sh
+   yarn react-native start
+   ```
 
 4. **(Optional) Clean up with `yarn unlink`**
 
@@ -70,7 +72,7 @@ Our recommended workflow is to use [`yarn link`][1] to register local `metro` pa
 Metro uses the [debug](https://www.npmjs.com/package/debug) package to write logs under named debug scopes (for example: `Metro:WatchmanWatcher`). Set the `DEBUG` environment variable before starting Metro to enable logs matching the supplied pattern.
 
 The snippet below provides a pattern matching all Metro-defined messages.
-
-    DEBUG='Metro:*' yarn metro serve
-
+```sh
+DEBUG='Metro:*' yarn metro serve
+```
 [1]: https://classic.yarnpkg.com/en/docs/cli/link