diff --git a/.github/workflows/package-alpine-linux.yml b/.github/workflows/package-alpine-linux.yml
index b01de6307a..e0728e278a 100644
--- a/.github/workflows/package-alpine-linux.yml
+++ b/.github/workflows/package-alpine-linux.yml
@@ -64,6 +64,7 @@ jobs:
         vec: [
           { friendlyName: "Alpine-3.20-x64", config: "Release", arch: "x64", tls: "openssl3", image: "mcr.microsoft.com/dotnet/runtime:9.0-alpine3.20-amd64", dotnetVersion: "9.0" },
           { friendlyName: "Alpine-3.20-ARM64", config: "Release", arch: "arm64", tls: "openssl3", image: "mcr.microsoft.com/dotnet/runtime:9.0-alpine3.20-arm64v8", dotnetVersion: "9.0" },
+          # .NET is not working properly for ARM32 Alpine with QEMU, so keep it disabled for now.
           # { friendlyName: "Alpine-3.20-ARM32", config: "Release", arch: "arm", tls: "openssl3", image: "mcr.microsoft.com/dotnet/runtime:9.0-alpine3.20-arm32v7", dotnetVersion: "9.0" },
         ]
     runs-on: ubuntu-latest
diff --git a/docs/PackagingAlpine.md b/docs/PackagingAlpine.md
deleted file mode 100644
index 5f2459e30e..0000000000
--- a/docs/PackagingAlpine.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# Packaging MsQuic for Alpine
-
-1. Create release and create tag with exact version number (e.g. v2.5.0).
-2. Run `generate-alpine-packaging-file.ps1` script to create `APKBUILD` file for the release. (This script can run on any Linux distro.)
-3. If you don't have account for [AlpineLinux GitLab](https://gitlab.alpinelinux.org). Create an account and [configure your SSH](https://docs.gitlab.com/ee/user/ssh.html).
-4. If you didn't fork `aports` repository yet, Fork `https://gitlab.alpinelinux.org/alpine/aports`.
-5. Clone `https://gitlab.alpinelinux.org/<your_username>/aports` repository.
-6. Navigate to `aports/testing/libmsquic` folder.
-7. Replace the `APKBUILD` file with newly created `APKBUILD` file.
-8. Create a commit using `testing/libmsquic: upgrade to <version_number>` (version_number e.g. 2.5.0 or 2.4.4).
-9. Create a merge request using `testing/libmsquic: upgrade to <version_number>` (version_number e.g. 2.5.0 or 2.4.4).
-10. Owners of the `aports` repository will respond to the PR or merge it in couple of days/hours.
-
-For future reference: [Official documentation](https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package)
diff --git a/docs/Release.md b/docs/Release.md
index a438df4d1b..fc7e14534a 100644
--- a/docs/Release.md
+++ b/docs/Release.md
@@ -106,6 +106,21 @@ Sometimes the pipeline fails due to PMC infra issues (e.g. the PMC HTTP endpoint
 
 When testing the pipeline, please make sure to comment out the PMC cli commands in [upload-linux-packages.sh](https://github.com/microsoft/msquic/blob/main/scripts/upload-linux-packages.sh) to avoid accidentally publishing packages into prod.
 
+## Publishing MsQuic for Alpine
+
+1. Create release and create tag with exact version number (e.g. v2.5.0).
+2. Run `generate-alpine-packaging-file.ps1` script to create `APKBUILD` file for the release. (This script can run on any Linux distro.)
+3. If you don't have account for [AlpineLinux GitLab](https://gitlab.alpinelinux.org). Create an account and [configure your SSH](https://docs.gitlab.com/ee/user/ssh.html).
+4. If you didn't fork `aports` repository yet, Fork `https://gitlab.alpinelinux.org/alpine/aports`.
+5. Clone `https://gitlab.alpinelinux.org/<your_username>/aports` repository.
+6. Navigate to `aports/testing/libmsquic` folder.
+7. Replace the `APKBUILD` file with newly created `APKBUILD` file.
+8. Create a commit using `testing/libmsquic: upgrade to <version_number>` (version_number e.g. 2.5.0 or 2.4.4).
+9. Create a merge request using `testing/libmsquic: upgrade to <version_number>` (version_number e.g. 2.5.0 or 2.4.4).
+10. Owners of the `aports` repository will respond to the PR or merge it in couple of days/hours.
+
+For future reference: [Official documentation](https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package)
+
 ## Synchronizing with Windows
 
 1. Once the release branch is created, set the pipeline [here](https://mscodehub.visualstudio.com/msquic/_build?definitionId=1868) to ingest the release branch into Windows, and run it.