Update docs

Author: simonhamp

resources/views/docs/mobile/1/digging-deeper/security.md

@@ -10,7 +10,7 @@ protect your users.
 
 ### Secrets and .env
 
-As your application is being installed on systems outside of your/your organisation's control, it is important to think
+As your application is being installed on systems outside your/your organisation's control, it is important to think
 of the environment that it's in as _potentially_ hostile, which is to say that any secrets, passwords or keys
 could fall into the hands of someone who might try to abuse them.
 
@@ -22,7 +22,7 @@ application and any API use a robust and secure authentication protocol, such as
 distribute unique and expiring tokens (an expiration date less than 48 hours in the future is recommended) with a high
 level of entropy, as this makes them hard to guess and hard to abuse.
 
-Always use HTTPS.
+**Always use HTTPS.**
 
 If your application allows users to connect _their own_ API keys for a service, you should treat these keys with great
 care. If you choose to store them anywhere (either in a [File](files) or

resources/views/docs/mobile/1/the-basics/dialogs.md

@@ -10,7 +10,7 @@ NativePHP allows you to trigger many native dialogs.
 Dialogs are created using the `Dialog` facade.
 
 ```php
-use Native\Laravel\Dialog;
+use Native\Ios\Facades\Dialog;
 ```
 
 ### The Share Dialog
@@ -31,7 +31,7 @@ $buttons = [
     'Cancel'
 ];
 
-Dialog::share('Title', 'Message', $buttons, fn ($selected) => {
+Dialog::alert('Title', 'Message', $buttons, fn ($selected) => {
     echo "You selected {$buttons[$selected]}";
 });
 ```

resources/views/docs/mobile/1/the-basics/notifications.md

@@ -6,15 +6,15 @@ order: 500
 ## Notifications
 
 NativePHP allows you to send system notifications using an elegant PHP API. These notifications are, unlike Laravel's
-built-in notifications, actual UI notifications displayed by the device's native notification UI.
+built-in notifications, actual device notifications displayed by the device's native notification UI.
 
 When used sparingly, notifications can be a great way to inform the user about events that are occurring in your
 application and to bring their attention back to it, especially if further input from them is required.
 
 Notifications are sent using the `Notification` facade.
 
 ```php
-use Native\Laravel\Facades\Notification;
+use Native\Ios\Facades\Notification;
 ```
 
 ### Sending Notifications

resources/views/docs/mobile/1/the-basics/system.md

@@ -22,12 +22,12 @@ about whether a particular feature is specific to iOS or Android.
 Most of the system-related features are available through the `System` facade.
 
 ```php
-use Native\Laravel\Facades\System;
+use Native\Ios\Facades\System;
 ```
 
 ## Camera
 
-You may request the native camera interface to take a photograph by calling:
+You may request the native camera interface to take a photograph by calling the `camera` method:
 
 ```php
 $imageData = System::camera()
@@ -50,6 +50,40 @@ decline, triggering the camera API will silently fail.**
 
 **COMING SOON**
 
+## Vibration
+
+You may vibrate the user's device by calling the `vibrate` method:
+
+```php
+System::vibrate()
+```
+
+## Push Notifications
+
+NativePHP makes it dead simple to enrol your user's device in push notifications from your app.
+
+Simply use the `enrolForPushNotifications` method to trigger enrolment. If this is the first time that your app tries
+to enrol this device for push notifications, the user will be presented with a native alert, allowing them to opt-in.
+
+Then use the `getPushNotificationsToken` method to retrieve the token. If enrolment was unsuccessful for some reason,
+this method will return `null`.
+
+```php
+System::enrolForPushNotifications();
+
+// Later...
+
+if ($token = System::getPushNotificationsToken()) {
+    // Do something with the token...
+}
+```
+
+Once you have the token, you may use it from your server-based applications to trigger Push Notifications directly to
+your user's device.
+
+Find out more about what's required to use Push Notifications in
+[Apple's Developer docs](https://developer.apple.com/notifications/).
+
 ## Accelerometer
 
 **COMING SOON**
@@ -115,23 +149,24 @@ For devices that support some form of biometric identification, you can use this
 of your application.
 
 ```php
-if (System::canPromptBiometricID() && System::promptBiometricID('access your Contacts')) {
+if (System::promptForBiometricID()) {
     // Do your super secret activity here
 }
 ```
 
 Using this, you can gate certain parts of your app, allowing you to offer an extra layer of protection for your user's
 data.
 
-**Note: Biometric identification only gives you greater *confidence* that the person using your app is someone who has
-the capacity to unlock the device your app is installed on. It does not allow you to *identify* that user or prove that
-they are willingly taking this action.**
+**Note: Despite the name, Biometric identification only gives you *greater confidence* that the person using your app
+is *someone* who has the capacity to unlock the device your app is installed on. It does not allow you to *identify*
+that user or prove that they are willingly taking this action.**
 
 ## Time Zones
 
 **COMING SOON**
 
-PHP and your Laravel application will be configured to work with the time zone that the device is configured to use.
+PHP and your Laravel application are configured to work with the time zone that the device reports it is currently
+operating in.
 
 This means that, for the most part, any dates and times your show will already be in the appropriate time zone for the
 user without having to ask your users to manually select their current time zone.