ArmDeveloperEcosystem · pareenaverma · Nov 10, 2025 · Nov 6, 2025 · Nov 6, 2025 · Nov 10, 2025
diff --git a/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure1.png b/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure1.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure2.png b/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure2.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure3.png b/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure3.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure4.png b/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure4.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure5.png b/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure5.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure6.png b/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure6.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure7.png b/content/learning-paths/embedded-and-microcontrollers/avh_ppocr/figure7.png
diff --git a/...g-paths/embedded-and-microcontrollers/introduction-to-tinyml-on-arm/connect.png b/...g-paths/embedded-and-microcontrollers/introduction-to-tinyml-on-arm/connect.png
diff --git a/...-paths/embedded-and-microcontrollers/introduction-to-tinyml-on-arm/overview.png b/...-paths/embedded-and-microcontrollers/introduction-to-tinyml-on-arm/overview.png
diff --git a/...g-paths/embedded-and-microcontrollers/jetson_object_detection/balenaetcher1.png b/...g-paths/embedded-and-microcontrollers/jetson_object_detection/balenaetcher1.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/linux-on-fvp/FVP running.png b/content/learning-paths/embedded-and-microcontrollers/linux-on-fvp/FVP running.png
diff --git a/...rning-paths/embedded-and-microcontrollers/linux-on-fvp/cortex-a53_mpidr_el1.png b/...rning-paths/embedded-and-microcontrollers/linux-on-fvp/cortex-a53_mpidr_el1.png
diff --git a/...rning-paths/embedded-and-microcontrollers/linux-on-fvp/cortex-a55_mpidr_el1.png b/...rning-paths/embedded-and-microcontrollers/linux-on-fvp/cortex-a55_mpidr_el1.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/linux-on-fvp/fvp.png b/content/learning-paths/embedded-and-microcontrollers/linux-on-fvp/fvp.png
diff --git a/...ent/learning-paths/embedded-and-microcontrollers/linux-on-fvp/select_target.png b/...ent/learning-paths/embedded-and-microcontrollers/linux-on-fvp/select_target.png
diff --git a/.../embedded-and-microcontrollers/project-migration-cmsis-v6/cmsis-rtx_missing.png b/.../embedded-and-microcontrollers/project-migration-cmsis-v6/cmsis-rtx_missing.png
diff --git a/.../embedded-and-microcontrollers/project-migration-cmsis-v6/coredebug_uvision.png b/.../embedded-and-microcontrollers/project-migration-cmsis-v6/coredebug_uvision.png
diff --git a/...ths/embedded-and-microcontrollers/project-migration-cmsis-v6/device_missing.png b/...ths/embedded-and-microcontrollers/project-migration-cmsis-v6/device_missing.png
diff --git a/...ded-and-microcontrollers/project-migration-cmsis-v6/eventrecorder_migration.png b/...ded-and-microcontrollers/project-migration-cmsis-v6/eventrecorder_migration.png
diff --git a/...paths/embedded-and-microcontrollers/project-migration-cmsis-v6/io_migration.png b/...paths/embedded-and-microcontrollers/project-migration-cmsis-v6/io_migration.png
diff --git a/...hs/embedded-and-microcontrollers/project-migration-cmsis-v6/os_tick_missing.png b/...hs/embedded-and-microcontrollers/project-migration-cmsis-v6/os_tick_missing.png
diff --git a/...nt/learning-paths/embedded-and-microcontrollers/raspberry-pi-smart-home/ui3.png b/...nt/learning-paths/embedded-and-microcontrollers/raspberry-pi-smart-home/ui3.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/uv_debug/callstacklocals.png b/content/learning-paths/embedded-and-microcontrollers/uv_debug/callstacklocals.png
diff --git a/...-paths/embedded-and-microcontrollers/uv_debug/callstacklocals_caller_callee.png b/...-paths/embedded-and-microcontrollers/uv_debug/callstacklocals_caller_callee.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/uv_debug/gmsticksmemory.png b/content/learning-paths/embedded-and-microcontrollers/uv_debug/gmsticksmemory.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/uv_debug/gmstickswatch.png b/content/learning-paths/embedded-and-microcontrollers/uv_debug/gmstickswatch.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/uv_debug/mainwhileloop.png b/content/learning-paths/embedded-and-microcontrollers/uv_debug/mainwhileloop.png
diff --git a/...rning-paths/embedded-and-microcontrollers/uv_debug/mainwhileloopdisassembly.png b/...rning-paths/embedded-and-microcontrollers/uv_debug/mainwhileloopdisassembly.png
diff --git a/.../learning-paths/embedded-and-microcontrollers/uv_debug/mainwhileloopstopped.png b/.../learning-paths/embedded-and-microcontrollers/uv_debug/mainwhileloopstopped.png
diff --git a/content/learning-paths/embedded-and-microcontrollers/uv_debug/managebkpt.png b/content/learning-paths/embedded-and-microcontrollers/uv_debug/managebkpt.png
diff --git a/.../learning-paths/embedded-and-microcontrollers/uv_debug/periodicwindowupdate.png b/.../learning-paths/embedded-and-microcontrollers/uv_debug/periodicwindowupdate.png
diff --git a/.../learning-paths/embedded-and-microcontrollers/uv_debug/systemcoreclockwatch.png b/.../learning-paths/embedded-and-microcontrollers/uv_debug/systemcoreclockwatch.png
diff --git a/...nt/learning-paths/embedded-and-microcontrollers/uv_debug/systicktimerwindow.png b/...nt/learning-paths/embedded-and-microcontrollers/uv_debug/systicktimerwindow.png
diff --git a/...ded-and-microcontrollers/visualizing-ethos-u-performance/7-configure-fvp-gui.md b/...ded-and-microcontrollers/visualizing-ethos-u-performance/7-configure-fvp-gui.md
@@ -70,7 +70,7 @@ Now run the Mobilenet V2 computer vision model, using [executorch/examples/arm/r
 
 Observe that the FVP loads the model file, compiles the PyTorch model to ExecuTorch `.pte` format and then shows an instruction count in the top right of the GUI:
 
-![Terminal and FVP output#center](./Terminal%20and%20FVP%20Output.jpg "Terminal and FVP output")
+![Terminal and FVP output#center](./terminal_and_fvp_output.jpg "Terminal and FVP output")
 
 {{% notice Note %}}
 

diff --git a/...u-performance/Terminal and FVP Output.jpg → ...u-performance/terminal_and_fvp_output.jpg b/...u-performance/Terminal and FVP Output.jpg → ...u-performance/terminal_and_fvp_output.jpg
diff --git a/...t/learning-paths/laptops-and-desktops/windowsperf-vs-extension/spe-settings.png b/...t/learning-paths/laptops-and-desktops/windowsperf-vs-extension/spe-settings.png
diff --git a/...nt/learning-paths/mobile-graphics-and-gaming/ams/images/fa_render_graph_1.1.gif b/...nt/learning-paths/mobile-graphics-and-gaming/ams/images/fa_render_graph_1.1.gif
diff --git a/...-graphics-and-gaming/analyze_a_frame_with_frame_advisor/fa_render_graph_1.1.gif b/...-graphics-and-gaming/analyze_a_frame_with_frame_advisor/fa_render_graph_1.1.gif
diff --git a/...ths/mobile-graphics-and-gaming/analyze_a_frame_with_frame_advisor/fa_sphinx.png b/...ths/mobile-graphics-and-gaming/analyze_a_frame_with_frame_advisor/fa_sphinx.png
diff --git a/...le-graphics-and-gaming/analyze_a_frame_with_frame_advisor/fa_step_drawcalls.gif b/...le-graphics-and-gaming/analyze_a_frame_with_frame_advisor/fa_step_drawcalls.gif
diff --git a/...paths/mobile-graphics-and-gaming/analyze_a_frame_with_frame_advisor/pillars.gif b/...paths/mobile-graphics-and-gaming/analyze_a_frame_with_frame_advisor/pillars.gif
diff --git a/...e-graphics-and-gaming/analyze_a_frame_with_frame_advisor/render_graph_egypt.png b/...e-graphics-and-gaming/analyze_a_frame_with_frame_advisor/render_graph_egypt.png
diff --git a/...analyze_a_frame_with_frame_advisor/render_graph_egypt_redundant_attachments.png b/...analyze_a_frame_with_frame_advisor/render_graph_egypt_redundant_attachments.png
diff --git a/...-gaming/analyze_a_frame_with_frame_advisor/render_graph_egypt_redundant_rps.png b/...-gaming/analyze_a_frame_with_frame_advisor/render_graph_egypt_redundant_rps.png
diff --git a/...ile-graphics-and-gaming/android_webgpu_dawn/images/gameactivityarchitecture.png b/...ile-graphics-and-gaming/android_webgpu_dawn/images/gameactivityarchitecture.png
diff --git a/...ile-graphics-and-gaming/android_webgpu_dawn/images/streamline-mali-analysis.png b/...ile-graphics-and-gaming/android_webgpu_dawn/images/streamline-mali-analysis.png
diff --git a/...ile-graphics-and-gaming/android_webgpu_dawn/images/streamline-mali-timeline.png b/...ile-graphics-and-gaming/android_webgpu_dawn/images/streamline-mali-timeline.png
diff --git a/...graphics-and-gaming/best-practices-for-hwrt-lumen-performance/images/garage.png b/...graphics-and-gaming/best-practices-for-hwrt-lumen-performance/images/garage.png
diff --git a/...raphics-and-gaming/best-practices-for-hwrt-lumen-performance/images/garage2.png b/...raphics-and-gaming/best-practices-for-hwrt-lumen-performance/images/garage2.png
diff --git a/...ing/build-android-selfie-app-using-mediapipe-multimodality/2-app-scaffolding.md b/...ing/build-android-selfie-app-using-mediapipe-multimodality/2-app-scaffolding.md
@@ -30,12 +30,12 @@ Before you start coding, here are some useful tips:
 1. Navigate to **File** > **New** > **New Project**.
 
 2. Select **Empty Views Activity** in the **Phone and Tablet** gallery as Figure 1 shows, then select **Next**.
-![Empty Views Activity.png alt-text#center](images/2/empty%20project.png "Figure 1: Select Empty Views Activity.")
+![Empty Views Activity.png alt-text#center](images/2/empty_project.png "Figure 1: Select Empty Views Activity.")
 
 3. Choose a project name, and select the default configurations as Figure 2 shows. 
 
     Make sure that the **Language** field is set to **Kotlin**, and the **Build configuration language** field is set to **Kotlin DSL**.
-![Project configuration.png alt-text#center](images/2/project%20config.png "Figure 2: Project Configuration.")
+![Project configuration.png alt-text#center](images/2/project_config.png "Figure 2: Project Configuration.")
 
 ## Add CameraX dependencies
 
@@ -45,7 +45,7 @@ Before you start coding, here are some useful tips:
 
 2. Once the project is synced, navigate to `libs.versions.toml` in your project's root directory. See Figure 3. This file serves as the version catalog for all dependencies that the project uses.
 
-![Version Catalog.png alt-text#center](images/2/dependency%20version%20catalog.png "Figure 3: Version Catalog.")
+![Version Catalog.png alt-text#center](./images/2/dependency_version_catalog.png "Figure 3: Version Catalog.")
 
 {{% notice Info %}}
 
@@ -88,20 +88,20 @@ camera-view = { group = "androidx.camera", name = "camera-view", version.ref = "
 
 2. You should see that a notification appears. See Figure 4. Click **Sync Now** to sync your project.
 
-![Gradle sync.png alt-text#center](images/2/gradle%20sync.png "Figure 4: Gradle Sync.")
+![Gradle sync.png alt-text#center](images/2/gradle_sync.png "Figure 4: Gradle Sync.")
 
 {{% notice Tip %}}
 
 You can also click the **Sync Project with Gradle Files** button in the toolbar, or enter the corresponding shortcut to start a sync.
 
-![Sync Project with Gradle Files](images/2/sync%20project%20with%20gradle%20files.png)
+![Sync Project with Gradle Files](images/2/sync_project_with_gradle_files.png)
 {{% /notice %}}
 
 3. Navigate to the `MainActivity.kt` source file and make the changes that Figure 5 shows in the View Binding screenshot. 
 
     This inflates the layout file into a view binding object, and stores it in a member variable within the view controller for easier access later.
 
-![view binding alt-text#center](images/2/view%20binding.png "Figure 5: View Binding.")
+![view binding alt-text#center](images/2/view_binding.png "Figure 5: View Binding.")
 
 ## Configure CameraX preview
 

diff --git a/...build-android-selfie-app-using-mediapipe-multimodality/4-introduce-mediapipe.md b/...build-android-selfie-app-using-mediapipe-multimodality/4-introduce-mediapipe.md
@@ -106,7 +106,7 @@ See the previous section [Set up the Development Environment](../2-app-scaffoldi
 
 2. Now you should see both model asset bundles in your `assets` directory, as shown below:
 
-![model asset bundles](images/4/model%20asset%20bundles.png)
+![model asset bundles](images/4/model_asset_bundles.png)
 
 3. You are ready to import MediaPipe's Face Landmark Detection and Gesture Recognizer into the project. 
 

diff --git a/...build-android-selfie-app-using-mediapipe-multimodality/6-flow-data-to-view-1.md b/...build-android-selfie-app-using-mediapipe-multimodality/6-flow-data-to-view-1.md
@@ -366,5 +366,5 @@ class GestureOverlayView(context: Context?, attrs: AttributeSet?) :
 
 4. Build and run the app again. Now you should see face and gesture overlays on top of the camera preview as shown below. Good job!
 
-![overlay views alt-text#center](images/6/overlay%20views.png "Figure 7: Face and Gesture Overlays.")
+![overlay views alt-text#center](images/6/overlay_views.png "Figure 7: Face and Gesture Overlays.")
 
diff --git a/...build-android-selfie-app-using-mediapipe-multimodality/7-flow-data-to-view-2.md b/...build-android-selfie-app-using-mediapipe-multimodality/7-flow-data-to-view-2.md
@@ -132,7 +132,7 @@ This makes sure each of the three parallel `launch` code sections run in its own
 5. Build and run the app again.
 Now you should see two switches on the bottom of the screen as shown below, which turn on and off while you smile and show thumb-up gestures. Good job!
 
-![indicator UI alt-text#center](images/7/indicator%20ui.png "Figure 8: Indicator UI.")
+![indicator UI alt-text#center](images/7/indicator_ui.png "Figure 8: Indicator UI.")
 
 ## Recap on SharedFlow vs StateFlow
 

diff --git a/...y/images/2/dependency version catalog.png → ...y/images/2/dependency_version_catalog.png b/...y/images/2/dependency version catalog.png → ...y/images/2/dependency_version_catalog.png
diff --git a/...-multimodality/images/2/empty project.png → ...-multimodality/images/2/empty_project.png b/...-multimodality/images/2/empty project.png → ...-multimodality/images/2/empty_project.png
diff --git a/...pe-multimodality/images/2/gradle sync.png → ...pe-multimodality/images/2/gradle_sync.png b/...pe-multimodality/images/2/gradle sync.png → ...pe-multimodality/images/2/gradle_sync.png
diff --git a/...multimodality/images/2/project config.png → ...multimodality/images/2/project_config.png b/...multimodality/images/2/project config.png → ...multimodality/images/2/project_config.png
diff --git a/...ages/2/sync project with gradle files.png → ...ages/2/sync_project_with_gradle_files.png b/...ages/2/sync project with gradle files.png → ...ages/2/sync_project_with_gradle_files.png
diff --git a/...e-multimodality/images/2/view binding.png → ...e-multimodality/images/2/view_binding.png b/...e-multimodality/images/2/view binding.png → ...e-multimodality/images/2/view_binding.png
diff --git a/...modality/images/4/model asset bundles.png → ...modality/images/4/model_asset_bundles.png b/...modality/images/4/model asset bundles.png → ...modality/images/4/model_asset_bundles.png
diff --git a/...-multimodality/images/6/overlay views.png → ...-multimodality/images/6/overlay_views.png b/...-multimodality/images/6/overlay views.png → ...-multimodality/images/6/overlay_views.png
diff --git a/...e-multimodality/images/7/indicator ui.png → ...e-multimodality/images/7/indicator_ui.png b/...e-multimodality/images/7/indicator ui.png → ...e-multimodality/images/7/indicator_ui.png
diff --git a/...nt/learning-paths/mobile-graphics-and-gaming/profiling-ml-on-arm/streamline.png b/...nt/learning-paths/mobile-graphics-and-gaming/profiling-ml-on-arm/streamline.png
diff --git a/...hics-and-gaming/profiling-unity-apps-on-android/images/import-window-step-1.PNG b/...hics-and-gaming/profiling-unity-apps-on-android/images/import-window-step-1.PNG
diff --git a/...learning-paths/mobile-graphics-and-gaming/ray_tracing/images/rquery_diagram.svg b/...learning-paths/mobile-graphics-and-gaming/ray_tracing/images/rquery_diagram.svg
diff --git a/...ning-paths/mobile-graphics-and-gaming/ray_tracing/images/rtpipeline_diagram.svg b/...ning-paths/mobile-graphics-and-gaming/ray_tracing/images/rtpipeline_diagram.svg
diff --git a/...hics-and-gaming/using_unity_machine_learning_agents/images/unityhubinstalls.png b/...hics-and-gaming/using_unity_machine_learning_agents/images/unityhubinstalls.png
diff --git a/...d-gaming/vision-llm-inference-on-android-with-kleidiai-and-mnn/loading_page.png b/...d-gaming/vision-llm-inference-on-android-with-kleidiai-and-mnn/loading_page.png
diff --git a/...arning-paths/mobile-graphics-and-gaming/vulkan-ml-sample/2-ml-ext-for-vulkan.md b/...arning-paths/mobile-graphics-and-gaming/vulkan-ml-sample/2-ml-ext-for-vulkan.md
@@ -45,7 +45,7 @@ You must use a version >= 1.4.321 for the Vulkan SDK.
 
 For this Learning Path, a pre-built of package of the emulation layers is available. Download them by clicking the link.
 
-[ML Emulation Layer for Vulkan](https://www.arm.com/-/media/Files/developer/MLEmulationLayerForVulkan)
+[ML Emulation Layer for Vulkan](https://www.arm.com/-/media/Files/developer/MLEmulationLayerForVulkan20251107)
 
 Extract the downloaded file in a location of your choice. You’re now ready to enable the emulation layers in Vulkan Configurator.
 

diff --git a/content/learning-paths/servers-and-cloud-computing/csp/images/armarch.png b/content/learning-paths/servers-and-cloud-computing/csp/images/armarch.png
diff --git a/...ent/learning-paths/servers-and-cloud-computing/csp/images/azureavailability.png b/...ent/learning-paths/servers-and-cloud-computing/csp/images/azureavailability.png
diff --git a/content/learning-paths/servers-and-cloud-computing/csp/images/azureimage.png b/content/learning-paths/servers-and-cloud-computing/csp/images/azureimage.png
diff --git a/content/learning-paths/servers-and-cloud-computing/csp/images/azurekey.png b/content/learning-paths/servers-and-cloud-computing/csp/images/azurekey.png
diff --git a/content/learning-paths/servers-and-cloud-computing/disk-io-benchmark/ebs.png b/content/learning-paths/servers-and-cloud-computing/disk-io-benchmark/ebs.png
diff --git a/content/learning-paths/servers-and-cloud-computing/disk-io-benchmark/iops.png b/content/learning-paths/servers-and-cloud-computing/disk-io-benchmark/iops.png
diff --git a/content/learning-paths/servers-and-cloud-computing/gke-multi-arch-axion/_index.md b/content/learning-paths/servers-and-cloud-computing/gke-multi-arch-axion/_index.md
@@ -1,24 +1,20 @@
 ---
-title: From x86 to Arm on GKE - Build, Deploy, and Migrate with Google Axion
-
-draft: true
-cascade:
-    draft: true
+title: Migrate x86 workloads to Arm on Google Kubernetes Engine with Axion processors 
 
 minutes_to_complete: 90
 
-who_is_this_for: This is an advanced topic for cloud, platform, and site reliability engineers operating Kubernetes on Google Cloud who need a prescriptive path to build multi-architecture images and migrate services from x86 to Arm using Google Axion processors.
+who_is_this_for: This is an advanced topic for cloud, platform, and site reliability engineers who operate Kubernetes on Google Cloud and need to build multi-architecture images and migrate services from x86 to Arm using Google Axion processors.
 
 learning_objectives:
     - Prepare Dockerfiles for multi-architecture builds by adding arm64 support
-    - Create a dual-architecture GKE standard cluster with two node pools, amd64 and arm64
-    - Build and publish multi-architecture images to Artifact Registry using Docker Buildx without using QEMU to emulate Arm instructions
-    - Deploy a Kubernetes application amd64 first, then migrate to arm64 using Kustomize overlays and progressive rollout
-    - Optionally automate builds and rollouts with Cloud Build and Skaffold
+    - Create a dual-architecture GKE standard cluster with amd64 and arm64 node pools 
+    - Build and publish multi-architecture images to Artifact Registry using Docker Buildx
+    - Deploy a Kubernetes application on amd64, then migrate to arm64 using Kustomize overlays
+    - Automate builds and rollouts with Cloud Build and Skaffold
 
 prerequisites:
     - A [Google Cloud account](https://console.cloud.google.com/) with billing enabled
-    - A local Linux or macOS computer or Cloud Shell access with Docker, Kubernetes CLI (kubectl), Google Cloud CLI (gcloud), and Git installed
+    - A local Linux or macOS computer with Docker, Kubernetes CLI (kubectl), Google Cloud CLI (gcloud), and Git installed, or access to Google Cloud Shell
     - Basic familiarity with Docker, Kubernetes, and gcloud
 
 author: 
@@ -40,11 +36,11 @@ tools_software_languages:
 
 further_reading:
     - resource:
-        title: GKE documentation
+        title: Google Kubernetes Engine documentation
         link: https://cloud.google.com/kubernetes-engine/docs
         type: documentation
     - resource:
-        title: Create Arm-based clusters and node pools 
+        title: Create standard clusters and node pools with Arm nodes 
         link: https://cloud.google.com/kubernetes-engine/docs/how-to/create-arm-clusters-nodes
         type: documentation
Original file line number	Diff line number	Diff line change
Expand Up		@@ -366,5 +366,5 @@ class GestureOverlayView(context: Context?, attrs: AttributeSet?) :

		4. Build and run the app again. Now you should see face and gesture overlays on top of the camera preview as shown below. Good job!

		![overlay views alt-text#center](images/6/overlay%20views.png "Figure 7: Face and Gesture Overlays.")
		![overlay views alt-text#center](images/6/overlay_views.png "Figure 7: Face and Gesture Overlays.")