chore: fix some comments

crates/core/messages.rs

@@ -28,7 +28,7 @@ static ERRORED: AtomicBool = AtomicBool::new(false);
 ///
 /// This locks stdout, not stderr, even though this prints to stderr. This
 /// avoids the appearance of interleaving output when stdout and stderr both
-/// correspond to a tty.)
+/// correspond to a tty.
 #[macro_export]
 macro_rules! eprintln_locked {
  ($($tt:tt)*) => {{

crates/regex/src/config.rs

@@ -233,7 +233,7 @@ impl ConfiguredHIR {
  &self.config
  }
 
- /// Return a reference to the underyling HIR.
+ /// Return a reference to the underlying HIR.
  pub(crate) fn hir(&self) -> &Hir {
  &self.hir
  }

crates/regex/src/literal.rs

@@ -15,7 +15,7 @@ use crate::{config::ConfiguredHIR, error::Error};
 /// that are in turn used to build a simpler regex that is more amenable to
 /// optimization.
 ///
-/// The main idea underyling the validity of this technique is the fact
+/// The main idea underlying the validity of this technique is the fact
 /// that ripgrep searches individuals lines and not across lines. (Unless
 /// -U/--multiline is enabled.) Namely, we can pluck literals out of the regex,
 /// search for them, find the bounds of the line in which that literal occurs