Fix more typos in comments and docs

app/assets/bundled/bootstrap/pwsh.ps1

@@ -243,7 +243,7 @@ $null = New-Module -Name Warp-Module -ScriptBlock {
         }
 
         # Clean up any completed warp jobs so they do not show up on the user's 'get-job'
-        # comands
+        # commands
         Warp-Clean-CompletedThread
 
         # Remove any instance of the 'Warp-Run-GeneratorCommand' call from the user's history

app/src/ai/blocklist/input_model.rs

@@ -40,7 +40,7 @@ use crate::{
 
 use super::telemetry_banner::should_collect_ai_ugc_telemetry;
 
-/// Cutoff score for deciding an user input matches a history command entry.
+/// Cutoff score for deciding a user input matches a history command entry.
 const HISTORY_ENTRY_MATCH_CUTOFF: f32 = 0.9;
 
 /// Duration to temporarily disable autodetection during operations like history selection.

app/src/code_review/mod.rs

@@ -142,10 +142,10 @@ fn is_file_autogenerated(file_path: &Path, content: Option<&str>) -> bool {
     false
 }
 
-/// A [`SingletonEntity`] that the tracks events for the code review model throughought the app.
+/// A [`SingletonEntity`] that the tracks events for the code review model throughout the app.
 /// We need this because toasts are emitted in the Workspace, and want a click handler that triggers
 /// behavior in a _specific_ review pane. We use this model get around restrictions that make it hard
-/// to emit a CodeReviewView typed action from the toast because it's not in the view reponder chain of the
+/// to emit a CodeReviewView typed action from the toast because it's not in the view responder chain of the
 /// Workspace.
 pub struct GlobalCodeReviewModel;
 

app/src/drive/import/nodes.rs

@@ -755,7 +755,7 @@ impl FileUploadState {
                     folder.server_id = Some(server_id.clone());
 
                     // If a folder has no children or all of its children complete syncing,
-                    // we need to bubble the state up in the folder hierachy tree.
+                    // we need to bubble the state up in the folder hierarchy tree.
                     if folder.children().is_empty() || folder.all_children_synced {
                         folder.status = UploadStatus::Loaded(server_id);
                         true

app/src/drive/items/item.rs

@@ -134,7 +134,7 @@ pub struct WarpDriveRow<'a> {
     space: Space,
     item_states: ItemStates,
     overflow_button: Box<dyn Element>,
-    /// how many levels into a folder hierachy the row is.
+    /// how many levels into a folder hierarchy the row is.
     /// 0 means the object is in the root directory.
     folder_depth: usize,
     sync_icon: Option<Box<dyn Element>>,

app/src/external_secrets/mod.rs

@@ -17,7 +17,7 @@ use crate::terminal::local_shell::execute_command;
 use crate::{terminal::shell::ShellType, ui_components::icons::Icon};
 
 lazy_static! {
-    // Used as a delimeter to separate metadata (such as names and references)
+    // Used as a delimiter to separate metadata (such as names and references)
     // in cases the cli tool doesn't display secrets in a common format (i.e. json)
     static ref WARP_SECRET_DELIMETER: &'static str = "/warp-secret-delimeter/";
     static ref LASTPASS_LIST_SECRETS_COMMAND: Vec<String> = {

app/src/resource_center/main_page.rs

@@ -459,9 +459,9 @@ impl ResourceCenterMainView {
 /// we should send the actions from the resouce center features. When the resource center is opened,
 /// we cache the current active window ID as well as the input ID of the active
 /// tab/pane. By sending all the actions to the input view, we ensure that
-/// they propgate correctly. This propogation assumes that each feature action
-/// must be in the reponder chain. If an action is not in the responder chain
-/// (such as a block navigation action) then it won't propogate correctly.
+/// they propagate correctly. This propagation assumes that each feature action
+/// must be in the responder chain. If an action is not in the responder chain
+/// (such as a block navigation action) then it won't propagate correctly.
 pub enum ActionTarget {
     None,
     View {

app/src/server/sync_queue.rs

@@ -620,7 +620,7 @@ impl SyncQueue {
                         workflow_id.uid(),
                         *item_id,
                         // When adding the initiated_by parameter to this function call, InitiatedBy::User was set as a default value.
-                        // It can be changed to propogate initiated_by value from the queue object in the future if desired.
+                        // It can be changed to propagate initiated_by value from the queue object in the future if desired.
                         InitiatedBy::User,
                         ctx,
                     );

app/src/terminal/model/block.rs

@@ -335,7 +335,7 @@ pub struct Block {
     /// determine if commands in a restored session should be included in
     /// History::session_commands. This is optional b/c just like session_id, pwd, git_branch, etc.
     /// which are determined at precmd time, it is unset at block creation. It is also to
-    /// accomodate the case where determining the ShellHost fails during session restoration, e.g.
+    /// accommodate the case where determining the ShellHost fails during session restoration, e.g.
     /// if the values in sqlite are NULL or invalid.
     shell_host: Option<ShellHost>,
 

app/src/terminal/model/session/command_executor/local_command_executor.rs

@@ -173,7 +173,7 @@ impl LocalCommandExecutor {
 
         let mut command_process = command_builder.build(command, shell_config_flag);
 
-        // This sets then enviornment variables, including the PATH var.
+        // This sets the environment variables, including the PATH var.
         // We need to run the command with the PATH var set because if the
         // user opened Warp through a parent process that didn't have the PATH var set
         // (i.e. outside of a shell, for example opening the app via Finder),

app/src/terminal/view.rs

@@ -1660,7 +1660,7 @@ pub enum Event {
     Pane(PaneEvent),
     OpenSettings(SettingsSection),
     AskAIAssistant(AskAIType),
-    /// Event propogates terminal inputs up to the workspace,
+    /// Event propagates terminal inputs up to the workspace,
     /// to be processed on the way back down through the view hierarchy.
     SyncInput(SyncEvent),
     /// Event used to propagate a state change for one of the terminal views
@@ -1996,7 +1996,7 @@ pub struct SyncEvent {
     pub data: SyncInputType,
 }
 
-/// Event used to propogate the keyboard events from one terminal to others.
+/// Event used to propagate the keyboard events from one terminal to others.
 #[derive(Clone)]
 pub enum SyncInputType {
     /// Event for when the input editor's buffer contents changed.
@@ -3887,7 +3887,7 @@ impl TerminalView {
             });
         }
 
-        // Here we intialize the block list mouse states for block zero.
+        // Here we initialize the block list mouse states for block zero.
         // Afterwards, we initialize all block list mouse states for a block when the
         // previous block sends a `BlockCompleted` event.
         let mut block_list_mouse_states = BlockListMouseStates::default();

app/src/tips/tip_view.rs

@@ -527,9 +527,9 @@ impl TipsView {
 /// we should send the actions from the welcome tips. When the tip view is opened,
 /// we cache the current active window ID as well as the input ID of the active
 /// tab/pane. By sending all the actions to the input view, we ensure that
-/// they propgate correctly. This propogation assumes that each welcome tip action
-/// must be in the reponder chain. If an action is not in the responder chain
-/// (such as a block navigation action) then it won't propogate correctly.
+/// they propagate correctly. This propagation assumes that each welcome tip action
+/// must be in the responder chain. If an action is not in the responder chain
+/// (such as a block navigation action) then it won't propagate correctly.
 enum ActionTarget {
     None,
     View {

app/src/uri/mod.rs

@@ -256,7 +256,7 @@ impl UriHost {
                 // For folder links, we expect an additional query parameter primary_object_id which refers to the id object
                 // that should be opened
                 // When the user is directed here via the request access flow, we expect an additional query parameter invitee_email
-                // If this paramter is present, we will open the sharing dialog with the email filled in.
+                // If this parameter is present, we will open the sharing dialog with the email filled in.
                 let object_type = url
                     .path_segments()
                     .into_iter()

crates/ai/src/skills/skill_reference.rs

@@ -1,7 +1,7 @@
 use serde::{Deserialize, Serialize};
 use std::{fmt, path::PathBuf};
 
-/// An unique reference to a skill.
+/// A unique reference to a skill.
 #[derive(Debug, Clone, PartialEq, Eq, Hash, Deserialize, Serialize)]
 pub enum SkillReference {
     /// A skill identified by the path to its SKILL.md file.

crates/integration/tests/common/mod.rs

@@ -36,7 +36,7 @@ pub fn run_integration_test(name: &str) -> Result<(), String> {
                 // as they tend to encode the home directory, which we override
                 // in tests to point to a per-test temporary directory.
                 || k == "XDG_RUNTIME_DIR"
-                // Propogate XAUTHORITY so we can run headless tests using xvfb.
+                // Propagate XAUTHORITY so we can run headless tests using xvfb.
                 || k == "XAUTHORITY"
         });
         keep_going = match Command::new(env!("CARGO_BIN_EXE_integration"))

crates/lsp/README.md

@@ -6,4 +6,4 @@ This crate provides a stdio-only Language Server Protocol (LSP) client transport
 - Communicates over stdio using JSON-RPC with proper Content-Length framing
 
 
-See main.rs for an example implmentation
+See main.rs for an example implementation

crates/warpui_core/README.md

@@ -41,9 +41,9 @@ Entities are of course entitled to own any state they like directly as well. Han
 
 The framework requires all views to implement the `View` trait, and a key method of this trait is `render`, which we showcased above. This method's job is to compute a visual description of the view based on its current state, and it is called whenever the view's state changes.
 
-To do describe the view's appearence, render returns an **element**. While a single view may exist for an arbitrary amount of time, changing its state as the user interacts with the application, an element is designed to exist for only a single frame. More precicely, elements returned by views that haven't changed are recycled across multiple frames, but conceptually you can think of an element as a throwaway object that is discarded and replaced whenever the view that returned it changes.
+To do describe the view's appearance, render returns an **element**. While a single view may exist for an arbitrary amount of time, changing its state as the user interacts with the application, an element is designed to exist for only a single frame. More precisely, elements returned by views that haven't changed are recycled across multiple frames, but conceptually you can think of an element as a throwaway object that is discarded and replaced whenever the view that returned it changes.
 
-The framework ships with several elements that can be composed to perform common tasks such as drawing backgrounds and borders, adding padding, rendering label text, laying out elements horizontally and vertically, handlign events, etc. The stock elements are loosely based on the Flutter framework. It's also straightforward to define your own custom elements, giving you detailed control over layout and the ability to imperatively paint pixels on scene via the hardware-accelerated `Scene` API.
+The framework ships with several elements that can be composed to perform common tasks such as drawing backgrounds and borders, adding padding, rendering label text, laying out elements horizontally and vertically, handling events, etc. The stock elements are loosely based on the Flutter framework. It's also straightforward to define your own custom elements, giving you detailed control over layout and the ability to imperatively paint pixels on scene via the hardware-accelerated `Scene` API.
 
 ## Actions
 

crates/warpui_core/src/elements/stack/mod_test.rs

@@ -668,7 +668,7 @@ fn test_relative_positioning_bound_to_window_by_position() {
             .scene()
             .expect("Presenter should have rendered a scene after the view was updated.");
 
-        // The expected bounds should have a modified position to accomodate the size of the
+        // The expected bounds should have a modified position to accommodate the size of the
         // positioned child (it should be moved back to (0,0) from it's 'default' (75, 75).
         //
         // Note the usage of `RectF::from_points`, which specifies top-left