Fix a number of spelling mistakes (#38281)

My pre push hooks keep failing on these. This is easier then disabling
and re-enabling those hooks all the time :)

Closes #ISSUE

Release Notes:

- N/A
This commit is contained in:
David Kleingeld
2025-09-16 19:18:39 +00:00
committed by GitHub
parent 5674445a61
commit 673a98a277
4 changed files with 5 additions and 5 deletions
@@ -160,7 +160,7 @@ mod tests {
&mut parser,
&mut rng
),
// This output is marlformed, so we're doing our best effort
// This output is malformed, so we're doing our best effort
"Hello world\n```\n\nThe end\n".to_string()
);
}
@@ -182,7 +182,7 @@ mod tests {
&mut parser,
&mut rng
),
// This output is marlformed, so we're doing our best effort
// This output is malformed, so we're doing our best effort
"```\nHello world\n```\n".to_string()
);
}
@@ -916,7 +916,7 @@ impl Loader {
if !found_non_static {
found_non_static = true;
eprintln!(
"Warning: Found non-static non-tree-sitter functions in the external scannner"
"Warning: Found non-static non-tree-sitter functions in the external scanner"
);
}
eprintln!(" `{function_name}`");
+1 -1
View File
@@ -9694,7 +9694,7 @@ impl EditorScrollbars {
editor_bounds.bottom_left(),
size(
// The horizontal viewport size differs from the space available for the
// horizontal scrollbar, so we have to manually stich it together here.
// horizontal scrollbar, so we have to manually stitch it together here.
editor_bounds.size.width - right_margin,
scrollbar_width,
),
+1 -1
View File
@@ -68,7 +68,7 @@ With both approaches, would need to record the buffer version and use that when
* Mode to navigate to source code on every element change while picking.
* Tracking of more source locations - currently the source location is often in a ui compoenent. Ideally this would have a way for the components to indicate that they are probably not the source location the user is looking for.
* Tracking of more source locations - currently the source location is often in a ui component. Ideally this would have a way for the components to indicate that they are probably not the source location the user is looking for.
- Could have `InspectorElementId` be `Vec<(ElementId, Option<Location>)>`, but if there are multiple code paths that construct the same element this would cause them to be considered different.