@@ -596,7 +596,7 @@ pub enum HitboxBehavior {
/// ```
///
/// This has effects beyond event handling - any use of hitbox checking, such as hover
- /// styles and tooltops. These other behaviors are the main point of this mechanism. An
+ /// styles and tooltips. These other behaviors are the main point of this mechanism. An
/// alternative might be to not affect mouse event handling - but this would allow
/// inconsistent UI where clicks and moves interact with elements that are not considered to
/// be hovered.
@@ -624,7 +624,7 @@ pub enum HitboxBehavior {
/// desired, then a `cx.stop_propagation()` handler like the one above can be used.
///
/// This has effects beyond event handling - this affects any use of `is_hovered`, such as
- /// hover styles and tooltops. These other behaviors are the main point of this mechanism.
+ /// hover styles and tooltips. These other behaviors are the main point of this mechanism.
/// An alternative might be to not affect mouse event handling - but this would allow
/// inconsistent UI where clicks and moves interact with elements that are not considered to
/// be hovered.
@@ -9733,7 +9733,7 @@ async fn test_ignored_dirs_events(cx: &mut gpui::TestAppContext) {
("project/target/debug/deps".to_string(), PathChange::Added),
("project/target/debug/deps".to_string(), PathChange::Removed),
],
- "Due to `debug` directory being tracket, it should get updates for entries inside it.
+ "Due to `debug` directory being tracked, it should get updates for entries inside it.
No updates for more nested directories should happen as those are ignored",
);
}
@@ -1,6 +1,6 @@
/// Trait for recursively merging settings structures.
///
-/// When Zed starts it loads settinsg from `default.json` to initialize
+/// When Zed starts it loads settings from `default.json` to initialize
/// everything. These may be further refined by loading the user's settings,
/// and any settings profiles; and then further refined by loading any
/// local project settings.