Fix markdown formatting (#10260)

Author: AhmedAlaa4611

mail.md

@@ -379,7 +379,7 @@ public function content(): Content
 }
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > You may wish to create a `resources/views/emails` directory to house all of your email templates; however, you are free to place them wherever you wish within your `resources/views` directory.
 
 <a name="plain-text-emails"></a>
@@ -637,7 +637,7 @@ Embedding inline images into your emails is typically cumbersome; however, Larav
 </body>
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > The `$message` variable is not available in plain-text message templates since plain-text messages do not utilize inline attachments.
 
 <a name="embedding-raw-data-attachments"></a>
@@ -851,7 +851,7 @@ Thanks,<br>
 </x-mail::message>
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > Do not use excess indentation when writing Markdown emails. Per Markdown standards, Markdown parsers will render indented content as code blocks.
 
 <a name="button-component"></a>
@@ -1073,7 +1073,7 @@ class OrderShipped extends Mailable implements ShouldQueue
 }
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > To learn more about working around these issues, please review the documentation regarding [queued jobs and database transactions](/docs/{{version}}/queues#jobs-and-database-transactions).
 
 <a name="rendering-mailables"></a>

middleware.md

@@ -60,7 +60,7 @@ As you can see, if the given `token` does not match our secret token, the middle
 
 It's best to envision middleware as a series of "layers" HTTP requests must pass through before they hit your application. Each layer can examine the request and even reject it entirely.
 
-> [!NOTE]  
+> [!NOTE]
 > All middleware are resolved via the [service container](/docs/{{version}}/container), so you may type-hint any dependencies you need within a middleware's constructor.
 
 <a name="middleware-and-responses"></a>
@@ -325,7 +325,7 @@ If you would like to manually manage all of the middleware within Laravel's defa
 })
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > By default, the `web` and `api` middleware groups are automatically applied to your application's corresponding `routes/web.php` and `routes/api.php` files by the `bootstrap/app.php` file.
 
 <a name="middleware-aliases"></a>

migrations.md

@@ -44,7 +44,7 @@ Laravel will use the name of the migration to attempt to guess the name of the t
 
 If you would like to specify a custom path for the generated migration, you may use the `--path` option when executing the `make:migration` command. The given path should be relative to your application's base path.
 
-> [!NOTE]  
+> [!NOTE]
 > Migration stubs may be customized using [stub publishing](/docs/{{version}}/artisan#stub-customization).
 
 <a name="squashing-migrations"></a>
@@ -70,7 +70,7 @@ php artisan schema:dump --database=testing --prune
 
 You should commit your database schema file to source control so that other new developers on your team may quickly create your application's initial database structure.
 
-> [!WARNING]  
+> [!WARNING]
 > Migration squashing is only available for the MariaDB, MySQL, PostgreSQL, and SQLite databases and utilizes the database's command-line client.
 
 <a name="migration-structure"></a>
@@ -165,7 +165,7 @@ When the `isolated` option is provided, Laravel will acquire an atomic lock usin
 php artisan migrate --isolated
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > To utilize this feature, your application must be using the `memcached`, `redis`, `dynamodb`, `database`, `file`, or `array` cache driver as your application's default cache driver. In addition, all servers must be communicating with the same central cache server.
 
 <a name="forcing-migrations-to-run-in-production"></a>
@@ -245,7 +245,7 @@ By default, the `migrate:fresh` command only drops tables from the default datab
 php artisan migrate:fresh --database=admin
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > The `migrate:fresh` command will drop all database tables regardless of their prefix. This command should be used with caution when developing on a database that is shared with other applications.
 
 <a name="tables"></a>
@@ -722,7 +722,7 @@ The `geography` method creates a `GEOGRAPHY` equivalent column with the given sp
 $table->geography('coordinates', subtype: 'point', srid: 4326);
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > Support for spatial types depends on your database driver. Please refer to your database's documentation. If your application is utilizing a PostgreSQL database, you must install the [PostGIS](https://postgis.net) extension before the `geography` method may be used.
 
 <a name="column-method-geometry"></a>
@@ -734,7 +734,7 @@ The `geometry` method creates a `GEOMETRY` equivalent column with the given spat
 $table->geometry('positions', subtype: 'point', srid: 0);
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > Support for spatial types depends on your database driver. Please refer to your database's documentation. If your application is utilizing a PostgreSQL database, you must install the [PostGIS](https://postgis.net) extension before the `geometry` method may be used.
 
 <a name="column-method-id"></a>
@@ -1229,7 +1229,7 @@ return new class extends Migration
 };
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > Support for default expressions depends on your database driver, database version, and the field type. Please refer to your database's documentation.
 
 <a name="column-order"></a>
