Merge pull request #3173 from madeline-underwood/mob

Mobile metadescriptions + enhancements using copilot file

Author: pareenaverma

content/learning-paths/mobile-graphics-and-gaming/afrc/_index.md

@@ -3,6 +3,8 @@ title: Learn about Arm Fixed Rate Compression (AFRC)
 
 minutes_to_complete: 25
 
+description: Learn how to enable and verify Arm Fixed Rate Compression in Vulkan applications on Android devices to reduce memory footprint and bandwidth.
+
 who_is_this_for: Software developers of Android applications and mobile games who are interested in learning how to enable Arm Fixed Rate Compression (AFRC) to improve performance.
 
 learning_objectives:

content/learning-paths/mobile-graphics-and-gaming/afrc/p1-intro.md

@@ -20,15 +20,15 @@ For example, the Sponza scene shown below, on a Google Pixel 8 shows the differe
  
 | Memory footprint (lower is better) | Memory bandwidth (lower is better) |
 | ----------- | ----------- |
-| ![Footprint](images/sponza_footprint.png) | ![Bandwidth](images/sponza_bandwidth.png) |
+| ![Bar chart comparing memory footprint of uncompressed images versus AFBC and AFRC compression on Google Pixel 8, showing AFRC achieves the lowest memory footprint at approximately 48 MB compared to uncompressed at 144 MB#center](images/sponza_footprint.png "Memory footprint comparison") | ![Bar chart comparing memory bandwidth of uncompressed images versus AFBC and AFRC compression on Google Pixel 8, showing AFRC achieves the lowest bandwidth at approximately 1200 MB per second#center](images/sponza_bandwidth.png "Memory bandwidth comparison") |
 
 Fixed-rate compression is lossy but, despite this, AFRC achieves high quality results even with the highest compression ratios, preserving detail in edges and high-frequency areas.
-So much so that, to the naked eye, the compressed and uncompressed images look the same side-by-side, so that it may be called 'visually lossless':
+So much so that, to the naked eye, the compressed and uncompressed images look the same side-by-side, so that it can be called 'visually lossless':
 
  
 | Uncompressed | AFRC 2BPC (bits per component) |
 | ----------- | ----------- |
-| ![Uncompressed](images/sponza_default.webp) | ![AFRC 2BPC](images/sponza_afrc.webp) |
+| ![Reference image of the Sponza scene rendered without compression, showing detailed textures and architectural elements#center](images/sponza_default.webp "Uncompressed Sponza scene") | ![Sponza scene rendered with AFRC at 2 bits per component compression, visually identical to the uncompressed version demonstrating visually lossless quality#center](images/sponza_afrc.webp "Sponza scene with AFRC 2BPC compression") |
 
 More information can be found in [this blog on Arm® Immortalis™](https://developer.arm.com/community/arm-community-blogs/b/mobile-graphics-and-gaming-blog/posts/arm-immortalis-g715-developer-overview) and in [this Vulkan sample](https://github.com/KhronosGroup/Vulkan-Samples/blob/main/samples/performance/image_compression_control/README.adoc).
 

content/learning-paths/mobile-graphics-and-gaming/afrc/p2-setup.md

@@ -8,13 +8,13 @@ layout: learningpathall
 
 ## How to run the code examples
 
-This Learning Path assumes you are already familiar with the Vulkan API and have an application that uses it to create and render images on Android. If that is the case, you may skip this step.
+This Learning Path assumes you're already familiar with the Vulkan API and have an application that uses it to create and render images on Android. If that's the case, you can skip this step.
 
-Otherwise, you may use a test application like those provided by the [Khronos Vulkan Samples repository](https://github.com/KhronosGroup/Vulkan-Samples).
+Otherwise, you can use a test application like those provided by the [Khronos Vulkan Samples repository](https://github.com/KhronosGroup/Vulkan-Samples).
 
 {{% notice Note %}}
-You do not need to create a new Vulkan Sample to complete this Learning Path but you can familiarize yourself with the code examples and save them as a reference.
-The Vulkan Sample provided in the previous step allows you to experiment with AFRC without any coding required.
+You don't need to create a new Vulkan Sample to complete this Learning Path but you can familiarize yourself with the code examples and save them as a reference.
+The Vulkan Sample provided in further reading allows you to experiment with AFRC without any coding required.
 {{% /notice %}}
 
 ### Build Khronos' Vulkan Samples
@@ -27,16 +27,16 @@ cd vulkan-samples
 python ./scripts/generate.py android
 ```
 
-And follow the build instructions to run the example applications on an Android device.
+Follow the build instructions to run the example applications on an Android device.
 
 {{% notice  %}}
 You can use [Android Studio](https://github.com/KhronosGroup/Vulkan-Samples/blob/main/docs/build.adoc#build-with-android-studio) to build and run the samples (the build instructions explain how to do this).
 {{% /notice %}}
 
 ### Create a test sample
 
-If you are coding an example, rather than following along with the existing [Image Compression Control](https://github.com/KhronosGroup/Vulkan-Samples/blob/main/samples/performance/image_compression_control/README.adoc) sample, we need to first create a test sample.
-We can use the default [API sample template](https://github.com/KhronosGroup/Vulkan-Samples/blob/main/scripts/README.adoc#generate-api-sample) to write and run the code snippets presented in this Learning Path.
+If you're coding an example, rather than following along with the existing [Image Compression Control](https://github.com/KhronosGroup/Vulkan-Samples/blob/main/samples/performance/image_compression_control/README.adoc) sample, you'll need to first create a test sample.
+You can use the default [API sample template](https://github.com/KhronosGroup/Vulkan-Samples/blob/main/scripts/README.adoc#generate-api-sample) to write and run the code snippets presented in this Learning Path.
 
 To create a new sample:
 

content/learning-paths/mobile-graphics-and-gaming/afrc/p3-enable-extensions.md

@@ -8,13 +8,13 @@ layout: learningpathall
 
 ## Vulkan Extensions
 
-The Vulkan extension [VK_EXT_image_compression_control](https://docs.vulkan.org/spec/latest/appendices/extensions.html#VK_EXT_image_compression_control) may be used to verify if default compression (such as AFBC) was applied, and to request fixed-rate compression.
+The Vulkan extension [VK_EXT_image_compression_control](https://docs.vulkan.org/spec/latest/appendices/extensions.html#VK_EXT_image_compression_control) can be used to verify if default compression (such as AFBC) was applied, and to request fixed-rate compression.
 
 Swapchain images are a special case, and additionally require the [VK_EXT_image_compression_control_swapchain](https://docs.vulkan.org/spec/latest/appendices/extensions.html#VK_EXT_image_compression_control_swapchain) extension.
 
 ### Enable VK_EXT_image_compression_control
 
-In your application, you may use [vkEnumerateDeviceExtensionProperties](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/vkEnumerateDeviceExtensionProperties.html) to check if the device supports the extension, and, if so, include it in [VkDeviceCreateInfo](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkDeviceCreateInfo.html)'s `ppEnabledExtensionNames` before calling [vkCreateDevice](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/vkCreateDevice.html).
+In your application, you can use [vkEnumerateDeviceExtensionProperties](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/vkEnumerateDeviceExtensionProperties.html) to check if the device supports the extension, and, if so, include it in [VkDeviceCreateInfo](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkDeviceCreateInfo.html)'s `ppEnabledExtensionNames` before calling [vkCreateDevice](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/vkCreateDevice.html).
 In the Vulkan Samples framework, this can be handled in the sample's constructor with this helper function:
 
 ```C
@@ -24,7 +24,7 @@ afrc::afrc()
 }
 ```
 
-If a device supports the extension, it does not mean that it also supports fixed-rate compression of images.
-The extension may still be used to verify if the images use default (lossless) compression.
+If a device supports the extension, it doesn't mean that it also supports fixed-rate compression of images.
+The extension can still be used to verify if the images use default (lossless) compression.
 
 Before compressing a `VkImage`, you need to use the extension to query if any given image, with its particular format and usage properties, supports fixed-rate compression, as shown in the next step.

content/learning-paths/mobile-graphics-and-gaming/afrc/p5-request-afrc.md

@@ -19,7 +19,7 @@ image_create_info.pNext = &compression_control;
 
 Note that these are the same `VkImageCompressionControlEXT` and `VkImageCreateInfo` structures used in the previous step.
 
-The image may then be created:
+You can then create the image:
 
 ```C
 VkImage image_handle;
@@ -28,9 +28,9 @@ vkCreateImage(get_device().get_handle(), &image_create_info, nullptr, &image_han
 ```
 
 This requests default fixed-rate compression (which depends on the device).
-On Arm GPUs, it is the highest supported bitrate that is the highest possible quality.
+On Arm GPUs, it's the highest supported bitrate that is the highest possible quality.
 
-To request a specific bitrate (after confirming that it is supported, as shown in the previous step), you may instead use `VK_IMAGE_COMPRESSION_FIXED_RATE_EXPLICIT_EXT` like this:
+To request a specific bitrate (after confirming that it's supported, as shown in the previous step), you can instead use `VK_IMAGE_COMPRESSION_FIXED_RATE_EXPLICIT_EXT` like this:
 
 ```C
 VkImageCompressionFixedRateFlagsEXT fixed_rate_flags_array[1] = {VK_IMAGE_COMPRESSION_FIXED_RATE_2BPC_BIT_EXT};

content/learning-paths/mobile-graphics-and-gaming/afrc/p6-verify-afrc.md

@@ -32,7 +32,7 @@ LOGI("Created image reports {}", compression_to_string(applied_compression_prope
 LOGI("Created image reports {}", fixed_rate_flags_to_string(applied_compression_properties.imageCompressionFixedRateFlags));
 ```
 
-The output may then look like this:
+The output might then look like this:
 
 ```output
 I/VulkanSamples: [info] Created image reports VK_IMAGE_COMPRESSION_FIXED_RATE_EXPLICIT_EXT

content/learning-paths/mobile-graphics-and-gaming/ai-camera-pipelines/_index.md

@@ -1,6 +1,8 @@
 ---
 title: Accelerate Denoising, Background Blur and Low-Light Camera Effects with SME2
 
+description: Learn how to build and optimize AI-powered camera pipeline applications on Arm Linux using KleidiAI, KleidiCV, and SME2 to accelerate denoising, background blur, and low-light effects.
+
 minutes_to_complete: 30
 
 who_is_this_for: This introductory topic is for mobile and computer-vision developers, camera pipeline engineers, and performance-minded practitioners who want to optimize real-time camera effects on Arm using KleidiAI and KleidiCV.

content/learning-paths/mobile-graphics-and-gaming/analyze_a_frame_with_frame_advisor/_index.md

@@ -1,5 +1,7 @@
 ---
 title: Analyze a frame with Frame Advisor
+description: Learn how to capture frame data from Android applications and analyze performance inefficiencies using Frame Advisor in Arm Performance Studio.
+
 
 minutes_to_complete: 10
 

content/learning-paths/mobile-graphics-and-gaming/android_halide/_index.md

@@ -1,5 +1,6 @@
 ---
-title: Build high-performance image processing with Halide on Android
+title: Optimize image processing on Android using Halide
+description: Learn how to build real-time image processing pipelines using Halide on Android, combining operations for improved performance in Kotlin applications.
 
 minutes_to_complete: 180
 

content/learning-paths/mobile-graphics-and-gaming/android_neon/_index.md

@@ -1,5 +1,7 @@
 ---
-title: Get started with Neon Intrinsics on Android
+title: Accelerate Android applications with Neon intrinsics
+
+description: Learn how to enable and implement Neon intrinsics in Android NDK applications to calculate vector operations and measure performance improvements.
 
 draft: true
 cascade: