add line break between list tags (#7655)

billing.md

@@ -1791,6 +1791,7 @@ First, you could redirect your customer to the dedicated payment confirmation pa
 On the payment confirmation page, the customer will be prompted to enter their credit card information again and perform any additional actions required by Stripe, such as "3D Secure" confirmation. After confirming their payment, the user will be redirected to the URL provided by the `redirect` parameter specified above. Upon redirection, `message` (string) and `success` (integer) query string variables will be added to the URL. The payment page currently supports the following payment method types:
 
 <div class="content-list" markdown="1">
+
 - Credit Cards
 - Alipay
 - Bancontact
@@ -1799,6 +1800,7 @@ On the payment confirmation page, the customer will be prompted to enter their c
 - Giropay
 - iDEAL
 - SEPA Direct Debit
+
 </div>
 
 Alternatively, you could allow Stripe to handle the payment confirmation for you. In this case, instead of redirecting to the payment confirmation page, you may [setup Stripe's automatic billing emails](https://dashboard.stripe.com/account/billing/automatic) in your Stripe dashboard. However, if an `IncompletePayment` exception is caught, you should still inform the user they will receive an email with further payment confirmation instructions.

blade.md

@@ -848,13 +848,15 @@ You may retrieve a specific attribute's value using the `get` method:
 By default, some keywords are reserved for Blade's internal use in order to render components. The following keywords cannot be defined as public properties or method names within your components:
 
 <div class="content-list" markdown="1">
+
 - `data`
 - `render`
 - `resolveView`
 - `shouldRender`
 - `view`
 - `withAttributes`
 - `withName`
+
 </div>
 
 <a name="slots"></a>

cashier-paddle.md

@@ -995,11 +995,13 @@ Once your listener has been defined, you may register it within your application
 Cashier also emit events dedicated to the type of the received webhook. In addition to the full payload from Paddle, they also contain the relevant models that were used to process the webhook such as the billable model, the subscription, or the receipt:
 
 <div class="content-list" markdown="1">
+
 - `Laravel\Paddle\Events\PaymentSucceeded`
 - `Laravel\Paddle\Events\SubscriptionPaymentSucceeded`
 - `Laravel\Paddle\Events\SubscriptionCreated`
 - `Laravel\Paddle\Events\SubscriptionUpdated`
 - `Laravel\Paddle\Events\SubscriptionCancelled`
+
 </div>
 
 You can also override the default, built-in webhook route by defining the `CASHIER_WEBHOOK` environment variable in your application's `.env` file. This value should be the full URL to your webhook route and needs to match the URL set in your Paddle control panel:

contributions.md

@@ -23,6 +23,7 @@ Remember, bug reports are created in the hope that others with the same problem
 The Laravel source code is managed on GitHub, and there are repositories for each of the Laravel projects:
 
 <div class="content-list" markdown="1">
+
 - [Laravel Application](https://github.com/laravel/laravel)
 - [Laravel Art](https://github.com/laravel/art)
 - [Laravel Documentation](https://github.com/laravel/docs)
@@ -43,6 +44,7 @@ The Laravel source code is managed on GitHub, and there are repositories for eac
 - [Laravel Socialite](https://github.com/laravel/socialite)
 - [Laravel Telescope](https://github.com/laravel/telescope)
 - [Laravel Website](https://github.com/laravel/laravel.com-next)
+
 </div>
 
 <a name="support-questions"></a>
@@ -51,13 +53,15 @@ The Laravel source code is managed on GitHub, and there are repositories for eac
 Laravel's GitHub issue trackers are not intended to provide Laravel help or support. Instead, use one of the following channels:
 
 <div class="content-list" markdown="1">
+
 - [GitHub Discussions](https://github.com/laravel/framework/discussions)
 - [Laracasts Forums](https://laracasts.com/discuss)
 - [Laravel.io Forums](https://laravel.io/forum)
 - [StackOverflow](https://stackoverflow.com/questions/tagged/laravel)
 - [Discord](https://discord.gg/laravel)
 - [Larachat](https://larachat.co)
 - [IRC](https://web.libera.chat/?nick=artisan&channels=#laravel)
+
 </div>
 
 <a name="core-development-discussion"></a>
@@ -124,8 +128,10 @@ Don't worry if your code styling isn't perfect! [StyleCI](https://styleci.io/) w
 The Laravel code of conduct is derived from the Ruby code of conduct. Any violations of the code of conduct may be reported to Taylor Otwell ([email protected]):
 
 <div class="content-list" markdown="1">
+
 - Participants will be tolerant of opposing views.
 - Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
 - When interpreting the words and actions of others, participants should always assume good intentions.
 - Behavior that can be reasonably considered harassment will not be tolerated.
+
 </div>

database.md

@@ -15,10 +15,12 @@
 Almost every modern web application interacts with a database. Laravel makes interacting with databases extremely simple across a variety of supported databases using raw SQL, a [fluent query builder](/docs/{{version}}/queries), and the [Eloquent ORM](/docs/{{version}}/eloquent). Currently, Laravel provides first-party support for four databases:
 
 <div class="content-list" markdown="1">
+
 - MySQL 5.7+ ([Version Policy](https://en.wikipedia.org/wiki/MySQL#Release_history))
 - PostgreSQL 9.6+ ([Version Policy](https://www.postgresql.org/support/versioning/))
 - SQLite 3.8.8+
 - SQL Server 2017+ ([Version Policy](https://docs.microsoft.com/en-us/lifecycle/products/?products=sql-server))
+
 </div>
 
 <a name="configuration"></a>

deployment.md

@@ -23,6 +23,7 @@ When you're ready to deploy your Laravel application to production, there are so
 The Laravel framework has a few system requirements. You should ensure that your web server has the following minimum PHP version and extensions:
 
 <div class="content-list" markdown="1">
+
 - PHP >= 7.3
 - BCMath PHP Extension
 - Ctype PHP Extension
@@ -33,6 +34,7 @@ The Laravel framework has a few system requirements. You should ensure that your
 - PDO PHP Extension
 - Tokenizer PHP Extension
 - XML PHP Extension
+
 </div>
 
 <a name="server-configuration"></a>

eloquent-mutators.md

@@ -119,6 +119,7 @@ Attribute casting provides functionality similar to accessors and mutators witho
 The `$casts` property should be an array where the key is the name of the attribute being cast and the value is the type you wish to cast the column to. The supported cast types are:
 
 <div class="content-list" markdown="1">
+
 - `array`
 - `AsStringable::class`
 - `boolean`
@@ -139,6 +140,7 @@ The `$casts` property should be an array where the key is the name of the attrib
 - `real`
 - `string`
 - `timestamp`
+
 </div>
 
 To demonstrate attribute casting, let's cast the `is_admin` attribute, which is stored in our database as an integer (`0` or `1`) to a boolean value:

eloquent-relationships.md

@@ -45,6 +45,7 @@
 Database tables are often related to one another. For example, a blog post may have many comments or an order could be related to the user who placed it. Eloquent makes managing and working with these relationships easy, and supports a variety of common relationships:
 
 <div class="content-list" markdown="1">
+
 - [One To One](#one-to-one)
 - [One To Many](#one-to-many)
 - [Many To Many](#many-to-many)
@@ -53,6 +54,7 @@ Database tables are often related to one another. For example, a blog post may h
 - [One To One (Polymorphic)](#one-to-one-polymorphic-relations)
 - [One To Many (Polymorphic)](#one-to-many-polymorphic-relations)
 - [Many To Many (Polymorphic)](#many-to-many-polymorphic-relations)
+
 </div>
 
 <a name="defining-relationships"></a>

homestead.md

@@ -473,8 +473,10 @@ After updating the `Homestead.yaml` file, be sure to re-provision the machine by
 By default, the following ports are forwarded to your Homestead environment:
 
 <div class="content-list" markdown="1">
+
 - **HTTP:** 8000 &rarr; Forwards To 80
 - **HTTPS:** 44300 &rarr; Forwards To 443
+
 </div>
 
 <a name="forwarding-additional-ports"></a>
@@ -492,13 +494,15 @@ If you wish, you may forward additional ports to the Vagrant box by defining a `
 Below is a list of additional Homestead service ports that you may wish to map from your host machine to your Vagrant box:
 
 <div class="content-list" markdown="1">
+
 - **SSH:** 2222 &rarr; To 22
 - **ngrok UI:** 4040 &rarr; To 4040
 - **MySQL:** 33060 &rarr; To 3306
 - **PostgreSQL:** 54320 &rarr; To 5432
 - **MongoDB:** 27017 &rarr; To 27017
 - **Mailhog:** 8025 &rarr; To 8025
 - **Minio:** 9600 &rarr; To 9600
+
 </div>
 
 <a name="php-versions"></a>

installation.md

@@ -181,9 +181,11 @@ php artisan serve
 Make sure to place Composer's system-wide vendor bin directory in your `$PATH` so the `laravel` executable can be located by your system. This directory exists in different locations based on your operating system; however, some common locations include:
 
 <div class="content-list" markdown="1">
+
 - macOS: `$HOME/.composer/vendor/bin`
 - Windows: `%USERPROFILE%\AppData\Roaming\Composer\vendor\bin`
 - GNU / Linux Distributions: `$HOME/.config/composer/vendor/bin` or `$HOME/.composer/vendor/bin`
+
 </div>
 
 For convenience, the Laravel installer can also create a Git repository for your new project. To indicate that you want a Git repository to be created, pass the `--git` flag when creating a new project:
@@ -243,11 +245,13 @@ Laravel should always be served out of the root of the "web directory" configure
 Now that you have created your Laravel project, you may be wondering what to learn next. First, we strongly recommend becoming familiar with how Laravel works by reading the following documentation:
 
 <div class="content-list" markdown="1">
+
 - [Request Lifecycle](/docs/{{version}}/lifecycle)
 - [Configuration](/docs/{{version}}/configuration)
 - [Directory Structure](/docs/{{version}}/structure)
 - [Service Container](/docs/{{version}}/container)
 - [Facades](/docs/{{version}}/facades)
+
 </div>
 
 How you want to use Laravel will also dictate the next steps on your journey. There are a variety of ways to use Laravel, and we'll explore two primary use cases for the framework below.

mix.md

@@ -216,9 +216,11 @@ Mix provides several features to help you work with your JavaScript files, such
 With this single line of code, you may now take advantage of:
 
 <div class="content-list" markdown="1">
+
 - The latest EcmaScript syntax.
 - Modules
 - Minification for production environments.
+
 </div>
 
 <a name="vue"></a>
@@ -270,9 +272,11 @@ If you intend to make frequent updates to your application's JavaScript, you sho
 The `extract` method accepts an array of all libraries or modules that you wish to extract into a `vendor.js` file. Using the snippet above as an example, Mix will generate the following files:
 
 <div class="content-list" markdown="1">
+
 - `public/js/manifest.js`: *The Webpack manifest runtime*
 - `public/js/vendor.js`: *Your vendor libraries*
 - `public/js/app.js`: *Your application code*
+
 </div>
 
 To avoid JavaScript errors, be sure to load these files in the proper order:

queues.md

@@ -130,9 +130,11 @@ Adjusting this value based on your queue load can be more efficient than continu
 The following dependencies are needed for the listed queue drivers. These dependencies may be installed via the Composer package manager:
 
 <div class="content-list" markdown="1">
+
 - Amazon SQS: `aws/aws-sdk-php ~3.0`
 - Beanstalkd: `pda/pheanstalk ~4.0`
 - Redis: `predis/predis ~1.0` or phpredis PHP extension
+
 </div>
 
 <a name="creating-jobs"></a>

session.md

@@ -29,12 +29,14 @@ Your application's session configuration file is stored at `config/session.php`.
 The session `driver` configuration option defines where session data will be stored for each request. Laravel ships with several great drivers out of the box:
 
 <div class="content-list" markdown="1">
+
 - `file` - sessions are stored in `storage/framework/sessions`.
 - `cookie` - sessions are stored in secure, encrypted cookies.
 - `database` - sessions are stored in a relational database.
 - `memcached` / `redis` - sessions are stored in one of these fast, cache based stores.
 - `dynamodb` - sessions are stored in AWS DynamoDB.
 - `array` - sessions are stored in a PHP array and will not be persisted.
+
 </div>
 
 > {tip} The array driver is primarily used during [testing](/docs/{{version}}/testing) and prevents the data stored in the session from being persisted.
@@ -290,12 +292,14 @@ If none of the existing session drivers fit your application's needs, Laravel ma
 Since the purpose of these methods is not readily understandable, let's quickly cover what each of the methods do:
 
 <div class="content-list" markdown="1">
+
 - The `open` method would typically be used in file based session store systems. Since Laravel ships with a `file` session driver, you will rarely need to put anything in this method. You can simply leave this method empty.
 - The `close` method, like the `open` method, can also usually be disregarded. For most drivers, it is not needed.
 - The `read` method should return the string version of the session data associated with the given `$sessionId`. There is no need to do any serialization or other encoding when retrieving or storing session data in your driver, as Laravel will perform the serialization for you.
 - The `write` method should write the given `$data` string associated with the `$sessionId` to some persistent storage system, such as MongoDB or another storage system of your choice.  Again, you should not perform any serialization - Laravel will have already handled that for you.
 - The `destroy` method should remove the data associated with the `$sessionId` from persistent storage.
 - The `gc` method should destroy all session data that is older than the given `$lifetime`, which is a UNIX timestamp. For self-expiring systems like Memcached and Redis, this method may be left empty.
+
 </div>
 
 <a name="registering-the-driver"></a>

upgrade.md

@@ -6,23 +6,27 @@
 ## High Impact Changes
 
 <div class="content-list" markdown="1">
+
 - [Model Factories](#model-factories)
 - [Queue `retryAfter` Method](#queue-retry-after-method)
 - [Queue `timeoutAt` Property](#queue-timeout-at-property)
 - [Queue `allOnQueue` and `allOnConnection`](#queue-allOnQueue-allOnConnection)
 - [Pagination Defaults](#pagination-defaults)
 - [Seeder & Factory Namespaces](#seeder-factory-namespaces)
+
 </div>
 
 <a name="medium-impact-changes"></a>
 ## Medium Impact Changes
 
 <div class="content-list" markdown="1">
+
 - [PHP 7.3.0 Required](#php-7.3.0-required)
 - [Failed Jobs Table Batch Support](#failed-jobs-table-batch-support)
 - [Maintenance Mode Updates](#maintenance-mode-updates)
 - [The `php artisan down --message` Option](#artisan-down-message)
 - [The `assertExactJson` Method](#assert-exact-json-method)
+
 </div>
 
 <a name="upgrade-8.0"></a>
@@ -46,21 +50,25 @@ The new minimum PHP version is now 7.3.0.
 Update the following dependencies in your `composer.json` file:
 
 <div class="content-list" markdown="1">
+
 - `guzzlehttp/guzzle` to `^7.0.1`
 - `facade/ignition` to `^2.3.6`
 - `laravel/framework` to `^8.0`
 - `laravel/ui` to `^3.0`
 - `nunomaduro/collision` to `^5.0`
 - `phpunit/phpunit` to `^9.0`
+
 </div>
 
 The following first-party packages have new major releases to support Laravel 8. If applicable, you should read their individual upgrade guides before upgrading:
 
 <div class="content-list" markdown="1">
+
 - [Horizon v5.0](https://github.com/laravel/horizon/blob/master/UPGRADE.md)
 - [Passport v10.0](https://github.com/laravel/passport/blob/master/UPGRADE.md)
 - [Socialite v5.0](https://github.com/laravel/socialite/blob/master/UPGRADE.md)
 - [Telescope v4.0](https://github.com/laravel/telescope/blob/master/UPGRADE.md)
+
 </div>
 
 In addition, the Laravel installer has been updated to support `composer create-project` and Laravel Jetstream. Any installer older than 4.0 will cease to work after October 2020. You should upgrade your global installer to `^4.0` as soon as possible.

validation.md

@@ -1050,11 +1050,13 @@ The field under validation must be formatted as an email address. This validatio
 The example above will apply the `RFCValidation` and `DNSCheckValidation` validations. Here's a full list of validation styles you can apply:
 
 <div class="content-list" markdown="1">
+
 - `rfc`: `RFCValidation`
 - `strict`: `NoRFCWarningsValidation`
 - `dns`: `DNSCheckValidation`
 - `spoof`: `SpoofCheckValidation`
 - `filter`: `FilterEmailValidation`
+
 </div>
 
 The `filter` validator, which uses PHP's `filter_var` function, ships with Laravel and was Laravel's default email validation behavior prior to Laravel version 5.8.