Fix image alt text for the Tests chapter.

tests/android/physical_devices.adoc

@@ -26,32 +26,36 @@ all branches.
 
 Start by clicking on **App Settings**.
 
-image:img/Builds---Settings.png[,1500,483]
+image:img/Builds---Settings.png["The buddybuild dashboard", 1500, 483]
 
 In the left navigation, click on **Test settings**.
 
-image:img/Tests---menu.jpg[,1500,606]
+image:img/Tests---menu.jpg["The Test settings button", 1500, 606]
 
 Next, locate **Run UI tests on physical devices** and click **Configure**.
 
-image:img/Tests---physical-configure.jpg[,1500,606]
+image:img/Tests---physical-configure.jpg["The Default test configuration
+screen", 1500, 606]
 
 [WARNING]
 =========
 **Running UI tests on physical devices are charged per minute of use**
 
-Annual plan subscribers will be invoiced once a month for running UI
-tests on physical devices.
+Annual plan subscribers are invoiced once a month for running UI tests
+on physical devices.
 =========
 
 Turn on **UI tests on physical devices**, then select the **variant**
 you would like to run UI tests against.
 
-image:img/Tests---physical-select-variant.jpg[,1500,543]
+image:img/Tests---physical-select-variant.jpg["Selecting a variant to
+test", 1500, 543]
 
 Lastly, select the physical devices you want to run UI tests on.
 
-image:img/Tests---physical-select-device.jpg[,1500,543]
+image:img/Tests---physical-select-device.jpg["The physical device
+selection screen", 1500, 543]
+
 
 === Run UI tests on physical devices for a specific branch only
 
@@ -62,12 +66,14 @@ Under **Override build configuration**, click **Add a branch** and
 select the branch you would like to run UI tests on physical devices
 for.
 
-image:img/Builds---Branch-override---1.png[,1500,555]
+image:img/Builds---Branch-override---1.png["The branch override dropdown
+menu", 1500, 555]
 
 Select **Run UI tests on physical devices** from the dropdown, then
 click the **Configure** button.
 
-image:img/Tests---physical-branch-override.jpg[,1500,543]
+image:img/Tests---physical-branch-override.jpg["Enabling UI tests for a
+specific branch", 1500, 543]
 
 You can now select the physical devices you want to run UI tests on for
 your selected branch.

tests/android/virtual_devices.adoc

@@ -1,9 +1,9 @@
 = UI Tests on Virtual Devices
 
-Ensure your Android app runs seamlessly on the exact devices your user
-base owns. Buddybuild supports numerous mobile devices across different
-OS versions and vendors. Select which virtual devices to run your UI
-tests against, and buddybuild will automate the rest!
+To ensure that your Android app runs seamlessly on the exact devices
+your user base owns, buddybuild supports numerous mobile devices across
+different OS versions and vendors. Select which virtual devices to run
+your UI tests against, and buddybuild automates the rest!
 
 [NOTE]
 ======
@@ -24,24 +24,28 @@ branches.
 
 Start by clicking on **App Settings**.
 
-image:img/Builds---Settings.png[,1500,483]
+image:img/Builds---Settings.png["The buddybuild dashboard", 1500, 483]
 
 In the left navigation, click on **Test settings**.
 
-image:img/Tests---menu.jpg[,1500,606]
+image:img/Tests---menu.jpg["The Test settings button", 1500, 606]
 
 Next, locate **Run UI tests on virtual devices** and click **Configure**.
 
-image:img/Tests---virtual-configure.jpg[,1500,606]
+image:img/Tests---virtual-configure.jpg["The Default test configuration
+screen", 1500, 606]
 
 Turn on **UI tests on virtual devices**, then select the **variant** you
 would like to run UI tests against.
 
-image:img/Tests---virtual-select-variant.jpg[,1500,543]
+image:img/Tests---virtual-select-variant.jpg["Selecting a variant for UI
+testing", 1500, 543]
 
 Lastly, select the virtual devices you want to run UI tests on.
 
-image:img/Tests---virtual-select-device.jpg[,1500,543]
+image:img/Tests---virtual-select-device.jpg["The Select virtual device
+screen", 1500, 543]
+
 
 == Run UI tests on virtual devices for a specific branch only
 
@@ -51,12 +55,14 @@ creating a **branch-specific override**.
 Under Override build configuration, click **Add a branch** and select
 the branch you would like to run UI tests on virtual devices for.
 
-image:img/Builds---Branch-override---1.png[,1500,555]
+image:img/Builds---Branch-override---1.png["The branch override dropdown
+menu", 1500, 555]
 
 Select **Run UI tests on virtual devices** from the dropdown, then click
 the **Configure** button.
 
-image:img/Tests---virtual-branch-override.jpg[,1500,543]
+image:img/Tests---virtual-branch-override.jpg["Enabling UI tests for a
+specific branch", 1500, 543]
 
 You can now select the virtual devices you want to run UI tests on for
 your selected branch.

tests/ios/configure_ui_tests_video_recording.adoc

@@ -47,7 +47,7 @@ instructions] to update the SDK on your local machine.
 . Click the **Add** button.
 --
 +
-image:img/1.png[,1500,861]
+image:img/1.png["The Project Navigator view in Xcode", 1500, 861]
 
 [[step4]]
 == Step 4: Initialize the buddybuild SDK
@@ -194,7 +194,7 @@ Go to the buddybuild dashboard and make sure that Tests are enabled in
 buddybuild. This setting can be found in the **'App Settings'** of your
 app.
 
-image:img/3.png[,1500,466]
+image:img/3.png["The Tests setting in the buddybuild dashboard", 1500, 466]
 
 [[step8]]
 == Step 8: Commit and push

tests/ios/tests.adoc

@@ -1,13 +1,13 @@
 = Unit Tests
 
-Buddybuild will automatically scan for your **XCTests** and run them for
+Buddybuild automatically scans for your **XCTests** and runs them for
 you as part of every build! No configuration required!
 
-If you like to see the test run details, simply navigate to the
-**Tests** tab in the build details page. See pass/fail counts, suite and
-test level results.
+To see the test run details, simply navigate to the **Tests** tab in the
+build details page. See pass/fail counts, suite- and test-level results.
 
-image:img/Builds---Tests.png[,1500,847]
+image:img/Builds---Tests.png["The Build Details page, with the Tests tab
+selected, showing XCTest results", 1500, 847]
 
 You also have access to the full test logs from the **Logs** tab under
 Build Details.