website updates

Author: ilg-ul

website/docs/maintainer/_common/_arm-toolchain-check-upstream-release.mdx

@@ -12,15 +12,15 @@ import versionMinor from '@site/src/libs/versionMinor';
 
 The current release must be announced in
 [Arm GNU Toolchain Downloads](https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads).
-Compare the latest release with the current xPack
+Compare the latest Arm release with the current xPack
 [release](https://github.com/xpack-dev-tools/arm-none-eabi-gcc-xpack/releases).
 If necessary, update the triplet, otherwise increase the fourth & fifth numbers,
 as below.
 
 ### Update to the latest Arm release
 
 - download the new _Source code_ archive (like
-<code>arm-gnu-toolchain-src-snapshot-{versionMajor()}.{versionMinor()}.rel{customField('armSubRelease')}.tar.xz</code> from
+<code>arm-gnu-toolchain-src-snapshot-{versionMajor()}.{versionMinor()}.rel{customField('armSubRelease')}.tar.xz</code>) from
 [Arm GNU Toolchain Downloads](https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads/)
 - the GCC version is in `gcc/gcc/BASE-VER`
 - the GDB version is in `binutils-gdb--gdb/gdb/version.in`

website/docs/maintainer/_common/_arm-toolchain-update-version-specific.mdx

@@ -34,13 +34,13 @@ Similarly for GDB:
 - push the tag to origin
 - check the tag at https://github.com/xpack-dev-tools/binutils-gdb/tags/
 
-### Update local gcc fork (if the commit ID present in manifest.txt)
+### Update the local gcc fork (if the commit ID present in manifest.txt)
 
 With a Git client:
 
 - checkout the branch mentioned in the release notes
   (like <code>ARM/arm-{versionMajor()}</code>)
-- identify the commit ID (search upwards)
+- identify the commit ID (filter by branch and search downwards)
 - create a branch like <code>arm-{customField('gdbVersionMajor')}-arm-none-eabi-{versionMajor()}.{versionMinor()}.rel{customField('armSubRelease')}</code>
 
 ### Update the gdb-*-cross.git.patch in helper

website/docs/maintainer/_development-durations.mdx

@@ -3,11 +3,11 @@
 
 {/* Below 5 minutes use "Several minutes later" */}
 export const developmentDurations = {
-    "work": "about 96 minutes (1h36m), without multi-libs",
-    "darwin-x64": "About 76 minutes (1h16m) later",
-    "darwin-arm64": "About 49 minutes later",
-    "linux-x64": "About 51 minutes later",
-    "win32-x64": "About 39 minutes later",
-    "linux-arm64": "About 353 minutes (5h53m) later, or 90 minutes (1h30m) on ampere",
+    "work": "about 96 minutes (1h36m), without multi-libs, 295 minutes (4h55m) with multi-libs",
+    "darwin-x64": "About 76 minutes (1h16m) later, 240 minutes (4h00m) with multi-libs",
+    "darwin-arm64": "About 49 minutes later, 132 minutes (2h12m) with multi-libs",
+    "linux-x64": "About 51 minutes later, 142 minutes (2h22m) with multi-libs",
+    "win32-x64": "About 39 minutes later, 134 minutes (2h14m) with multi-libs",
+    "linux-arm64": "About 353 minutes (5h53m) later, or 90 minutes (1h30m) on ampere, 239 minutes (3h59m) on ampere with multi-libs",
     "linux-arm": "About 345 minutes (5h45m) later",
 }

website/docs/maintainer/_github-actions-durations.mdx

@@ -3,9 +3,9 @@
 
 The builds take almost XX hours to complete:
 
-- `darwin-x64`: 5m / 1h21m (nuc)
-- `darwin-arm64`: 4m / 45m (m1)
-- `linux-x64`: 4m / 60m (amd)
-- `win32-x64`: 5m / 53m (amd)
-- `linux-arm64`: 11m / 5h38m (rpi4)
-- `linux-arm`: 11m / 5h34m (rpi4)
+- `darwin-x64`: 4h24m / 1h21m (nuc)
+- `darwin-arm64`: 2h17m / 45m (m1)
+- `linux-x64`: 2h42m / 60m (amd)
+- `win32-x64`: 2h35m / 53m (amd)
+- `linux-arm64`: 14h15m / 5h38m (rpi4)
+- `linux-arm`: 13h44m / 5h34m (rpi4)

website/docs/maintainer/index.mdx

@@ -146,7 +146,7 @@ and will be updated when the new release is out.
 Check the latest versions at https://github.com/xpack-dev-tools/ and
 update the dependencies in `build-assets/package.json`.
 
-### Increase the version and update the version in top `package.json`
+### Increase the version and update it in the top `package.json`
 
 - determine the version (like <code>{customField('upstreamVersion')}</code>)
 - update the version in top `package.json`
@@ -156,7 +156,7 @@ like <code>{customField('upstreamVersion')}-{customField('xpackSubversion')}.{cu
 ### Update the `customFields` in `build-assets/package.json` (if necessary)
 
 If the project uses `customFields` in `build-assets/package.json`,
-update them (for example `armSubRelease` for Arm toolchains).
+update them.
 
 ### Start the local web server
 
@@ -375,7 +375,7 @@ via HomeBrew, and make a link to `/usr/local/bin`.
 
 :::
 
-### Update the list of links in package.json
+### Update the list of links in top package.json
 
 Copy/paste the full list of links displayed at the end of the build, in
 sequence, for each platform (GNU/Linux, macOS, Windows), and check the
@@ -713,7 +713,7 @@ watching this project.
   - `website/docs/install/_manual-install-quick-test.mdx`
 - commit changes
 
-### Check the list of links in package.json
+### Check the list of links in top package.json
 
 - open the `package.json` file
 - check if the links in the `bin` property cover the actual binaries
@@ -832,7 +832,7 @@ and the X/Twitter announcement
 The `website` branch may be subsequently updated, as long as the
 version in `package.json` is not changed.
 
-### Update the repo main branch
+### Update the `xpack` branch
 
 - merge `xpack-development` into `xpack`
 - push the `xpack` branch to GitHub