Changes based on feedback

Signed-off-by: Andre Wanlin <awanlin@spotify.com>

docs/tutorials/yarn-migration.md

@@ -1,12 +1,10 @@
 ---
 id: yarn-migration
-title: Migration to Yarn 3
-description: Guide for how to migrate a Backstage project to use Yarn 3
+title: Migration to Yarn 4
+description: Guide for how to migrate a Backstage project to use Yarn 4
 ---
 
-While Backstage projects created with `@backstage/create-app` use [Yarn 1](https://classic.yarnpkg.com/) by default, it
-is possible to switch them to instead use [Yarn 3](https://yarnpkg.com/). Tools like `yarn backstage-cli versions:bump` will
-still work, as they recognize both lockfile formats.
+Backstage projects created with `@backstage/create-app` now use [Yarn 4](https://yarnpkg.com/), you may have a previous version of Backstage that is still using [Yarn 1](https://classic.yarnpkg.com/) that you'll want to migrate, this tutorial will help you with this task.
 
 ## Migration
 
@@ -19,7 +17,7 @@ First off, be sure to have the updated ignore entries in your app. These are inc
 Add the following to `.gitignore`:
 
 ```gitignore
-# Yarn 3 files
+# Yarn files
 .pnp.*
 .yarn/*
 !.yarn/patches
@@ -38,12 +36,18 @@ And this to `.dockerignore`:
 
 ### Installation
 
-Let's move on to the actual installation. We'd recommend making separate Git commits of most of these steps, in case you need to go back and debug anything. To install Yarn 3, run the following command in the project root:
+Let's move on to the actual installation. We'd recommend making separate Git commits of most of these steps, in case you need to go back and debug anything. To install Yarn 4, run the following command in the project root:
 
 ```bash
-yarn set version 3.x
+yarn set version 4.x
 ```
 
+:::note
+
+If the above command doesn't work then you may need to run `yarn set version latest` but use this with caution as it may take you to a version beyond Yarn 4
+
+:::
+
 We'll need the Yarn workspace tools plugin later on, so let's install that too:
 
 ```bash
@@ -56,23 +60,23 @@ In case you had a `.yarnrc` you can delete it now, but be sure to migrate over a
 
 ### Migrate Usage
 
-At this point you'll be all set up with Yarn 3! What remains is to migrate any usage of Yarn according to their [migration guide](https://yarnpkg.com/getting-started/migration). For example, any `yarn install --frozen-lockfile` commands should be replaced with `yarn install --immutable`.
+At this point you'll be all set up with Yarn 4! What remains is to migrate any usage of Yarn according to their [migration guide](https://yarnpkg.com/getting-started/migration). For example, any `yarn install --frozen-lockfile` commands should be replaced with `yarn install --immutable`.
 
-You'll also need to update any `Dockerfile`s to add instructions to copy in your Yarn 3 installation into the image:
+You'll also need to update any `Dockerfile`s to add instructions to copy in your Yarn 4 installation into the image:
 
 ```Dockerfile
 COPY .yarn ./.yarn
 COPY .yarnrc.yml ./
 ```
 
-In a multi-stage `Dockerfile`, each stage that runs a `yarn` command will also need the Yarn 3 installation. For example, in the final stage you may need to add the following:
+In a multi-stage `Dockerfile`, each stage that runs a `yarn` command will also need the Yarn 4 installation. For example, in the final stage you may need to add the following:
 
 ```Dockerfile
 COPY --from=build --chown=node:node /app/.yarn ./.yarn
 COPY --from=build --chown=node:node /app/.yarnrc.yml  ./
 ```
 
-The `--production` flag to `yarn install` has been removed in Yarn 3, instead you need to use `yarn workspaces focus --all --production` to avoid installing development dependencies in your production deployment. A tradeoff of this is that `yarn workspaces focus` does not support the `--immutable` flag.
+The `--production` flag to `yarn install` has been removed in Yarn 4, instead you need to use `yarn workspaces focus --all --production` to avoid installing development dependencies in your production deployment. A tradeoff of this is that `yarn workspaces focus` does not support the `--immutable` flag.
 
 ```Dockerfile
 RUN yarn workspaces focus --all --production && rm -rf "$(yarn cache clean)"
@@ -81,8 +85,6 @@ RUN yarn workspaces focus --all --production && rm -rf "$(yarn cache clean)"
 Additionally, `yarn config` has been reworked from being able to store any arbitrary key-value pairs to only supporting a handful of predefined pairs. Previously, we would set our preferred `python3` interpreter to work around [any issues related to node-gyp](https://github.com/backstage/backstage/issues/11583) so we need to provide an appropriate substitute.
 
 ```Dockerfile
-FROM node:16-bullseye-slim
-
 # highlight-add-start
 # Set Python interpreter for `node-gyp` to use
 ENV PYTHON=/usr/bin/python3