spelling: use

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
fastlane · rogerluan · Jan 18, 2024 · Jan 14, 2024 · Jan 14, 2024 · Jan 14, 2024
commit 316f1e13b50c9cdbc3d00fccf8ebe78d34033fb2
diff --git a/docs/getting-started/android/screenshots.md b/docs/getting-started/android/screenshots.md
@@ -92,7 +92,7 @@ public class ExampleInstrumentedTest {
 }
 
 ```
-There is an [example project](https://github.com/fastlane/fastlane/tree/master/screengrab/example/src/androidTest/java/tools/fastlane/localetester) showing how to use use JUnit 3 or 4 and Espresso with the screengrab Java library to capture screenshots during a UI test run.
+There is an [example project](https://github.com/fastlane/fastlane/tree/master/screengrab/example/src/androidTest/java/tools/fastlane/localetester) showing how to use JUnit 3 or 4 and Espresso with the screengrab Java library to capture screenshots during a UI test run.
 
 Using JUnit 4 is preferable because of its ability to perform actions before and after the entire test class is run. This means you will change the device's locale far fewer times when compared with JUnit 3 running those commands before and after each test method.
-Original file line number
+Diff line change
@@ Expand Up / @@ -92,7 +92,7 @@ public class ExampleInstrumentedTest { @@
     }
     ```
-    There is an [example project](https://github.com/fastlane/fastlane/tree/master/screengrab/example/src/androidTest/java/tools/fastlane/localetester) showing how to use use JUnit 3 or 4 and Espresso with the screengrab Java library to capture screenshots during a UI test run.
+    There is an [example project](https://github.com/fastlane/fastlane/tree/master/screengrab/example/src/androidTest/java/tools/fastlane/localetester) showing how to use JUnit 3 or 4 and Espresso with the screengrab Java library to capture screenshots during a UI test run.
     Using JUnit 4 is preferable because of its ability to perform actions before and after the entire test class is run. This means you will change the device's locale far fewer times when compared with JUnit 3 running those commands before and after each test method.
@@ Expand Down @@