Merge pull request #903 from codeigniter4/datamweb-fix-docs

docs: fix small items

Author: datamweb

docs/addons/jwt.md

@@ -33,9 +33,10 @@ To use JWT Authentication, you need additional setup and configuration.
 2. Copy the **AuthJWT.php** from **vendor/codeigniter4/shield/src/Config/** into your project's config folder and update the namespace to `Config`. You will also need to have these classes extend the original classes. See the example below.
 
     ```php
-    // new file - app/Config/AuthJWT.php
     <?php
-
+    
+    // app/Config/AuthJWT.php
+    
     declare(strict_types=1);
 
     namespace Config;
@@ -140,7 +141,10 @@ $routes->post('auth/jwt', '\App\Controllers\Auth\LoginController::jwtLogin');
 ```
 
 ```php
+<?php
+
 // app/Controllers/Auth/LoginController.php
+
 declare(strict_types=1);
 
 namespace App\Controllers\Auth;
@@ -260,6 +264,7 @@ file itself:
 $routes->group('api', ['filter' => 'jwt'], static function ($routes) {
     // ...
 });
+
 $routes->get('users', 'UserController::list', ['filter' => 'jwt']);
 ```
 

docs/customization/integrating_custom_view_libs.md

@@ -5,6 +5,12 @@ If your application uses a different method to convert view files to HTML than C
 All controllers and actions use the `CodeIgniter\Shield\Traits\Viewable` trait which provides a simple `view()` method that takes the same arguments as the `view()` helper. This allows you to extend the Action or Controller and only change the single method of rendering the view, leaving all of the logic untouched so your app will not need to maintain Shield logic when it doesn't need to change it.
 
 ```php
+<?php
+
+declare(strict_types=1);
+
+namespace App\Controllers;
+
 use Acme\Themes\Traits\Themeable;
 use CodeIgniter\Shield\Controllers\LoginController;
 

docs/getting_started/concepts.md

@@ -70,7 +70,7 @@ systems that are appropriate for your application. The following Validators are
 You can choose which validators are used in `Config\Auth::$passwordValidators`:
 
 ```php
-public $passwordValidators = [
+public array $passwordValidators = [
     CompositionValidator::class,
     NothingPersonalValidator::class,
     DictionaryValidator::class,

docs/guides/mobile_apps.md

@@ -9,11 +9,15 @@ Typically, a mobile application would issue a request from their login screen, p
 Start by creating a route that would handle the request from the login screen on the mobile device. The device name can be any arbitrary string, but is typically used to identify the device the request is being made from, like "Johns iPhone 13".
 
 ```php
-
 // Routes.php
 $routes->post('auth/token', '\App\Controllers\Auth\LoginController::mobileLogin');
+```
+
+```php
+<?php
+
+// app/Controllers/Auth/LoginController.php
 
-// LoginController.php
 namespace App\Controllers\Auth;
 
 use App\Controllers\BaseController;

docs/references/authentication/authentication.md

@@ -12,7 +12,7 @@ You can see the [Authenticator List](../../getting_started/authenticators.md).
 The available authenticators are defined in `Config\Auth`:
 
 ```php
-public $authenticators = [
+public array $authenticators = [
     // alias  => classname
     'session' => Session::class,
     'tokens'  => AccessTokens::class,
@@ -24,7 +24,7 @@ public $authenticators = [
 The default authenticator is also defined in the configuration file, and uses the alias given above:
 
 ```php
-public $defaultAuthenticator = 'session';
+public string $defaultAuthenticator = 'session';
 ```
 
 ## Auth Helper

docs/references/events.md

@@ -44,8 +44,7 @@ Events::on('failedLogin', function($credentials) {
     dd($credentials);
 });
 
-// Outputs:
-['email' => 'foo@example.com'];
+// Outputs: ['email' => 'foo@example.com'];
 ```
 
 When the magic link login fails, the following array will be provided: