diff --git a/apps/site/pages/en/learn/diagnostics/flame-graphs.md b/apps/site/pages/en/learn/diagnostics/flame-graphs.md index 5ebdd3062bd9c..53245fef7cb35 100644 --- a/apps/site/pages/en/learn/diagnostics/flame-graphs.md +++ b/apps/site/pages/en/learn/diagnostics/flame-graphs.md @@ -34,9 +34,9 @@ Now let's get to work. 2. Try running `perf` - it might complain about missing kernel modules, install them too 3. Run node with perf enabled (see [perf output issues](#perf-output-issues) for tips specific to Node.js versions) - ``` - perf record -e cycles:u -g -- node --perf-basic-prof --interpreted-frames-native-stack app.js - ``` +```bash +perf record -e cycles:u -g -- node --perf-basic-prof --interpreted-frames-native-stack app.js +``` 4. Disregard warnings unless they're saying you can't run perf due to missing packages; you may get some warnings about not being able to access kernel module samples which you're not after anyway. 5. Run `perf script > perfs.out` to generate the data file you'll visualize in a moment. It's useful to [apply some cleanup](#filtering-out-nodejs-internal-functions) for a more readable graph diff --git a/apps/site/pages/en/learn/getting-started/userland-migrations.md b/apps/site/pages/en/learn/getting-started/userland-migrations.md index fa99afcbf2cb2..374648ff72a04 100644 --- a/apps/site/pages/en/learn/getting-started/userland-migrations.md +++ b/apps/site/pages/en/learn/getting-started/userland-migrations.md @@ -4,8 +4,6 @@ layout: learn authors: JakobJingleheimer, AugustinMauroy --- -![Node.js Userland Migrations](https://raw.githubusercontent.com/nodejs/userland-migrations/8fd9c141a118c4b64cc37eed8e663005cbc819ac/.github/assets/Userland-Migration-Tagline.png) - # Userland Migrations Node.js offers migrations for "userland" code (anything outside the node executable) to help adopt new features and handle breaking changes. These are built in collaboration with [Codemod](https://codemod.com), a platform focused on making it easy to build, share, and run codemods.