review fixes

Author: sokra

turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs

@@ -1401,7 +1401,7 @@ impl AggregationUpdateQueue {
                             task: lost_follower_id,
                         });
                     }
-                    // notify uppers about new follower
+                    // notify uppers about lost follower
                     if !upper_ids.is_empty() {
                         self.push(AggregationUpdateJob::InnerOfUppersLostFollower {
                             upper_ids,
@@ -1554,7 +1554,7 @@ impl AggregationUpdateQueue {
                             task: lost_follower_id,
                         });
                     }
-                    // notify uppers about new follower
+                    // notify uppers about lost follower
                     if !upper_ids.is_empty() {
                         self.push(AggregationUpdateJob::InnerOfUppersLostFollower {
                             upper_ids,
@@ -2445,7 +2445,7 @@ const MAX_YIELD_DURATION: Duration = Duration::from_millis(1);
 const MAX_RETRIES: u16 = 10000;
 
 /// Retry the passed function for a few milliseconds, while yielding to other threads.
-/// Returns an error if the function was not ablue to complete and the timeout was reached.
+/// Returns an error if the function was not able to complete and the timeout was reached.
 ///
 /// Each graph modification will only lock one or two tasks at a time, but updates usually also
 /// require follow-up updates to connected tasks. So an update will "slowly" propagate through the
@@ -2456,7 +2456,7 @@ const MAX_RETRIES: u16 = 10000;
 /// update yet). So we will retry (with this method) removals until the thing is there. So this is
 /// basically a busy loop that waits for the "add" update to complete. If the busy loop is not
 /// sucessful, the update is added to the end of the queue again. This is important as the "add"
-/// update might even be in the curreent thread and in the same queue. If that's the case yielding
+/// update might even be in the current thread and in the same queue. If that's the case yielding
 /// won't help and the update need to be requeued.
 fn retry_loop(mut f: impl FnMut() -> ControlFlow<()>) -> Result<(), RetryTimeout> {
     let mut time: Option<Instant> = None;