chore: fix CI checks

vegaprotocol · Oct 7, 2024 · 5f24398 · 5f24398
1 parent 6bd4d78
commit 5f24398
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/protocol/0098_OCRM-off_chain_rewards.md → protocol/0098-OCRM-off_chain_rewards.md b/protocol/0098_OCRM-off_chain_rewards.md → protocol/0098-OCRM-off_chain_rewards.md
@@ -75,8 +75,8 @@ Following section includes a number of considerations for the implementation wit
 
 ## Consensus
 
-- Given the network is currently ready to receive data for a reward paying out at the end of epoch `1`. If in epoch `2` the network has received less than `consensusThreshold` matching metric transactions, then no rewards will be distributed at the end of epoch `2`. 
-- Given the network is currently ready to receive data for a reward paying out at the end of epoch `1`. If in epoch `2` the network has received greater than or equal to `consensusThreshold` matching metric transactions, then rewards will be distributed at the end of epoch `2`. 
+- Given the network is currently ready to receive data for a reward paying out at the end of epoch `1`. If in epoch `2` the network has received less than `consensusThreshold` matching metric transactions, then no rewards will be distributed at the end of epoch `2`.
+- Given the network is currently ready to receive data for a reward paying out at the end of epoch `1`. If in epoch `2` the network has received greater than or equal to `consensusThreshold` matching metric transactions, then rewards will be distributed at the end of epoch `2`.
 
 ## Distribution
 
@@ -92,4 +92,4 @@ Following section includes a number of considerations for the implementation wit
 - Given the network is currently awaiting consensus on metrics for a reward for epochs `1` and `2`. If the network achieves consensus on the metrics for epoch `2` and then `1`, rewards will be distributed first for epoch `1` and then `2` at the next epoch boundary.
 
 - Given the network is currently awaiting consensus on metrics for two different rewards funded from the same account (`A` and `B`), `A` waiting for metrics from epoch `1` and `B` awaiting metrics from epoch `2`. If the network achieves consensus on the metrics for reward `B` then they will be distributed at the next epoch boundary.
-- Given the network is currently awaiting consensus on metrics for two different rewards funded from the same account (`A` and `B`), `A` waiting for metrics from epoch `1` and `B` awaiting metrics from epoch `2`. If the network achieves consensus on the metrics for reward `B` and then reward `A`, rewards will be distributed first for reward `B` (epoch `2`) and then reward `A` (epoch `1`) at the next epoch boundary.
+- Given the network is currently awaiting consensus on metrics for two different rewards funded from the same account (`A` and `B`), `A` waiting for metrics from epoch `1` and `B` awaiting metrics from epoch `2`. If the network achieves consensus on the metrics for reward `B` and then reward `A`, rewards will be distributed first for reward `B` (epoch `2`) and then reward `A` (epoch `1`) at the next epoch boundary.