@@ -1508,7 +1508,7 @@ Schema::withoutForeignKeyConstraints(function () {
 });
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > SQLite disables foreign key constraints by default. When using SQLite, make sure to [enable foreign key support](/docs/{{version}}/database#configuration) in your database configuration before attempting to create them in your migrations.
 
 <a name="events"></a>

mix.md

@@ -16,5 +16,5 @@ mix.js('resources/js/app.js', 'public/js')
 
 If you've ever been confused and overwhelmed about getting started with webpack and asset compilation, you will love Laravel Mix. However, you are not required to use it while developing your application; you are free to use any asset pipeline tool you wish, or even none at all.
 
-> [!NOTE]  
+> [!NOTE]
 > Vite has replaced Laravel Mix in new Laravel installations. For Mix documentation, please visit the [official Laravel Mix](https://laravel-mix.com/) website. If you would like to switch to Vite, please see our [Vite migration guide](https://github.com/laravel/vite-plugin/blob/main/UPGRADE.md#migrating-from-laravel-mix-to-vite).

mocking.md

@@ -154,7 +154,7 @@ class UserControllerTest extends TestCase
 }
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > You should not mock the `Request` facade. Instead, pass the input you desire into the [HTTP testing methods](/docs/{{version}}/http-tests) such as `get` and `post` when running your test. Likewise, instead of mocking the `Config` facade, call the `Config::set` method in your tests.
 
 <a name="facade-spies"></a>

mongodb.md

@@ -66,7 +66,7 @@ Finally, use Composer to install the Laravel MongoDB package:
 composer require mongodb/laravel-mongodb
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > This installation of the package will fail if the `mongodb` PHP extension is not installed. The PHP configuration can differ between the CLI and the web server, so ensure the extension is enabled in both configurations.
 
 <a name="configuration"></a>

notifications.md

@@ -831,7 +831,7 @@ Thanks,<br>
 </x-mail::message>
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > Do not use excess indentation when writing Markdown emails. Per Markdown standards, Markdown parsers will render indented content as code blocks.
 
 <a name="button-component"></a>

octane.md

@@ -47,7 +47,7 @@ php artisan octane:install
 <a name="server-prerequisites"></a>
 ## Server Prerequisites
 
-> [!WARNING]  
+> [!WARNING]
 > Laravel Octane requires [PHP 8.1+](https://php.net/releases/).
 
 <a name="frankenphp"></a>
@@ -204,7 +204,7 @@ Using Laravel Octane with Open Swoole grants the same functionality provided by
 <a name="swoole-via-laravel-sail"></a>
 #### Swoole via Laravel Sail
 
-> [!WARNING]  
+> [!WARNING]
 > Before serving an Octane application via Sail, ensure you have the latest version of Laravel Sail and execute `./vendor/bin/sail build --no-cache` within your application's root directory.
 
 Alternatively, you may develop your Swoole based Octane application using [Laravel Sail](/docs/{{version}}/sail), the official Docker based development environment for Laravel. Laravel Sail includes the Swoole extension by default. However, you will still need to adjust the `docker-compose.yml` file used by Sail.
@@ -261,7 +261,7 @@ By default, applications running via Octane generate links prefixed with `http:/
 <a name="serving-your-application-via-nginx"></a>
 ### Serving Your Application via Nginx
 
-> [!NOTE]  
+> [!NOTE]
 > If you aren't quite ready to manage your own server configuration or aren't comfortable configuring all of the various services needed to run a robust Laravel Octane application, check out [Laravel Cloud](https://cloud.laravel.com), which offers fully-managed Laravel Octane support.
 
 In production environments, you should serve your Octane application behind a traditional web server such as Nginx or Apache. Doing so will allow the web server to serve your static assets such as images and stylesheets, as well as manage your SSL certificate termination.
@@ -482,7 +482,7 @@ $service->method($request->input('name'));
 
 The global `request` helper will always return the request the application is currently handling and is therefore safe to use within your application.
 
-> [!WARNING]  
+> [!WARNING]
 > It is acceptable to type-hint the `Illuminate\Http\Request` instance on your controller methods and route closures.
 
 <a name="configuration-repository-injection"></a>
@@ -553,7 +553,7 @@ While building your application, you should take special care to avoid creating
 <a name="concurrent-tasks"></a>
 ## Concurrent Tasks
 
-> [!WARNING]  
+> [!WARNING]
 > This feature requires [Swoole](#swoole).
 
 When using Swoole, you may execute operations concurrently via light-weight background tasks. You may accomplish this using Octane's `concurrently` method. You may combine this method with PHP array destructuring to retrieve the results of each operation:
@@ -580,7 +580,7 @@ When invoking the `concurrently` method, you should not provide more than 1024 t
 <a name="ticks-and-intervals"></a>
 ## Ticks and Intervals
 
-> [!WARNING]  
+> [!WARNING]
 > This feature requires [Swoole](#swoole).
 
 When using Swoole, you may register "tick" operations that will be executed every specified number of seconds. You may register "tick" callbacks via the `tick` method. The first argument provided to the `tick` method should be a string that represents the name of the ticker. The second argument should be a callable that will be invoked at the specified interval.
@@ -603,7 +603,7 @@ Octane::tick('simple-ticker', fn () => ray('Ticking...'))
 <a name="the-octane-cache"></a>
 ## The Octane Cache
 
-> [!WARNING]  
+> [!WARNING]
 > This feature requires [Swoole](#swoole).
 
 When using Swoole, you may leverage the Octane cache driver, which provides read and write speeds of up to 2 million operations per second. Therefore, this cache driver is an excellent choice for applications that need extreme read / write speeds from their caching layer.
@@ -614,7 +614,7 @@ This cache driver is powered by [Swoole tables](https://www.swoole.co.uk/docs/mo
 Cache::store('octane')->put('framework', 'Laravel', 30);
 ```
 
-> [!NOTE]  
+> [!NOTE]
 > The maximum number of entries allowed in the Octane cache may be defined in your application's `octane` configuration file.
 
 <a name="cache-intervals"></a>
@@ -633,7 +633,7 @@ Cache::store('octane')->interval('random', function () {
 <a name="tables"></a>
 ## Tables
 
-> [!WARNING]  
+> [!WARNING]
 > This feature requires [Swoole](#swoole).
 
 When using Swoole, you may define and interact with your own arbitrary [Swoole tables](https://www.swoole.co.uk/docs/modules/swoole-table). Swoole tables provide extreme performance throughput and the data in these tables can be accessed by all workers on the server. However, the data within them will be lost when the server is restarted.
@@ -662,5 +662,5 @@ Octane::table('example')->set('uuid', [
 return Octane::table('example')->get('uuid');
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > The column types supported by Swoole tables are: `string`, `int`, and `float`.

packages.md

@@ -111,7 +111,7 @@ Now, when users of your package execute Laravel's `vendor:publish` command, your
 $value = config('courier.option');
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > You should not define closures in your configuration files. They cannot be serialized correctly when users execute the `config:cache` Artisan command.
 
 <a name="default-package-configuration"></a>
@@ -133,7 +133,7 @@ public function register(): void
 }
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > This method only merges the first level of the configuration array. If your users partially define a multi-dimensional configuration array, the missing options will not be merged.
 
 <a name="routes"></a>

pagination.md

@@ -137,7 +137,7 @@ $users = DB::table('users')->orderBy('id')->cursorPaginate(15);
 
 Once you have retrieved a cursor paginator instance, you may [display the pagination results](#displaying-pagination-results) as you typically would when using the `paginate` and `simplePaginate` methods. For more information on the instance methods offered by the cursor paginator, please consult the [cursor paginator instance method documentation](#cursor-paginator-instance-methods).
 
-> [!WARNING]  
+> [!WARNING]
 > Your query must contain an "order by" clause in order to take advantage of cursor pagination. In addition, the columns that the query are ordered by must belong to the table you are paginating.
 
 <a name="cursor-vs-offset-pagination"></a>
@@ -174,7 +174,7 @@ The `Paginator` and `CursorPaginator` classes do not need to know the total numb
 
 In other words, the `Paginator` corresponds to the `simplePaginate` method on the query builder, the `CursorPaginator` corresponds to the `cursorPaginate` method, and the `LengthAwarePaginator` corresponds to the `paginate` method.
 
-> [!WARNING]  
+> [!WARNING]
 > When manually creating a paginator instance, you should manually "slice" the array of results you pass to the paginator. If you're unsure how to do this, check out the [array_slice](https://secure.php.net/manual/en/function.array-slice.php) PHP function.
 
 <a name="customizing-pagination-urls"></a>