Prettified Code!

Author: rawilk

docs/installation.md

@@ -103,14 +103,15 @@ to either extend or completely change the component's functionality by using a c
 and/or view of your own.
 
 ### Component Namespace
+
 New in v6, the package also declares a `form-components` blade component namespace. This means that
 for any component you may also use the `<x-form-components::component-name>` syntax. For the `input`
 component, you would use `<x-form-components::inputs.input />`. If you choose to render the components
 using this method, you can safely remove the component alias from the config, however there are two caveats to this:
 
 1. You may not be able to override the component class definition any more if you remove the alias from the config.
 2. Some components have an array of configuration options attached to their alias. Those arrays are referenced
-by the component, so these aliases should not be removed or renamed.
+   by the component, so these aliases should not be removed or renamed.
 
 ## Component JavaScript
 

docs/requirements.md

@@ -14,7 +14,7 @@ sort: 2
 
 ## Version Matrix
 
-| Laravel | Minimum Version | Maximum Version |
-| ------- | --------------- | --- |
-| 8.0 - 8.55    | 1.0.0           | 5.1.0 |
-| 8.56 | 6.0.0 | |
+| Laravel    | Minimum Version | Maximum Version |
+| ---------- | --------------- | --------------- |
+| 8.0 - 8.55 | 1.0.0           | 5.1.0           |
+| 8.56       | 6.0.0           |                 |

docs/upgrade.md

@@ -6,14 +6,17 @@ sort: 4
 ## Upgrading from v5 to v6
 
 ### Laravel Version
+
 v6 of laravel-form-components now requires a minimum Laravel version of `8.56`. Be sure to update your project to at least that version.
 
 ### Overriding component views
+
 In v6, you must publish any package views you want to override instead of specifying a different view in the config. This was done to help
 simplify the package config and how the base `BladeComponent` class determines the view to render. You are still free to override any
 component classes in the config, however.
 
 ### New Component Namespace
+
 Not a breaking change, but the package now defines the `form-components` namespace in addition to providing aliases for each component
 in the config. You will now be able to reference components either as `<x-form>` or as `<x-form-components::form>` if you choose to.