Update method names

Author: simonhamp

resources/views/docs/mobile/1/apis/biometrics.md

@@ -14,14 +14,14 @@ use Native\Mobile\Facades\Biometrics;
 
 ## Methods
 
-### `promptForBiometricID()`
+### `prompt()`
 
 Prompts the user for biometric authentication.
 
 ```php
 use Native\Mobile\Facades\Biometrics;
 
-Biometrics::promptForBiometricID();
+Biometrics::prompt();
 ```
 
 ## Events

resources/views/docs/mobile/1/apis/push-notifications.md

@@ -13,15 +13,15 @@ use Native\Mobile\Facades\PushNotifications;
 
 ## Methods
 
-### `enrollForPushNotifications()`
+### `enroll()`
 
 Requests permission and enrolls the device for push notifications.
 
 **Returns:** `void`
 
-### `getPushNotificationsToken()`
+### `getToken()`
 
-Retrieves the current FCM token for this device.
+Retrieves the current push notification token for this device.
 
 **Returns:** `string|null` - The FCM token, or `null` if not available
 
@@ -48,7 +48,7 @@ public function handlePushToken(string $token)
 ## Permission Flow
 
 1. User taps "Enable Notifications"
-2. App calls `enrollForPushNotifications()`
+2. App calls `enroll()`
 3. System shows permission dialog
 4. If granted, FCM generates token
 5. `TokenGenerated` event fires with token

resources/views/docs/mobile/1/concepts/push-notifications.md

@@ -52,12 +52,12 @@ It's common practice to request push notification permissions during app bootup
 - The app is updated
 - Other internal FCM operations
 
-To request a token, use the `PushNotifications::getPushNotificationsToken()` method:
+To request a token, use the `PushNotifications::getToken()` method:
 
 ```php
 use Native\Mobile\Facades\PushNotifications;
 
-PushNotifications::getPushNotificationsToken();
+PushNotifications::getToken();
 ```
 
 If the user has approved your app to use push notifications and the request to FCM succeeded, a `TokenGenerated` event