Merge branch 'release/3.2.1'

Author: lindyhopchris

1.0/routing/custom-actions.md

@@ -302,7 +302,7 @@ JsonApiRoute::server('v1')
                 $relationships->hasOne('author')->readOnly();
                 $relationships->hasMany('tags');
             })->actions('-actions', function ($actions) {
-                $actions->withId()->post('purge');
+                $actions->withId()->post('publish');
             });
 
         // ...other resources

2.0/routing/custom-actions.md

@@ -302,7 +302,7 @@ JsonApiRoute::server('v1')
                 $relationships->hasOne('author')->readOnly();
                 $relationships->hasMany('tags');
             })->actions('-actions', function ($actions) {
-                $actions->withId()->post('purge');
+                $actions->withId()->post('publish');
             });
 
         // ...other resources

3.0/routing/README.md

@@ -490,3 +490,14 @@ JsonApiRoute::server('v1')
         $server->resource('posts', PostController::class);
     });
 ```
+
+## Writing Regular Laravel Routes
+
+You are not constrained to just using the routing from this package!
+
+If you need to create some routes and actions that deviate from JSON:API conventions,
+you can just create an endpoint in exactly the way you would when using Laravel -
+i.e. register a route, write a controller.
+
+If you want to return a JSON:API response from the controller, you can use one of the
+package's [response classes](../responses/).

3.0/routing/custom-actions.md

@@ -304,7 +304,7 @@ JsonApiRoute::server('v1')
                 $relationships->hasOne('author')->readOnly();
                 $relationships->hasMany('tags');
             })->actions('-actions', function (ActionRegistrar $actions) {
-                $actions->withId()->post('purge');
+                $actions->withId()->post('publish');
             });
 
         // ...other resources