Yes. The Hooks module was renamed Orchestration, and a hook became a job. The two words mean the same thing everywhere, so anything written about hooks applies to jobs unchanged.
| Old name | New name |
|---|---|
| Hooks, the module | Orchestration |
| hook | job |
| hook batch | job run, or job batch; listed under Batch Logs |
| hook category | job category |
| Trigger hook, the action | Trigger job |
| synchronous hook | synchronous job |
Some names did not change. The admin still calls a run a batch (Batch Logs, Batch persistence), and the API and the code still say hook; why the API still says hooks explains where.