Update pre-commit dependencies (astral-sh#17840)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Micha Reiser <micha@reiser.io>

Author: renovate[bot]

.pre-commit-config.yaml

@@ -65,7 +65,7 @@ repos:
           - black==25.1.0
 
   - repo: https://github.com/crate-ci/typos
-    rev: v1.31.1
+    rev: v1.32.0
     hooks:
       - id: typos
 
@@ -79,7 +79,7 @@ repos:
         pass_filenames: false # This makes it a lot faster
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.11.7
+    rev: v0.11.8
     hooks:
       - id: ruff-format
       - id: ruff

crates/ty_python_semantic/src/semantic_index/builder.rs

@@ -226,8 +226,8 @@ impl<'db> SemanticIndexBuilder<'db> {
 
     fn push_scope(&mut self, node: NodeWithScopeRef) {
         let parent = self.current_scope();
-        let reachabililty = self.current_use_def_map().reachability;
-        self.push_scope_with_parent(node, Some(parent), reachabililty);
+        let reachability = self.current_use_def_map().reachability;
+        self.push_scope_with_parent(node, Some(parent), reachability);
     }
 
     fn push_scope_with_parent(

crates/ty_python_semantic/src/semantic_index/use_def.rs

@@ -644,7 +644,7 @@ pub(super) struct UseDefMapBuilder<'db> {
 
     /// Tracks whether or not the scope start is visible at the current point in control flow.
     /// This is subtly different from `scope_start_visibility`, as we apply these constraints
-    /// at the beginnging of a branch. Visibility constraints, on the other hand, need to be
+    /// at the beginning of a branch. Visibility constraints, on the other hand, need to be
     /// applied at the end of a branch, as we apply them retroactively to all live bindings:
     /// ```py
     /// y = 1