Clarify branding

Author: rmcdaniel

blog/2022-10-29-email-verifications.md

@@ -21,7 +21,7 @@ A typical registration process goes as follows:
 
 What’s wrong with this? Nothing. But like all things, as soon as real world complexity creeps in, this pattern could become painful. What if you wanted to send an email after the code or link expires? And do you really need a user in your database if they never verify their email address?
 
-Let’s take this trivial example and replace it with a workflow. This is based on the [Workflow](https://github.com/laravel-workflow/laravel-workflow) library.
+Let’s take this trivial example and replace it with a workflow. This is based on the [Workflow library](https://github.com/laravel-workflow/laravel-workflow) (the Laravel-native durable workflow package).
 
 Get Started
 ===========

blog/2022-12-22-new-laravel-workflow-feature-side-effects.md

@@ -15,7 +15,7 @@ Workflow is a powerful package for the Laravel web framework that provides tools
 
 One of the key features of any workflow engine is the ability to track the history of a workflow as it is executed which allows a workflow to be retried if it fails or encounters an error. However, this also means that your workflow code must be deterministic and any non-deterministic code has to be carefully managed.
 
-Recently, Workflow added support for [side effects](https://laravel-workflow.com/docs/features/side-effects), which are closures containing non-deterministic code that is only executed once and the result saved. Side effects are a useful way to introduce non-deterministic behavior into a workflow, such as generating a random number or UUID.
+Recently, the Workflow package added support for [side effects](https://laravel-workflow.com/docs/features/side-effects), which are closures containing non-deterministic code that is only executed once and the result saved. Side effects are a useful way to introduce non-deterministic behavior into a workflow, such as generating a random number or UUID.
 
 Here is an example workflow that demonstrates side effects.
 

blog/2023-04-05-introducing-child-workflows-in-laravel-workflow.md

@@ -11,12 +11,12 @@ tags: [child-workflows, nesting]
 
 import ThemedImage from '@site/src/components/ThemedImage';
 
-Workflow has introduced an exciting new feature called “Child Workflows.” This addition aims to enhance the organization and maintainability of complex processes by allowing developers to encapsulate sub-processes within a parent workflow. This article will discuss the benefits of using child workflows, their similarities with running a workflow as an activity, and their compatibility with retry and resume features.
+Workflow (the Laravel-native durable workflow package) has introduced an exciting new feature called “Child Workflows.” This addition aims to enhance the organization and maintainability of complex processes by allowing developers to encapsulate sub-processes within a parent workflow. This article will discuss the benefits of using child workflows, their similarities with running a workflow as an activity, and their compatibility with retry and resume features.
 
 What are Child Workflows?
 =========================
 
-In Workflow, child workflows are a way to manage complex processes by breaking them down into smaller, more manageable units. They enable developers to create hierarchical and modular structures for their workflows, making them more organized and easier to maintain. A child workflow is essentially a separate workflow that is invoked within a parent workflow using the `child()` helper function.
+In the Workflow package, child workflows are a way to manage complex processes by breaking them down into smaller, more manageable units. They enable developers to create hierarchical and modular structures for their workflows, making them more organized and easier to maintain. A child workflow is essentially a separate workflow that is invoked within a parent workflow using the `child()` helper function.
 
 Benefits of Using Child Workflows
 =================================

blog/2023-04-25-combining-laravel-workflow-and-state-machines.md

@@ -9,12 +9,12 @@ authors:
 tags: [side-effects, random, determinism]
 ---
 
-When it comes to building web applications, managing complex processes and activities can be a daunting task. Workflow simplifies this process by providing tools for defining and managing workflows and activities. In addition, integrating a state machine library can offer more explicit control over the transitions between states or activities, resulting in a more structured and visual representation of the workflow. In this blog post, we will explore the benefits of using Workflow along with a state machine and walk through an example of integrating Workflow with Finite, a simple state machine library.
+When it comes to building web applications, managing complex processes and activities can be a daunting task. Workflow (the Laravel-native durable workflow package) simplifies this process by providing tools for defining and managing workflows and activities. In addition, integrating a state machine library can offer more explicit control over the transitions between states or activities, resulting in a more structured and visual representation of the workflow. In this blog post, we will explore the benefits of using Workflow along with a state machine and walk through an example of integrating Workflow with Finite, a simple state machine library.
 
 Benefits of Combining Workflow and State Machines
 =========================================================
 
-Using Workflow and a state machine together provides several advantages:
+Using the Workflow package and a state machine together provides several advantages:
 
 1.  Flexibility and modularity: Workflow allows developers to break down complex processes into smaller, modular units that are easy to maintain and update.
 2.  Explicit control over transitions: State machines provide a clear visualization of workflow states, activities, and transitions, making it easier to understand and maintain.

blog/2023-05-21-saga-pattern-and-laravel-workflow.md

@@ -37,7 +37,7 @@ Sagas are an established design pattern for managing complex, long-running opera
 3.  Each operation in the Saga can be reversed by a compensatory transaction.
 4.  The Saga pattern assures that all operations are either completed successfully or the corresponding compensation transactions are run to reverse any completed work.
 
-Workflow provides inherent support for the Saga pattern, simplifying the process of handling rollbacks and executing compensatory transactions.
+Workflow (the Laravel-native durable workflow package) provides inherent support for the Saga pattern, simplifying the process of handling rollbacks and executing compensatory transactions.
 
 Booking Saga Flow
 =================

docs/configuration/_category_.json

@@ -3,6 +3,6 @@
   "position": 5,
   "link": {
     "type": "generated-index",
-    "description": "Workflow allows you to specify various options when defining your workflows and activities."
+    "description": "The Workflow package allows you to specify various options when defining your workflows and activities."
   }
 }

docs/configuration/options.md

@@ -4,7 +4,7 @@ sidebar_position: 2
 
 # Options
 
-Workflow allows you to specify various options when defining your workflows and activities. These options include the number of times a workflow or activity may be attempted before it fails, the connection and queue, and the maximum number of seconds it is allowed to run.
+The Workflow package allows you to specify various options when defining your workflows and activities. These options include the number of times a workflow or activity may be attempted before it fails, the connection and queue, and the maximum number of seconds it is allowed to run.
 
 ```php
 use Workflow\Activity;

docs/constraints/_category_.json

@@ -3,6 +3,6 @@
   "position": 7,
   "link": {
     "type": "generated-index",
-    "description": "Workflow's determinism and idempotency constraints for workflows and activities are important for ensuring the reliability and correctness of the overall system."
+    "description": "The Workflow package's determinism and idempotency constraints for workflows and activities are important for ensuring the reliability and correctness of the overall system."
   }
 }

docs/features/_category_.json

@@ -3,6 +3,6 @@
   "position": 4,
   "link": {
     "type": "generated-index",
-    "description": "Workflow provides methods for executing activities, handling errors and retries, and communicating with the workflow."
+    "description": "The Workflow package provides methods for executing activities, handling errors and retries, and communicating with the workflow."
   }
 }

docs/installation.md

@@ -24,15 +24,15 @@ Workflow also requires a cache driver that supports [locks](https://laravel.com/
 
 > ✨ SQS Support: `timer()` and `awaitWithTimeout()` work with any duration, even when using the SQS queue driver. Workflow automatically handles SQS's delay limitation transparently.
 
-## Installing Workflow
+## Installing the Workflow package
 
-Workflow is installable via Composer. To install it, run the following command in your Laravel project:
+The Workflow package is installable via Composer. To install it, run the following command in your Laravel project:
 
 ```bash
 composer require laravel-workflow/laravel-workflow
 ```
 
-After installing Workflow, you must also publish the migrations. To publish the migrations, run the following command:
+After installing the Workflow package, you must also publish the migrations. To publish the migrations, run the following command:
 
 ```bash
 php artisan vendor:publish --provider="Workflow\Providers\WorkflowServiceProvider" --tag="migrations"
@@ -46,4 +46,4 @@ php artisan migrate
 
 ## Running Workers
 
-Workflow uses queues to run workflows and activities in the background. You will need to either run the `queue:work` [command](https://laravel.com/docs/12.x/queues#the-queue-work-command) or use [Horizon](https://laravel.com/docs/12.x/horizon) to run your queue workers. Without a queue worker, workflows and activities will not be processed. You cannot use the sync driver with queue workers.
+The Workflow package uses queues to run workflows and activities in the background. You will need to either run the `queue:work` [command](https://laravel.com/docs/12.x/queues#the-queue-work-command) or use [Horizon](https://laravel.com/docs/12.x/horizon) to run your queue workers. Without a queue worker, workflows and activities will not be processed. You cannot use the sync driver with queue workers.