typos desktop

desktop/scripts/vips.js

@@ -24,7 +24,7 @@
  *
  * Note that `vips.js` would've already run once `beforeBuild.js` is run, but on
  * our CI we prepare builds for multiple architectures in one go, so we need to
- * unconditonally replace the binary with the relevant one for the current
+ * unconditionally replace the binary with the relevant one for the current
  * architecture being built (which might be different from the one we're running
  * on). `beforeBuild.js` runs for each architecture being built.
  *

desktop/src/main.ts

@@ -607,7 +607,7 @@ const handleBackOnStripeCheckout = (window: BrowserWindow) =>
  *
  * But this is an issue for uploads in the self hosted apps (or when we
  * ourselves are trying to test things by with an arbitrary S3 bucket without
- * going via a worker). During upload, theer is no redirection, so the request
+ * going via a worker). During upload, there is no redirection, so the request
  * ACAO is "ente://app" but the response ACAO is `null` which don't match,
  * causing the request to fail.
  *

desktop/src/main/types/any-shell-escape.d.ts

@@ -12,7 +12,7 @@
  *
  * yields (on POSIX shells):
  *
- *     curl -v -H 'Location;' -H 'User-Agent: FoorBar'"'"'s so-called "Browser"' 'http://www.daveeddy.com/?name=dave&age=24'
+ *     curl -v -H 'Location;' -H 'User-Agent: FooBar'"'"'s so-called "Browser"' 'http://www.daveeddy.com/?name=dave&age=24'
  *
  * or (on Windows):
  *

desktop/src/main/utils/temp.ts

@@ -64,7 +64,7 @@ export const deleteTempFile = async (tempFilePath: string) => {
 };
 
 /**
- * A variant of {@link deleteTempFile} that supresses any errors, making it
+ * A variant of {@link deleteTempFile} that suppresses any errors, making it
  * safe to call them in a sequence without needing to handle the scenario where
  * one of them failing causes the rest to be skipped.
  */

desktop/src/preload.ts

@@ -335,7 +335,7 @@ const clearPendingUploads = () => ipcRenderer.invoke("clearPendingUploads");
  * >
  * > https://www.electronjs.org/docs/latest/api/context-bridge#methods
  *
- * The copy itself is relatively fast, but the problem with transfering large
+ * The copy itself is relatively fast, but the problem with transferring large
  * amounts of data is potentially running out of memory during the copy.
  *
  * For an alternative, see [Note: IPC streams].