@@ -177,7 +177,7 @@ This command doesn't change the global version used when running the package |
177 | 177 | manager from outside the project (use the \`-g,--global\` flag if you wish |
178 | 178 | to do this). |
179 | 179 |
|
180 | | -### `corepack install <-g,--global> [--all] [... name@version]` |
| 180 | +### `corepack install <-g,--global> [--all] [... name[@<version>]]` |
181 | 181 |
|
182 | 182 | | Option | Description | |
183 | 183 | | --------------------- | ------------------------------------------ | |
@@ -189,7 +189,7 @@ Package managers thus installed will be configured as the new default when |
189 | 189 | calling their respective binaries outside of projects defining the |
190 | 190 | `packageManager` field. |
191 | 191 |
|
192 | | -### `corepack pack [--all] [... name@version]` |
| 192 | +### `corepack pack [--all] [... name[@<version>]]` |
193 | 193 |
|
194 | 194 | | Option | Description | |
195 | 195 | | --------------------- | ------------------------------------------ | |
@@ -200,7 +200,7 @@ calling their respective binaries outside of projects defining the |
200 | 200 | Download the selected package managers and store them inside a tarball |
201 | 201 | suitable for use with `corepack install -g`. |
202 | 202 |
|
203 | | -### `corepack use <name@version>` |
| 203 | +### `corepack use <name[@<version>]>` |
204 | 204 |
|
205 | 205 | When run, this command will retrieve the latest release matching the provided |
206 | 206 | descriptor, assign it to the project's package.json file, and automatically |
|
215 | 215 | Unlike `corepack use` this command doesn't take a package manager name nor a |
216 | 216 | version range, as it will always select the latest available version from the |
217 | 217 | same major line. Should you need to upgrade to a new major, use an explicit |
218 | | -`corepack use {name}@latest` call. |
| 218 | +`corepack use {name}@latest` call (or simply `corepack use {name}`). |
219 | 219 |
|
220 | 220 | ## Environment Variables |
221 | 221 |
|
|