Update documentation.

Author: RTippin

docs/ChatBots.md

@@ -73,7 +73,7 @@ class Kernel extends ConsoleKernel
 
 - If a [BotActionHandler][link-action-handler] throws an exception while being handled, it will be caught and dispatched in the [BotActionFailedEvent][link-action-failed-event].
 - Upon a [BotActionHandler][link-action-handler] being handled successfully, the [BotActionHandledEvent][link-action-handled-event] will be dispatched.
-  - You must attach your own event listeners to these events if you plan do utilize them.
+  - You must attach your own event listeners to these events if you plan to utilize them.
   - Please see the [Events Documentation][link-events-docs] for more information.
 
 ---
@@ -139,12 +139,12 @@ class TestBot extends BotActionHandler
 
 **`unique`, `match`, and `triggers` are optional overrides.**
 
-- `alias` Used to locate and attach your handler to a bot.
-- `description` The description of your bot handler, typically what it does.
-- `name` The name of your bot handler.
-- `unique (optional)` When set and true, the handler may only be used once across all bots in a thread.
-- `triggers (optional)` Overrides allowing the end user to set the triggers. Only the given trigger(s) will be used. Separate multiple via the pipe (|) or use an array.
-- `match (optional)` Overrides allowing end user to select matching method.
+- `alias [string]` Used to locate and attach your handler to a bot.
+- `description [string]` The description of your bot handler, typically what it does.
+- `name [string]` The name of your bot handler.
+- `unique (optional) [bool]` When set and true, the handler may only be used once across all bots in a thread.
+- `triggers (optional)  [array]` Overrides allowing the end user to set the triggers. Only the given trigger(s) will be used. Use a single array of all trigger words.
+- `match (optional) [string]` Overrides allowing end user to select matching method.
 
 ---
 
@@ -507,13 +507,13 @@ class TestBotPackage extends PackagedBot
 
 **`avatar`, `cooldown`, `enabled`, and `hide_actions` are optional overrides.**
 
-- `alias` Used to locate and install your packaged bot.
-- `description` The description of your packaged bot.
-- `name` The name of your packaged bot. The name will be used as the original `Bot` model's `name` when stored.
-- `avatar (optional)` Define the path to a local image file that will be used to display the package's avatar to the frontend, as well as stored for the `Bot` models initial `avatar`.
-- `cooldown` Cooldown the `Bot` model stored has after each action is triggered. Default of `0`.
-- `enabled` Whether the `Bot` model is enabled or disabled. Default of `true`.
-- `hide_actions` Whether the `Bot` model's actions are hidden or visible to others. Default of `false`.
+- `alias [string]` Used to locate and install your packaged bot.
+- `description [string]` The description of your packaged bot.
+- `name [string]` The name of your packaged bot. The name will be used as the original `Bot` model's `name` when stored.
+- `avatar (optional) [string]` Define the path to a local image file that will be used to display the package's avatar to the frontend, as well as stored for the `Bot` models initial `avatar`.
+- `cooldown (optional) [int]` Cooldown the `Bot` model stored has after each action is triggered. Default of `0`.
+- `enabled (optional) [bool]` Whether the `Bot` model is enabled or disabled. Default of `true`.
+- `hide_actions (optional) [bool]` Whether the `Bot` model's actions are hidden or visible to others. Default of `false`.
 
 **Example:**
 
@@ -541,13 +541,14 @@ public static function getSettings(): array
 - Return the listing of `BotActionHandler` classes you want to be bundled with this install. 
 - The array keys must be the `BotActionHandler` class. 
 - For handlers that require you to set properties, or that you want to override certain defaults, you must define them as the value of the handler class key represented as an associative array. 
-- If you want the handler to be installed multiple times with different parameters, you can define an array of arrays as the value. The key/values of your parameters must match the default for a BotAction model, as well as include any parameters that are defined on the handlers rules for serializing a payload.
-- `BotAction | BotActionHandler` handler keys include:
-  - `enabled` Default of `true`.
-  - `cooldown` Default of `30`.
-  - `admin_only` Default of `false`.
-  - `triggers` No default. You must define them if the `BotActionHandler` does not override them.
-  - `match` No default. You must define them if the `BotActionHandler` does not override them.
+- If you want the handler to be installed multiple times with different parameters, you can define an array of arrays as the value. 
+- The key/values of your parameters must match the default for a BotAction model, as well as include any parameters that are defined on the handlers rules for serializing a payload.
+- `BotAction | BotActionHandler` keys include:
+  - `enabled [bool]` Default of `true`.
+  - `cooldown [int]` Default of `30`.
+  - `admin_only [bool]` Default of `false`.
+  - `triggers (optional) [array]` No default. You must define them if the `BotActionHandler` does not override them.
+  - `match (optional) [string]` No default. You must define them if the `BotActionHandler` does not override them.
 - Any parameters that are already defined in the bot handler class cannot be overridden. While installing, each `BotActionHandler` will pass through a validation process, and will be discarded if it fails validating.
 
 ---

docs/Configuration.md

@@ -13,7 +13,7 @@
 #### SET THIS BEFORE MIGRATING
 
 - All tables in this package that have relations to one of your `MessengerProvider` models will use polymorphic `morphTo` columns. If your providers use UUIDs (char 36) as their primary keys, then set this to true. 
-- Please note that if you use multiple providers, they all must have matching primary key types (int / char / etc.).
+- Please note that if you use multiple providers, they all must have matching primary key types.
 - This also determines the primary key type on the internal `Bot` model and its related columns.
 
 ---

docs/Installation.md

@@ -9,8 +9,8 @@ composer require rtippin/messenger
 ```
 
 ### Install Command
-- Installs the base messenger files, publishing the [`messenger.php`][link-config] config and service provider.
-- This will also register the published service provider in your `app.php` config file inside the providers array.
+- Installs the base messenger files, publishing the [`messenger.php`][link-config] configuration file and `MessengerServiceProvider`.
+- This will also register the published service provider in your `app.php` configuration file inside the `providers` array.
 - You will be asked to confirm running this command, as well as an option to run the migrations before completion.
   - If your `Provider|User` models you are registering in `Messenger` use UUIDs instead of auto-incrementing integers as their primary keys, add the `--uuids` flag when installing.
 ```bash
@@ -36,8 +36,7 @@ php artisan migrate
 - Providers are the model's from your application you register into `Messenger`.
 - For most applications, you will only register your `User` model. 
   - If you had a `User` and a `Teacher` model, you can register both models with `Messenger`, allowing teachers to have their own inbox, and able to message users as a teacher.
-- The `Bot` model is a registered internally as a provider, allowing it to participate in group threads.
-- Your provider models will also use the internal [Messenger.php][link-messenger-model] model, which acts as a settings model, as well as allowing reverse search. More on this below, after registering providers.
+- Your provider models will also use the internal [Messenger.php][link-messenger-model] model, which acts as a settings model, as well as allowing reverse searching. More on this below, after registering providers.
 
 ---