Update markdown tables (#9778)

* Update tables

* Fix quotes

* Update `<x-mail::table>` examples

* Add overflow-auto div to tables

* Update requests.md

Author: TENIOS

authentication.md

@@ -741,17 +741,17 @@ Once the configuration file has been published, you may set the `rehash_on_login
 
 Laravel dispatches a variety of [events](/docs/{{version}}/events) during the authentication process. You may [define listeners](/docs/{{version}}/events) for any of the following events:
 
-Event Name |
-------------- |
-`Illuminate\Auth\Events\Registered` |
-`Illuminate\Auth\Events\Attempting` |
-`Illuminate\Auth\Events\Authenticated` |
-`Illuminate\Auth\Events\Login` |
-`Illuminate\Auth\Events\Failed` |
-`Illuminate\Auth\Events\Validated` |
-`Illuminate\Auth\Events\Verified` |
-`Illuminate\Auth\Events\Logout` |
-`Illuminate\Auth\Events\CurrentDeviceLogout` |
-`Illuminate\Auth\Events\OtherDeviceLogout` |
-`Illuminate\Auth\Events\Lockout` |
-`Illuminate\Auth\Events\PasswordReset` |
+| Event Name |
+| --- |
+| `Illuminate\Auth\Events\Registered` |
+| `Illuminate\Auth\Events\Attempting` |
+| `Illuminate\Auth\Events\Authenticated` |
+| `Illuminate\Auth\Events\Login` |
+| `Illuminate\Auth\Events\Failed` |
+| `Illuminate\Auth\Events\Validated` |
+| `Illuminate\Auth\Events\Verified` |
+| `Illuminate\Auth\Events\Logout` |
+| `Illuminate\Auth\Events\CurrentDeviceLogout` |
+| `Illuminate\Auth\Events\OtherDeviceLogout` |
+| `Illuminate\Auth\Events\Lockout` |
+| `Illuminate\Auth\Events\PasswordReset` |

blade.md

@@ -423,8 +423,10 @@ If you are in a nested loop, you may access the parent loop's `$loop` variable v
 
 The `$loop` variable also contains a variety of other useful properties:
 
+<div class="overflow-auto">
+
 | Property           | Description                                            |
-|--------------------|--------------------------------------------------------|
+| ------------------ | ------------------------------------------------------ |
 | `$loop->index`     | The index of the current loop iteration (starts at 0). |
 | `$loop->iteration` | The current loop iteration (starts at 1).              |
 | `$loop->remaining` | The iterations remaining in the loop.                  |
@@ -436,6 +438,8 @@ The `$loop` variable also contains a variety of other useful properties:
 | `$loop->depth`     | The nesting level of the current loop.                 |
 | `$loop->parent`    | When in a nested loop, the parent's loop variable.     |
 
+</div>
+
 <a name="conditional-classes"></a>
 ### Conditional Classes & Styles
 

cache.md

@@ -440,12 +440,12 @@ Once your extension is registered, update the `CACHE_STORE` environment variable
 
 To execute code on every cache operation, you may listen for various [events](/docs/{{version}}/events) dispatched by the cache:
 
-Event Name |
-------------- |
-`Illuminate\Cache\Events\CacheHit` |
-`Illuminate\Cache\Events\CacheMissed` |
-`Illuminate\Cache\Events\KeyForgotten` |
-`Illuminate\Cache\Events\KeyWritten` |
+| Event Name |
+| --- |
+| `Illuminate\Cache\Events\CacheHit` |
+| `Illuminate\Cache\Events\CacheMissed` |
+| `Illuminate\Cache\Events\KeyForgotten` |
+| `Illuminate\Cache\Events\KeyWritten` |
 
 To increase performance, you may disable cache events by setting the `events` configuration option to `false` for a given cache store in your application's `config/cache.php` configuration file:
 

configuration.md

@@ -72,7 +72,7 @@ Before loading your application's environment variables, Laravel determines if a
 All variables in your `.env` files are typically parsed as strings, so some reserved values have been created to allow you to return a wider range of types from the `env()` function:
 
 | `.env` Value | `env()` Value |
-|--------------|---------------|
+| ------------ | ------------- |
 | true         | (bool) true   |
 | (true)       | (bool) true   |
 | false        | (bool) false  |

contracts.md

@@ -181,15 +181,19 @@ You may even register many resource controllers at once by passing an array to t
 <a name="actions-handled-by-resource-controllers"></a>
 #### Actions Handled by Resource Controllers
 
-Verb      | URI                    | Action       | Route Name
-----------|------------------------|--------------|---------------------
-GET       | `/photos`              | index        | photos.index
-GET       | `/photos/create`       | create       | photos.create
-POST      | `/photos`              | store        | photos.store
-GET       | `/photos/{photo}`      | show         | photos.show
-GET       | `/photos/{photo}/edit` | edit         | photos.edit
-PUT/PATCH | `/photos/{photo}`      | update       | photos.update
-DELETE    | `/photos/{photo}`      | destroy      | photos.destroy
+<div class="overflow-auto">
+
+| Verb      | URI                    | Action  | Route Name     |
+| --------- | ---------------------- | ------- | -------------- |
+| GET       | `/photos`              | index   | photos.index   |
+| GET       | `/photos/create`       | create  | photos.create  |
+| POST      | `/photos`              | store   | photos.store   |
+| GET       | `/photos/{photo}`      | show    | photos.show    |
+| GET       | `/photos/{photo}/edit` | edit    | photos.edit    |
+| PUT/PATCH | `/photos/{photo}`      | update  | photos.update  |
+| DELETE    | `/photos/{photo}`      | destroy | photos.destroy |
+
+</div>
 
 <a name="customizing-missing-model-behavior"></a>
 #### Customizing Missing Model Behavior
@@ -305,15 +309,19 @@ Often, it is not entirely necessary to have both the parent and the child IDs wi
 
 This route definition will define the following routes:
 
-Verb      | URI                               | Action       | Route Name
-----------|-----------------------------------|--------------|---------------------
-GET       | `/photos/{photo}/comments`        | index        | photos.comments.index
-GET       | `/photos/{photo}/comments/create` | create       | photos.comments.create
-POST      | `/photos/{photo}/comments`        | store        | photos.comments.store
-GET       | `/comments/{comment}`             | show         | comments.show
-GET       | `/comments/{comment}/edit`        | edit         | comments.edit
-PUT/PATCH | `/comments/{comment}`             | update       | comments.update
-DELETE    | `/comments/{comment}`             | destroy      | comments.destroy
+<div class="overflow-auto">
+
+| Verb      | URI                               | Action  | Route Name             |
+| --------- | --------------------------------- | ------- | ---------------------- |
+| GET       | `/photos/{photo}/comments`        | index   | photos.comments.index  |
+| GET       | `/photos/{photo}/comments/create` | create  | photos.comments.create |
+| POST      | `/photos/{photo}/comments`        | store   | photos.comments.store  |
+| GET       | `/comments/{comment}`             | show    | comments.show          |
+| GET       | `/comments/{comment}/edit`        | edit    | comments.edit          |
+| PUT/PATCH | `/comments/{comment}`             | update  | comments.update        |
+| DELETE    | `/comments/{comment}`             | destroy | comments.destroy       |
+
+</div>
 
 <a name="restful-naming-resource-routes"></a>
 ### Naming Resource Routes
@@ -407,11 +415,15 @@ Route::singleton('profile', ProfileController::class);
 
 The singleton resource definition above will register the following routes. As you can see, "creation" routes are not registered for singleton resources, and the registered routes do not accept an identifier since only one instance of the resource may exist:
 
-Verb      | URI                               | Action       | Route Name
-----------|-----------------------------------|--------------|---------------------
-GET       | `/profile`                        | show         | profile.show
-GET       | `/profile/edit`                   | edit         | profile.edit
-PUT/PATCH | `/profile`                        | update       | profile.update
+<div class="overflow-auto">
+
+| Verb      | URI             | Action | Route Name     |
+| --------- | --------------- | ------ | -------------- |
+| GET       | `/profile`      | show   | profile.show   |
+| GET       | `/profile/edit` | edit   | profile.edit   |
+| PUT/PATCH | `/profile`      | update | profile.update |
+
+</div>
 
 Singleton resources may also be nested within a standard resource:
 
@@ -421,11 +433,15 @@ Route::singleton('photos.thumbnail', ThumbnailController::class);
 
 In this example, the `photos` resource would receive all of the [standard resource routes](#actions-handled-by-resource-controller); however, the `thumbnail` resource would be a singleton resource with the following routes:
 
-| Verb      | URI                              | Action  | Route Name               |
-|-----------|----------------------------------|---------|--------------------------|
-| GET       | `/photos/{photo}/thumbnail`      | show    | photos.thumbnail.show    |
-| GET       | `/photos/{photo}/thumbnail/edit` | edit    | photos.thumbnail.edit    |
-| PUT/PATCH | `/photos/{photo}/thumbnail`      | update  | photos.thumbnail.update  |
+<div class="overflow-auto">
+
+| Verb      | URI                              | Action | Route Name              |
+| --------- | -------------------------------- | ------ | ----------------------- |
+| GET       | `/photos/{photo}/thumbnail`      | show   | photos.thumbnail.show   |
+| GET       | `/photos/{photo}/thumbnail/edit` | edit   | photos.thumbnail.edit   |
+| PUT/PATCH | `/photos/{photo}/thumbnail`      | update | photos.thumbnail.update |
+
+</div>
 
 <a name="creatable-singleton-resources"></a>
 #### Creatable Singleton Resources
@@ -438,15 +454,19 @@ Route::singleton('photos.thumbnail', ThumbnailController::class)->creatable();
 
 In this example, the following routes will be registered. As you can see, a `DELETE` route will also be registered for creatable singleton resources:
 
+<div class="overflow-auto">
+
 | Verb      | URI                                | Action  | Route Name               |
-|-----------|------------------------------------|---------|--------------------------|
+| --------- | ---------------------------------- | ------- | ------------------------ |
 | GET       | `/photos/{photo}/thumbnail/create` | create  | photos.thumbnail.create  |
 | POST      | `/photos/{photo}/thumbnail`        | store   | photos.thumbnail.store   |
 | GET       | `/photos/{photo}/thumbnail`        | show    | photos.thumbnail.show    |
 | GET       | `/photos/{photo}/thumbnail/edit`   | edit    | photos.thumbnail.edit    |
 | PUT/PATCH | `/photos/{photo}/thumbnail`        | update  | photos.thumbnail.update  |
 | DELETE    | `/photos/{photo}/thumbnail`        | destroy | photos.thumbnail.destroy |
 
+</div>
+
 If you would like Laravel to register the `DELETE` route for a singleton resource but not register the creation or storage routes, you may utilize the `destroyable` method:
 
 ```php