diff --git a/backend/windmill-worker/src/python_executor.rs b/backend/windmill-worker/src/python_executor.rs index d4acf709c2..80b577f5f3 100644 --- a/backend/windmill-worker/src/python_executor.rs +++ b/backend/windmill-worker/src/python_executor.rs @@ -1867,7 +1867,7 @@ pub async fn handle_python_reqs( if let Err(e) = pull { tracing::info!( workspace_id = %w_id, - "No tarball was found for {venv_p} on S3 or different problem occured {job_id}:\n{e}", + "No tarball was found for {venv_p} on S3 or different problem occurred {job_id}:\n{e}", ); } else { print_success( diff --git a/backend/windmill-worker/src/universal_pkg_installer.rs b/backend/windmill-worker/src/universal_pkg_installer.rs index 3f3198339a..d4e33b4a72 100644 --- a/backend/windmill-worker/src/universal_pkg_installer.rs +++ b/backend/windmill-worker/src/universal_pkg_installer.rs @@ -544,7 +544,7 @@ async fn try_install_one_detached<'a, T: Clone + std::marker::Send + Sync + 'a + if let Err(e) = s3_pull_future.await { tracing::info!( workspace_id = %w_id, - "No tarball was found for {:?} on S3 or different problem occured {job_id}:\n{e}", + "No tarball was found for {:?} on S3 or different problem occurred {job_id}:\n{e}", &dep._s3_handle.clone() ); } else { diff --git a/frontend/src/lib/components/InstanceSetting.svelte b/frontend/src/lib/components/InstanceSetting.svelte index 6a059dcf00..95fb21b614 100644 --- a/frontend/src/lib/components/InstanceSetting.svelte +++ b/frontend/src/lib/components/InstanceSetting.svelte @@ -746,7 +746,7 @@ The max amount of documents (here jobs) per commit. To optimize indexing throughput, it is best to keep this as high as possible. However, especially when reindexing the whole instance, it can be useful to have a limit on how many - jobs can be written without being commited. A commit will make the jobs + jobs can be written without being committed. A commit will make the jobs available for search, constitute a "checkpoint" state in the indexing and will be logged. @@ -805,7 +805,7 @@ representing all logs during 1 minute for a specific host. To optimize indexing throughput, it is best to keep this as high as possible. However, especially when reindexing the whole instance, it can be useful to have a limit on how many - logs can be written without being commited. A commit will make the logs + logs can be written without being committed. A commit will make the logs available for search, appear as a log line, and be a "checkpoint" of the indexing progress. diff --git a/frontend/src/lib/components/ScriptBuilder.svelte b/frontend/src/lib/components/ScriptBuilder.svelte index f81c45f8e9..2394ffcbe2 100644 --- a/frontend/src/lib/components/ScriptBuilder.svelte +++ b/frontend/src/lib/components/ScriptBuilder.svelte @@ -360,7 +360,7 @@ return templateScript } catch (error) { sendUserToast( - 'An error occured when trying to load your template script, please try again later', + 'An error occurred when trying to load your template script, please try again later', true ) } diff --git a/frontend/src/lib/components/apps/components/helpers/RunnableComponent.svelte b/frontend/src/lib/components/apps/components/helpers/RunnableComponent.svelte index 69653bc17a..c68edc20d4 100644 --- a/frontend/src/lib/components/apps/components/helpers/RunnableComponent.svelte +++ b/frontend/src/lib/components/apps/components/helpers/RunnableComponent.svelte @@ -614,7 +614,7 @@ return { error: { name: 'TransformerError', - message: 'An error occured in the transformer', + message: 'An error occurred in the transformer', stack: err.message } } @@ -894,7 +894,7 @@