From bd63fcad16bbae28a635f08eb266e64770658475 Mon Sep 17 00:00:00 2001
From: Copper <157772455+FateUnix29@users.noreply.github.com>
Date: Sun, 9 Jun 2024 15:10:59 -0700
Subject: [PATCH] Another two-letter addition

---
 docs/Redpiler.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Redpiler.md b/docs/Redpiler.md
index 85167f8d..4d799f7f 100644
--- a/docs/Redpiler.md
+++ b/docs/Redpiler.md
@@ -83,7 +83,7 @@ Different node types operates differently:
 
 ### Repeater
 
-When a Repeater is updated, the first thing that is check is if the Repeater should be locked. If that value is different from the current state, the locking state of the Repeater is changed. Since this state change happens during the update, Repeater locking is instant. Then, if the Repeater is not locked and there is not already a tick pending at its node, then whether or not it should be powered is calculated. If this value is different from the current state, a tick is scheduled with the delay of the specific Repeater. The priority of the tick depends on if the output of the Repeater is directly facing another Repeater or Comparator. If it is, the priority is `Highest`. If not, but the Repeater is depowering, the priority is `Higher`. Otherwise, when the repeater should be powered and is not facing a Repeater or Comparator, the priority is `High`.
+When a Repeater is updated, the first thing that is checked is if the Repeater should be locked. If that value is different from the current state, the locking state of the Repeater is changed. Since this state change happens during the update, Repeater locking is instant. Then, if the Repeater is not locked and there is not already a tick pending at its node, then whether or not it should be powered is calculated. If this value is different from the current state, a tick is scheduled with the delay of the specific Repeater. The priority of the tick depends on if the output of the Repeater is directly facing another Repeater or Comparator. If it is, the priority is `Highest`. If not, but the Repeater is depowering, the priority is `Higher`. Otherwise, when the repeater should be powered and is not facing a Repeater or Comparator, the priority is `High`.
 
 When a Repeater is ticked, the first thing that is checked is if the Repeater is locked. If not, then the Repeater checked if it should be powered. If the Repeater is not powered, its state is set to powered. If the Repeater is powered but should not be powered, its state is set to unpowered. Note that a Repeater will become powered here regardless of the input it is receiving, but the same is not true for depowering. If its state is changed, all nodes that may be affected by this change are updated. If the Repeater was just set to powered even though it is not receiving a non-zero input, a tick is scheduled with `Higher` priority with the delay of the Repeater. This is the only node type where a tick is scheduled in the tick function itself.