remove empty lines

Author: Sven Schleier

tests-beta/android/MASVS-AUTH/MASTG-TEST-0326.md

@@ -14,10 +14,8 @@ best-practices: []
 
 !!! note
     Android offers the `BiometricPrompt` class in 2 different ways:
-    
     1. Via the [androidx.biometric](https://developer.android.com/reference/androidx/biometric/BiometricPrompt) library (Jetpack), which provides backward compatibility to API level 23.
     2. The built-in [android.hardware.biometrics](https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt) framework API (available from API level 28+)
-
     The examples in this test uses the `android.hardware.biometrics` framework API.
 
 This test checks if the app uses biometric authentication mechanisms that allow fallback to device credentials (PIN, pattern, or password) for sensitive operations. On Android, the [`BiometricPrompt`](https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt) API can be configured to accept different types of [`BiometricManager.Authenticators`](https://developer.android.com/reference/android/hardware/biometrics/BiometricManager.Authenticators#constants_1) via the method[`setAllowedAuthenticators`](https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt.Builder#setAllowedAuthenticators(int)).

tests-beta/android/MASVS-AUTH/MASTG-TEST-0327.md

@@ -14,10 +14,8 @@ best-practices: []
 
 !!! note
     Android offers the `BiometricPrompt` class in 2 different ways:
-    
     1. Via the [androidx.biometric](https://developer.android.com/reference/androidx/biometric/BiometricPrompt) library (Jetpack), which provides backward compatibility to API level 23.
     2. The built-in [android.hardware.biometrics](https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt) framework API (available from API level 28+)
-
     The examples in this test uses the `android.hardware.biometrics` framework API.
 
 This test checks if the app implements event-bound biometric authentication to access sensitive resources (e.g., tokens, keys), where authentication success relies solely on a callback result rather than being cryptographically bound to sensitive operations and requiring user presence.

tests-beta/android/MASVS-AUTH/MASTG-TEST-0328.md

@@ -14,10 +14,8 @@ best-practices: []
 
 !!! note
     Android offers the `BiometricPrompt` class in 2 different ways:
-    
     1. Via the [androidx.biometric](https://developer.android.com/reference/androidx/biometric/BiometricPrompt) library (Jetpack), which provides backward compatibility to API level 23.
     2. The built-in [android.hardware.biometrics](https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt) framework API (available from API level 28+)
-
     The examples in this test uses the `android.hardware.biometrics` framework API.
 
 This test checks whether the app fails to protect sensitive operations against unauthorized access following biometric enrollment changes. An attacker who obtains the device passcode could add a new fingerprint or facial representation via system settings and use it to authenticate in the app.

tests-beta/android/MASVS-AUTH/MASTG-TEST-0329.md

@@ -14,10 +14,8 @@ best-practices: []
 
 !!! note
     Android offers the `BiometricPrompt` class in 2 different ways:
-    
     1. Via the [androidx.biometric](https://developer.android.com/reference/androidx/biometric/BiometricPrompt) library (Jetpack), which provides backward compatibility to API level 23.
     2. The built-in [android.hardware.biometrics](https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt) framework API (available from API level 28+)
-
     The examples in this test uses the `android.hardware.biometrics` framework API.
 
 This test checks if the app enforces biometric authentication [without requiring explicit user action](https://developer.android.com/identity/sign-in/biometric-auth#no-explicit-user-action). When using [`BiometricPrompt`](https://developer.android.com/reference/androidx/biometric/BiometricPrompt), the [`setConfirmationRequired()`](https://developer.android.com/reference/androidx/biometric/BiometricPrompt.PromptInfo.Builder#setConfirmationRequired(boolean)) method in [`BiometricPrompt.PromptInfo.Builder`](https://developer.android.com/reference/androidx/biometric/BiometricPrompt.PromptInfo.Builder) controls whether the user must explicitly confirm their authentication, which is enforced by default.

tests-beta/android/MASVS-AUTH/MASTG-TEST-0330.md

@@ -14,10 +14,8 @@ best-practices: []
 
 !!! note
     Android offers the `BiometricPrompt` class in 2 different ways:
-    
     1. Via the [androidx.biometric](https://developer.android.com/reference/androidx/biometric/BiometricPrompt) library (Jetpack), which provides backward compatibility to API level 23.
     2. The built-in [android.hardware.biometrics](https://developer.android.com/reference/android/hardware/biometrics/BiometricPrompt) framework API (available from API level 28+)
-
     The examples in this test uses the `android.hardware.biometrics` framework API.
 
 This test checks if the app configures cryptographic keys with an extended validity duration that allows keys to remain unlocked beyond the immediate operation. When using biometric authentication with [`CryptoObject`](https://developer.android.com/reference/androidx/biometric/BiometricPrompt.CryptoObject), the authentication validity duration determines how long a key remains usable after successful authentication.