fix!: remove process manager

Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>

Author: yordis

guides/explanations/process-managers.md

@@ -115,7 +115,7 @@ defmodule Commanded.Application do
   own separately configured and isolated event store. Each application must be
   started with a unique name.
 
-  Multiple instances of the same event handler or process manager can be
+  Multiple instances of the same event handler can be
   started by referring to a started application by its name. The event store
   operations can also be scoped to an application by referring to its name.
 
@@ -320,9 +320,9 @@ defmodule Commanded.Application do
           - `:eventual` (default) - a successful command dispatch will return immediately.
 
           - `:strong` - a successful command dispatch will block until all strongly
-            consistent event handlers and process managers have handled all events created by the command.
+            consistent event handlers have handled all events created by the command.
 
-          - An explicit list of event handler and process manager modules (or their configured names),
+          - An explicit list of event handler modules (or their configured names),
             containing only those handlers you'd like to wait for. No other handlers will be awaited on,
             regardless of their own configured consistency setting.
             e.g. `[ExampleHandler, AnotherHandler]` or `["ExampleHandler", "AnotherHandler"]`

lib/application.ex

@@ -8,7 +8,6 @@ defmodule Commanded do
   - [Command registration and dispatch](commands.html).
   - [Hosting and delegation to aggregates](aggregates.html).
   - [Event handling](events.html).
-  - [Long running process managers](process-managers.html).
 
   Use Commanded with one of the following event stores for persistence:
 

lib/commanded.ex

@@ -113,15 +113,15 @@ defmodule Commanded.Commands.Router do
           :ok = BankApp.dispatch(command, consistency: :eventual)
 
     - `:strong` - block command dispatch until all strongly
-      consistent event handlers and process managers have successfully processed
+      consistent event handlers have successfully processed
       all events created by the command.
 
       Use this when you have event handlers that update read models you need to
       query immediately after dispatching the command.
 
           :ok = BankApp.dispatch(command, consistency: :strong)
 
-    - Provide an explicit list of event handler and process manager modules (or
+    - Provide an explicit list of event handler modules (or
       their configured names), containing only those handlers you'd like to wait
       for. No other handlers will be awaited on, regardless of their own
       configured consistency setting.

lib/commanded/commands/router.ex

@@ -131,7 +131,7 @@ defmodule Commanded.Event.Handler do
   ## Event handler name
 
   The name you specify is used when subscribing to the event store. You must use
-  a unique name for each event handler and process manager you start. Also, you
+  a unique name for each event handler you start. Also, you
   *should not* change the name once the handler has been deployed. A new
   subscription will be created if you change the name and the event handler will
   receive already handled events.

lib/commanded/event/handler.ex

@@ -9,7 +9,7 @@ defprotocol Commanded.Event.Upcaster do
   Upcaster will run for new events and for historical events.
 
   Because the upcaster changes any historical event to the latest version,
-  consumers (aggregates, event handlers, and process managers) only need
+  consumers (aggregates and event handlers) only need
   to support the latest version.
 
   ## Example