diff --git a/.github/workflows/azure-prod-build-deploy.yml b/.github/workflows/azure-prod-build-deploy.yml
index 06da6426068b..06ac18399adf 100644
--- a/.github/workflows/azure-prod-build-deploy.yml
+++ b/.github/workflows/azure-prod-build-deploy.yml
@@ -61,12 +61,11 @@ jobs:
 
       # Create a temporary token for the Azure Container Registry
       # and set it as a GitHub Actions environment variable
-      # Then clean up by deleting the temp token.
       # Created token are viewable in the ACR resource UI
       # under Repository permissions > Tokens
       - name: 'Create Azure Container Registry Token'
         env:
-          PROD_REGISTRY_SERVER: ${{ secrets.PROD_REGISTRY_SERVER }}
+          CONTAINER_REGISTRY_SERVER: ${{ secrets.PROD_REGISTRY_SERVER }}
         run: npm run create-acr-token
 
       - name: 'Docker login'
diff --git a/.github/workflows/validate-github-github-docs-urls.yml b/.github/workflows/validate-github-github-docs-urls.yml
index e93d9f803660..c1df3d211661 100644
--- a/.github/workflows/validate-github-github-docs-urls.yml
+++ b/.github/workflows/validate-github-github-docs-urls.yml
@@ -8,15 +8,16 @@ on:
   workflow_dispatch:
   schedule:
     - cron: '20 16 * * 1' # Run every Monday at 16:20 UTC / 8:20 PST
-  pull_request:
-    paths:
-      - 'content/**'
-      # In case a relevant dependency changes
-      - 'package*.json'
-      # The scripts
-      - 'src/links/scripts/validate-github-github-docs-urls/**'
-      # The workflow
-      - .github/workflows/validate-github-github-docs-urls.yml
+  # See https://gh.io/AAsyyao before uncommenting:
+  # pull_request:
+  #   paths:
+  #     - 'content/**'
+  #     # In case a relevant dependency changes
+  #     - 'package*.json'
+  #     # The scripts
+  #     - 'src/links/scripts/validate-github-github-docs-urls/**'
+  #     # The workflow
+  #     - .github/workflows/validate-github-github-docs-urls.yml
 
 permissions:
   contents: read
diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md
index fe8e90b0735c..54cbe2387e4d 100644
--- a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md
+++ b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -2,7 +2,7 @@
 title: Managing access to self-hosted runners using groups
 shortTitle: Manage access with runner groups
 intro: You can use policies to limit access to self-hosted runners that have been added to an organization{% ifversion ghec or ghes %} or enterprise{% endif %}.
-permissions: 'Enterprise accounts, organizations owned by enterprise accounts, and organizations using {% data variables.product.prodname_team %} can create and manage additional runner groups.<br><br>{% ifversion custom-org-roles %}Users with the "Manage organization runners and runner groups" permission can manage runner groups at the organization level.{% endif %}'
+permissions: 'Enterprise accounts, organizations owned by enterprise accounts, and organizations using {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_user %} plans can create and manage additional runner groups using self-hosted runners.<br><br>{% ifversion custom-org-roles %}Users with the "Manage organization runners and runner groups" permission can manage runner groups at the organization level.{% endif %}'
 redirect_from:
   - /actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners
   - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners
diff --git a/data/reusables/actions/azure-vnet-supported-regions.md b/data/reusables/actions/azure-vnet-supported-regions.md
index 021a96bf7742..ceb813d45fc1 100644
--- a/data/reusables/actions/azure-vnet-supported-regions.md
+++ b/data/reusables/actions/azure-vnet-supported-regions.md
@@ -17,6 +17,7 @@ The {% data variables.product.prodname_actions %} service supports a subset of a
 <li><code>SwitzerlandNorth</code></li>
 <li><code>UkSouth</code></li>
 <li><code>SoutheastAsia</code></li>
+<li><code>KoreaCentral</code></li>
 </ul>
 
 Azure private networking supports GPU runners in the following regions.
diff --git a/src/audit-logs/lib/config.json b/src/audit-logs/lib/config.json
index 6d77e73b4193..53f5a7a61024 100644
--- a/src/audit-logs/lib/config.json
+++ b/src/audit-logs/lib/config.json
@@ -3,5 +3,5 @@
     "apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.",
     "apiRequestEvent": "This event is only available via audit log streaming."
   },
-  "sha": "cdccf7613c6f26c2c5542d8481cf8dacb617a94b"
+  "sha": "d5e464291d8f2559b1c5b7398c16d43c61f79548"
 }
\ No newline at end of file
diff --git a/src/workflows/acr-create-token.ts b/src/workflows/acr-create-token.ts
index ba18ebac7fdc..4a17817ca211 100755
--- a/src/workflows/acr-create-token.ts
+++ b/src/workflows/acr-create-token.ts
@@ -9,7 +9,7 @@ type IsoDateString = string
 dotenv.config()
 
 const acrTokenName = process.env.ACR_TOKEN_NAME
-const acrProdRegistryServer = process.env.PROD_REGISTRY_SERVER
+const acrServer = process.env.CONTAINER_REGISTRY_SERVER
 const repo = process.env.GITHUB_REPOSITORY
 
 function main() {
@@ -23,7 +23,7 @@ function main() {
   try {
     const cmd = `az acr token create \
       --name ${acrTokenName} \
-      --registry ${acrProdRegistryServer} \
+      --registry ${acrServer} \
       --repository ${repo} \
       content/write \
       content/read \