docs(site): update getting started guide

Author: JamieMason

site/src/content/docs/guide/getting-started.mdx

@@ -23,14 +23,14 @@ Some of the things it can do are:
 
 The fastest way to try syncpack is via [npx](HREF_NPX).
 
-Run this command from the root directory of a monorepo and it will list every dependency installed under a [`dependencies`](HREF_DEPENDENCIES) property of a package.json file in the project.
-
-Syncpack uses your package manager's workspace configuration to locate your package.json files, or you can target specific files using the [`source`](CONFIG_SOURCE) configuration or `--source` option.
-
 ```bash
 npx syncpack@alpha list --dependency-types prod
 ```
 
+Run this command from the root directory of a monorepo and it will list every dependency installed under a [`dependencies`](HREF_DEPENDENCIES) property of a package.json file in the project.
+
+Syncpack uses your package manager's workspace configuration to locate your package.json files, or you can target specific files using the [`source`](CONFIG_SOURCE) configuration or `--source` option.
+
 For any given command, browse a summary of its options with `-h`
 
 ```bash
@@ -60,24 +60,16 @@ npm exec syncpack -- list
 ## Introduction
 
 :::note
-
-For the rest of this guide I will run syncpack as if it was installed globally
-
-```
-npm install -g syncpack@alpha
-```
-
+The examples below assume syncpack is installed globally. Replace `syncpack` with `npx syncpack@alpha` if you haven't installed it or `npm exec syncpack` if you have installed it locally.
 :::
 
-We're going to run a few commands to better understand not only syncpack, but our own project as well. Monorepos can be _huge_, it's not easy to drill down and see all of the many dependencies we might be using, and harder still to know where any inconsistencies are.
-
 Let's see which dependencies we use the most.
 
 ```bash
 syncpack list --dependency-types prod --sort count
 ```
 
-Some of our dependencies might have errors next to them, if our Terminal supports it we can command + click each error to view its documentation, or each filename to open the file.
+Some of our dependencies might have [status codes](REF_STATUS_CODES) next to them, if our Terminal supports it we can command + click each error to view its documentation, or each filename to open the file.
 
 To focus only on dependencies with errors, use `lint` instead of `list`.
 
@@ -91,6 +83,10 @@ If the suggested changes look ok, we can autofix them.
 syncpack fix --dependency-types prod
 ```
 
+:::tip
+After running `fix` or `update`, run your package manager (`npm install`, `pnpm install`, etc.) to update your lockfile.
+:::
+
 Or we could choose to only autofix one of them, for this example I've chosen `react`.
 
 ```bash
@@ -133,12 +129,16 @@ And by removing the `--check` option we can write the newer versions to our file
 syncpack update --dependencies react
 ```
 
-I'm hoping by this point that you're starting to develop an intuition for how syncpack works and how its options can be combined. Take a look at the `--help` documentation of each command to see examples and what options are available.
+Each command supports `--help` for examples and available options.
 
 ```bash
 syncpack list --help
 ```
 
+## Configuration
+
+Create a `.syncpackrc` file in your repo root to customise behaviour. See [Configuration](CONFIG_SYNCPACKRC) for all options.
+
 ## Further reading
 
 1. Read the [`Peer Dependencies`](GUIDE_PEER_DEPENDENCIES) guide if your projects uses them, it will be important to understand them from a version consistency point of view.