Merge pull request #2750 from ArmDeveloperEcosystem/resize-images

Resize images changed in the last week

Author: pareenaverma

content/learning-paths/mobile-graphics-and-gaming/profiling-unity-apps-on-android/2-preparation.md

@@ -86,7 +86,7 @@ Once the sample project has been imported, you will see some errors and warnings
 
 3. Select _Switch Platform_, as you did in the [previous Learning Path](/learning-paths/mobile-graphics-and-gaming/get-started-with-unity-on-android/3-test-on-android/)
 
-   ![Build-Profile-Menu#center](images/bp-menu.png "Figure 5. Build Profile menu.")
+   ![Build-Profile-Menu#center](images/bp-menu.webp "Figure 5. Build Profile menu.")
 
 Unity will take a moment to build the assets for the Android platform.
 
@@ -126,7 +126,7 @@ You will now deploy the sample to your Android device. Your device must already
 
 2. Tick the _Development Build_ option
 
-  ![Import sample project#center](images/bp-menu-build.png "Figure 9. Development Build.")
+  ![Import sample project#center](images/bp-menu-build.webp "Figure 9. Development Build.")
 
 3. Select _Add Open Scenes_ to add the demo scene to your _Scenes in Build_ list
 

content/learning-paths/mobile-graphics-and-gaming/profiling-unity-apps-on-android/4-profiling.md

@@ -39,7 +39,7 @@ In the sample, the performance issues will be apparent soon after launch. To pro
 
 2. Ensure _Autoconnect Profiler_ is ticked
 
-    ![Build settings to autoconnect profiler#center](images/ac.png "Figure 1. Build settings with connected Android device and Autoconnect Profiler enabled.")
+    ![Build settings to autoconnect profiler#center](images/ac.webp "Figure 1. Build settings with connected Android device and Autoconnect Profiler enabled.")
 
 3. Select _Build and Run_