Update docs

Author: andrey-helldar

docs/.vuepress/config.js

@@ -71,9 +71,10 @@ export default defineUserConfig({
 
         navbar: [
             {
-                text: '5.x',
+                text: '6.x',
                 children: [
-                    {text: '5.x', link: '/getting-started/installation/index.md'},
+                    {text: '6.x', link: '/getting-started/installation/index.md'},
+                    {text: '5.x', link: 'https://github.com/TheDragonCode/laravel-deploy-operations/blob/5.x/docs/index.md'},
                     {text: '4.x', link: 'https://github.com/TheDragonCode/laravel-deploy-operations/blob/4.x/docs/index.md'},
                     {text: '3.x', link: 'https://github.com/TheDragonCode/laravel-deploy-operations/blob/3.x/docs/index.md'},
                 ]

docs/getting-started/installation/index.md

@@ -1,6 +1,6 @@
 # Installation
 
-To get the latest version of `Deploy Operations for Laravel`, simply require the project using [Composer](https://getcomposer.org):
+To get the latest version of `Deploy Operations for Laravel`, require the project using [Composer](https://getcomposer.org):
 
 ```bash
 composer require dragon-code/laravel-deploy-operations

docs/helpers/artisan.md

@@ -1,11 +1,12 @@
 # Artisan Command
 
-Quite often, when working with operations, it becomes necessary to run one or another console command, and each time you have to write the following code:
+Quite often, when working with operations, it becomes necessary to run one or another console command,
+and each time you have to write the following code:
 
 ```php
 use DragonCode\LaravelDeployOperations\Operation;
 
-return new class () extends Operation
+return new class extends Operation
 {
     public function __invoke(): void
     {

docs/helpers/events.md

@@ -11,7 +11,8 @@ DragonCode\LaravelDeployOperations\Events\NoPendingDeployOperations::class
 
 If there are no operation files to execute, the `NoPendingDeployOperations` event will be sent.
 
-In other cases, the `DeployOperationStarted` event will be sent before processing starts, and the `DeployOperationEnded` event will be sent after processing.
+In other cases, the `DeployOperationStarted` event will be sent before processing starts,
+and the `DeployOperationEnded` event will be sent after processing.
 
 For example:
 

docs/helpers/execution-status.md

@@ -8,7 +8,7 @@ You can also override the `success` and `failed` methods, which are called on su
 use DragonCode\LaravelDeployOperations\Operation;
 use Illuminate\Support\Facade\Log;
 
-return new class () extends Operation
+return new class extends Operation
 {
     public function up(): void
     {

docs/how-to-use/creating.md

@@ -71,7 +71,7 @@ By default, the new operation class will contain the `__invoke` method, but you
 ```php
 use DragonCode\LaravelDeployOperations\Operation;
 
-return new class () extends Operation
+return new class extends Operation
 {
     public function __invoke(): void
     {
@@ -88,7 +88,7 @@ return new class () extends Operation
 ```php
 use DragonCode\LaravelDeployOperations\Operation;
 
-return new class () extends Operation
+return new class extends Operation
 {
     public function __invoke(): void {} // called when `php artisan operations` running
 
@@ -105,7 +105,7 @@ You can also use the dependency injection with `__invoke`, `up` and `down` metho
 use DragonCode\LaravelDeployOperations\Operation;
 use Tests\Concerns\Some;
 
-return new class () extends Operation
+return new class extends Operation
 {
     public function __invoke(Some $some): void
     {
@@ -118,7 +118,7 @@ return new class () extends Operation
 use DragonCode\LaravelDeployOperations\Operation;
 use Tests\Concerns\Some;
 
-return new class () extends Operation
+return new class extends Operation
 {
     public function up(Some $some): void
     {

docs/how-to-use/rollback.md

@@ -1,12 +1,12 @@
 # Rolling Back Operations
 
-To roll back the latest operation, you may use the `rollback` command. This command rolls back the last "batch" of actions, which may include multiple action files:
+To roll back the latest operation, you may use the `rollback` command. This command rolls back the last "batch" of operations, which may include multiple operation files:
 
 ```
 php artisan operations:rollback
 ```
 
-You may roll back a limited number of operations by providing the `step` option to the rollback command. For example, the following command will roll back the last five actions:
+You may roll back a limited number of operations by providing the `step` option to the rollback command. For example, the following command will roll back the last five operations:
 
 ```
 php artisan operations:rollback --step=5
@@ -48,7 +48,7 @@ php artisan operations:rollback --step=2
 
 ## Roll Back & Operation Using A Single Command
 
-The `operations:refresh` command will roll back all of your actions and then execute the `actions` command. This command effectively re-creates your entire
+The `operations:refresh` command will roll back all of your operations and then execute the `operations` command. This command effectively re-creates your entire
 database:
 
 ```
@@ -64,8 +64,8 @@ php artisan operations:refresh --step=5
 
 ## Drop All & Rerun Operations
 
-The `operations:fresh` command will drop all operations records from the operations table and then execute the operations command:
+The `operations:fresh` command will drop all operation records from the operation table and then execute the operations command:
 
 ```
-php artisan actions:fresh
+php artisan operations:fresh
 ```

docs/how-to-use/running.md

@@ -120,15 +120,15 @@ return new class extends Operation
 
 If the value is `$once = false`, the `up` method will be called every time the `operations` command called.
 
-In this case, information about it will not be written to the `actions` table and, therefore, the `down` method will not be called when the rollback command is called.
+In this case, information about it will not be written to the `operations` table and, therefore, the `down` method will not be called when the rollback command is called.
 
 > Note
 >
-> When using the `before` parameter to run command, it is recommended to override the value of the `$before` attribute to `false`, otherwise this action will be executed twice.
+> When using the `before` parameter to run command, it is recommended to override the value of the `$before` attribute to `false`, otherwise this operation will be executed twice.
 
 ## Execution In A Specific Environment
 
-In some cases, it becomes necessary to execute an action in a specific environment. For example `production`.
+In some cases, it becomes necessary to execute an operation in a specific environment. For example `production`.
 
 For this you can use the `$environment` parameter:
 
@@ -162,11 +162,11 @@ return new class extends Operation
 };
 ```
 
-By default, the action will run in all environments. The same will happen if you specify `null` or `[]` as the value.
+By default, the operation will run in all environments. The same will happen if you specify `null` or `[]` as the value.
 
 ## Execution Excluding Certain Environments
 
-In some cases, it becomes necessary to execute an action excluding certain environments. For example `production`.
+In some cases, it becomes necessary to execute an operation excluding certain environments. For example `production`.
 
 For this you can use the `$except_environment` parameter:
 
@@ -200,15 +200,15 @@ return new class extends Operation
 };
 ```
 
-By default, no actions will be excluded. The same happens if you specify `null` or `[]` value.
+By default, no operations will be excluded. The same happens if you specify `null` or `[]` value.
 
 ## Database Transactions
 
-In some cases, it becomes necessary to undo previously performed actions in the database. For example, when code execution throws an error. To do this, the code must be wrapped in
+In some cases, it becomes necessary to undo previously performed operations in the database. For example, when code execution throws an error. To do this, the code must be wrapped in
 a transaction.
 
 By setting the `$transactions = true` parameter, you will ensure that your code is wrapped in a transaction without having to manually call the `DB::transaction()` method. This
-will reduce the time it takes to create the action.
+will reduce the time it takes to create the operation.
 
 ```php
 use DragonCode\LaravelDeployOperations\Operation;
@@ -228,9 +228,9 @@ return new class extends Operation
 
 ## Asynchronous Call
 
-In some cases, it becomes necessary to execute actions in an asynchronous manner without delaying the deployment process.
+In some cases, it becomes necessary to execute operations in an asynchronous manner without delaying the deployment process.
 
-To do this, you need to override the `$async` property in the action class:
+To do this, you need to override the `$async` property in the operation class:
 
 ```php
 use DragonCode\LaravelDeployOperations\Operation;
@@ -246,9 +246,9 @@ return new class extends Operation
 };
 ```
 
-In this case, the action file that defines this parameter will run asynchronously using the `DragonCode\LaravelDeployOperations\Jobs\ActionJob` class.
+In this case, the operation file that defines this parameter will run asynchronously using the `DragonCode\LaravelDeployOperations\Jobs\OperationJob` class.
 
-The name of the connection and queue can be changed through the [settings](https://github.com/TheDragonCode/laravel-actions/tree/main/config).
+The name of the connection and queue can be changed through the [settings](https://github.com/TheDragonCode/laravel-deploy-operations/tree/main/config).
 
 ::: Info
 We remind you that in this case the [queuing system](https://laravel.com/docs/queues) must work in your application.

docs/prologue/upgrade-guide/3.x.md

@@ -82,7 +82,7 @@ class Some extends Actionable {}
 // after
 use DragonCode\LaravelActions\Action;
 
-return new class () extends Action {};
+return new class extends Action {};
 ```
 
 ## Invokable Method

docs/prologue/upgrade-guide/4.x.md

@@ -1,6 +1,6 @@
 # Upgrading To 4.x from 3.x
 
-### High Impact Changes
+### High-Impact Changes
 
 - [Rename package name](#rename-package-name)
 - [Changing the names of console commands](#changing-the-names-of-console-commands)