Fix link in operation_order

Author: knopers8

docs/handbook/operation_order.md

@@ -1,7 +1,7 @@
 # Environment operation order
 
 This chapter attempts to document the order of important operations done during environment transitions.
-Since AliECS is an evolving system, the information presented here might be out-of-date, thus please refer to event handling in [environment.go][https://github.com/AliceO2Group/Control/blob/master/core/environment/environment.go) and plugin calls in [ControlWorkflows/workflows/readout-dataflow.yaml](https://github.com/AliceO2Group/ControlWorkflows/blob/master/workflows/readout-dataflow.yaml) for the ultimate source of truth.
+Since AliECS is an evolving system, the information presented here might be out-of-date, thus please refer to event handling in [environment.go](https://github.com/AliceO2Group/Control/blob/master/core/environment/environment.go) and plugin calls in [ControlWorkflows/workflows/readout-dataflow.yaml](https://github.com/AliceO2Group/ControlWorkflows/blob/master/workflows/readout-dataflow.yaml) for the ultimate source of truth.
 Also, please report to the ECS developers any inaccuracies.
 
 ## State machine triggers
@@ -99,4 +99,4 @@ This is the order of actions happening at a healthy end of run.
 - `"run_end_completion_time_ms"` is set using current time. It is considered as the EOEOR timestamp.
 - `after_STOP_ACTIVITY` hooks with positive weights (incl. 0) are executed:
   - `ccdb.RunStop()` at `0`
-  - `bookkeeping.UpdateRunStop()`, `bookkeeping.UpdateEnv()` at `+100`
+  - `bookkeeping.UpdateRunStop()`, `bookkeeping.UpdateEnv()` at `+100`