Fix table overflow

authorization.md

@@ -654,6 +654,8 @@ The `authorizeResource` method accepts the model's class name as its first argum
 
 The following controller methods will be mapped to their corresponding policy method. When requests are routed to the given controller method, the corresponding policy method will automatically be invoked before the controller method is executed:
 
+<div class="overflow-auto">
+
 | Controller Method | Policy Method |
 | --- | --- |
 | index | viewAny |
@@ -664,6 +666,8 @@ The following controller methods will be mapped to their corresponding policy me
 | update | update |
 | destroy | delete |
 
+</div>
+
 > **Note**  
 > You may use the `make:policy` command with the `--model` option to quickly generate a policy class for a given model: `php artisan make:policy PostPolicy --model=Post`.
 

facades.md

@@ -243,6 +243,8 @@ When the real-time facade is used, the publisher implementation will be resolved
 
 Below you will find every facade and its underlying class. This is a useful tool for quickly digging into the API documentation for a given facade root. The [service container binding](/docs/{{version}}/container) key is also included where applicable.
 
+<div class="overflow-auto">
+
 Facade  |  Class  |  Service Container Binding
 ------------- | ------------- | -------------
 App  |  [Illuminate\Foundation\Application](https://laravel.com/api/{{version}}/Illuminate/Foundation/Application.html)  |  `app`
@@ -293,3 +295,5 @@ Validator (Instance)  |  [Illuminate\Validation\Validator](https://laravel.com/a
 View  |  [Illuminate\View\Factory](https://laravel.com/api/{{version}}/Illuminate/View/Factory.html)  |  `view`
 View (Instance)  |  [Illuminate\View\View](https://laravel.com/api/{{version}}/Illuminate/View/View.html)  |  &nbsp;
 Vite  |  [Illuminate\Foundation\Vite](https://laravel.com/api/{{version}}/Illuminate/Foundation/Vite.html)  |  &nbsp;
+
+</div>

logging.md

@@ -46,6 +46,8 @@ By default, Monolog is instantiated with a "channel name" that matches the curre
 
 Each log channel is powered by a "driver". The driver determines how and where the log message is actually recorded. The following log channel drivers are available in every Laravel application. An entry for most of these drivers is already present in your application's `config/logging.php` configuration file, so be sure to review this file to become familiar with its contents:
 
+<div class="overflow-auto">
+
 Name | Description
 ------------- | -------------
 `custom` | A driver that calls a specified factory to create a channel
@@ -59,6 +61,8 @@ Name | Description
 `stack` | A wrapper to facilitate creating "multi-channel" channels
 `syslog` | A `SyslogHandler` based Monolog driver
 
+</div>
+
 > **Note**  
 > Check out the documentation on [advanced channel customization](#monolog-channel-customization) to learn more about the `monolog` and `custom` drivers.
 
@@ -70,18 +74,26 @@ Name | Description
 
 The `single` and `daily` channels have three optional configuration options: `bubble`, `permission`, and `locking`.
 
+<div class="overflow-auto">
+
 Name | Description | Default
 ------------- | ------------- | -------------
 `bubble` | Indicates if messages should bubble up to other channels after being handled | `true`
 `locking` | Attempt to lock the log file before writing to it | `false`
 `permission` | The log file's permissions | `0644`
 
+</div>
+
 Additionally, the retention policy for the `daily` channel can be configured via the `days` option:
 
+<div class="overflow-auto">
+
 Name | Description                                                       | Default
 ------------- |-------------------------------------------------------------------| -------------
 `days` | The number of days that daily log files should be retained | `7`
 
+</div>
+
 <a name="configuring-the-papertrail-channel"></a>
 #### Configuring The Papertrail Channel
 

releases.md

@@ -21,13 +21,18 @@ When referencing the Laravel framework or its components from your application o
 
 For all Laravel releases, bug fixes are provided for 18 months and security fixes are provided for 2 years. For all additional libraries, including Lumen, only the latest major release receives bug fixes. In addition, please review the database versions [supported by Laravel](/docs/{{version}}/database#introduction).
 
+
+<div class="overflow-auto">
+
 | Version | PHP (*) | Release | Bug Fixes Until | Security Fixes Until |
 | --- | --- | --- | --- | --- |
 | 8 | 7.3 - 8.1 | September 8th, 2020 | July 26th, 2022 | January 24th, 2023 |
 | 9 | 8.0 - 8.1 | February 8th, 2022 | August 8th, 2023 | February 6th, 2024 |
 | 10 | 8.1 | February 7th, 2023 | August 6th, 2024 | February 4th, 2025 |
 | 11 | 8.2 | February 6th, 2024 | August 5th, 2025 | February 3rd, 2026 |
 
+</div>
+
 <div class="version-colors">
     <div class="end-of-life">
         <div class="color-box"></div>

scheduling.md

@@ -101,6 +101,8 @@ The `exec` method may be used to issue a command to the operating system:
 
 We've already seen a few examples of how you may configure a task to run at specified intervals. However, there are many more task schedule frequencies that you may assign to a task:
 
+<div class="overflow-auto">
+
 Method  | Description
 ------------- | -------------
 `->cron('* * * * *');`  |  Run the task on a custom cron schedule
@@ -135,6 +137,8 @@ Method  | Description
 `->yearlyOn(6, 1, '17:00');`  |  Run the task every year on June 1st at 17:00
 `->timezone('America/New_York');` | Set the timezone for the task
 
+</div>
+
 These methods may be combined with additional constraints to create even more finely tuned schedules that only run on certain days of the week. For example, you may schedule a command to run weekly on Monday:
 
     // Run once per week on Monday at 1 PM...
@@ -151,6 +155,8 @@ These methods may be combined with additional constraints to create even more fi
 
 A list of additional schedule constraints may be found below:
 
+<div class="overflow-auto">
+
 Method  | Description
 ------------- | -------------
 `->weekdays();`  |  Limit the task to weekdays
@@ -168,6 +174,8 @@ Method  | Description
 `->when(Closure);`  |  Limit the task based on a truth test
 `->environments($env);`  |  Limit the task to specific environments
 
+</div>
+
 <a name="day-constraints"></a>
 #### Day Constraints
 

valet.md

@@ -458,6 +458,8 @@ If you would like to define a custom Valet driver for a single application, crea
 <a name="other-valet-commands"></a>
 ## Other Valet Commands
 
+<div class="overflow-auto">
+
 Command  | Description
 ------------- | -------------
 `valet list` | Display a list of all Valet commands.
@@ -470,6 +472,8 @@ Command  | Description
 `valet trust` | Add sudoers files for Brew and Valet to allow Valet commands to be run without prompting for your password.
 `valet uninstall` | Uninstall Valet: shows instructions for manual uninstall. Pass the `--force` option to aggressively delete all of Valet's resources.
 
+</div>
+
 <a name="valet-directories-and-files"></a>
 ## Valet Directories & Files