Fix misspellings

Closes: #2807
Approved by: matthiasclasen

NEWS

@@ -329,7 +329,7 @@ Changes in 1.0.1
 ================
 
 This fixes various build and test failures that were detected when
-packaging 1.0, as well as translations and doc udpates. It also
+packaging 1.0, as well as translations and doc updates. It also
 has some minor features, including a new subcommand "flatpak ps"
 to list the running flatpak instances for your user.
 
@@ -554,7 +554,7 @@ Major changes in 0.11.8
  install/update operation.
  * We now respect multiple extension versions matches when auto-downloading extensions.
  * New http header Flatpak-Upgrade-From sent when upgrading.
- * Commands like "flatpak info/list/remotes/seach" now work properly if /var/lib/flatpak doesn't exist.
+ * Commands like "flatpak info/list/remotes/search" now work properly if /var/lib/flatpak doesn't exist.
  * The bubblewrap version required for system-bwrap is now 0.2.1.
 
 Major changes in 0.11.7
@@ -702,11 +702,11 @@ Major changes in 0.10.1
 
  * New command "flatpak remote-info" shows information about applications
  in a remote. In particular the --log operation shows the history and
- can be used in combination with flatpak upate --commit=XYZ to roll
+ can be used in combination with flatpak update --commit=XYZ to roll
  back to a previous version.
  * New command "flatpak search" which allows you to search the appstream
  data from the commandline.
- * flatpak update now upates appstream data for all confured remotes, which
+ * flatpak update now updates appstream data for all confured remotes, which
  is important for search to work.
  * Allow automatic installation of gtk themes matching the active theme.
  * Handle the case when /etc/resolv.conf is a symlink
@@ -808,8 +808,8 @@ Major changes in 0.9.11
  * You can now show all outstanding updates with: flatpak remote-ls --updates
  * The dbus filter "org.name.*" now means all subnames of org.name, not just
  the first level. This matches how dbus arg0namespace works, and how the
- comming dbus container support will work.
- * Fixed segfauld on update
+ coming dbus container support will work.
+ * Fixed segfault on update
  * Better commandline tab completion
  * Flatpak now exposes host icons readonly as /run/host/share/icons to the sandbox.
 
@@ -920,7 +920,7 @@ Major changes in 0.9.5
  * document-portal: The app-specific directory is always accessible
  to the app, take this into consideration for AddFull.
  * builder: Don't warn for unknown keys if they start with x-
- * Fix a race condition whe restarting the document portal
+ * Fix a race condition when restarting the document portal
  * build-update-repo: Don't list removed deltas in the summary
  * list: Don't show .Locale/.Debug/.Sources by default. Show with -a.
  * remote-ls: Don't show .Locale/.Debug/.Sources, or non-primary
@@ -942,7 +942,7 @@ Major changes in 0.9.4
  * Now requires ostree 2017.6 and bubblewrap 0.1.8
  * Better progress reporting in CLI and UI
  * Improved output from commands info, list, remotes,
- remote-ls: More detail, colors, nicer table formating.
+ remote-ls: More detail, colors, nicer table formatting.
  * New command flatpak repo that lets you show information
  about local repositories.
  * When launching exported desktop files, the paths
@@ -1072,7 +1072,7 @@ Major changes in 0.9.2
  * OCI support now works with the system-helper for unprivileged systemwide
  installation.
  * Experimental support for the new ostree bare-user-only repo mode that
- allows flatpak to run on filesytems without xattrs. Set
+ allows flatpak to run on filesystems without xattrs. Set
  FLATPAK_OSTREE_REPO_MODE=user-only in the environment to use this.
  * builder: New property disable-fsckobjects for git sources
  * builder: New property commit for git sources. This lets you specify
@@ -1101,7 +1101,7 @@ Major changes in 0.9.2
  this is optional in later versions of ostree. Instead we use
  they python SimpleHTTPServer.
  * The minimum glib version has been corrected to 2.44.
- * The minumum automake version has been increased to 1.13.4
+ * The minimum automake version has been increased to 1.13.4
  because some older version didn't work.
 
 Major changes in 0.9.1
@@ -1447,7 +1447,7 @@ Major changes in 0.6.12
  can now only have dashes in the last element. This allows
  apps to export files such as org.my.App-extra.desktop which
  was used by the libreoffice builds.
- * By default the kernel keyring is not accessable, as it is
+ * By default the kernel keyring is not accessible, as it is
  not containable.
  * Some robustness fixes for build-commit-from
  * Better error messages
@@ -1547,7 +1547,7 @@ Major changes in 0.6.8
  * Requires OSTree 2016.7, allowing us to enable use of static delta
  for system downloads again.
  * Support --no-desktop which allows you to run a flatpak app outside
- a desktop, with some loss of functionallity (for example, there
+ a desktop, with some loss of functionality (for example, there
  will be no systemd --user scope created for the app)..
  * More documentation.
  * Memory leak fixes.

app/flatpak-builtins-build-export.c

@@ -938,7 +938,7 @@ flatpak_builtin_build_export (int argc, char **argv, GCancellable *cancellable,
  goto out;
 
  /* This is useful only if the target is a "bare" rep, but this happens
- in flatpak-builder when commiting to the cache repo. For other repos
+ in flatpak-builder when committing to the cache repo. For other repos
  this is a no-op */
  if (!ostree_repo_scan_hardlinks (repo, cancellable, error))
  goto out;

app/flatpak-builtins-history.c

@@ -54,7 +54,7 @@ static GOptionEntry options[] = {
 };
 
 static Column all_columns[] = {
- { "time", N_("Time"), N_("Show when the change happend"),  0, FLATPAK_ELLIPSIZE_MODE_NONE, 1, 1 },
+ { "time", N_("Time"), N_("Show when the change happened"), 0, FLATPAK_ELLIPSIZE_MODE_NONE, 1, 1 },
  { "change", N_("Change"), N_("Show the kind of change"), 0, FLATPAK_ELLIPSIZE_MODE_NONE, 1, 1 },
  { "ref", N_("Ref"), N_("Show the ref"), 0, FLATPAK_ELLIPSIZE_MODE_NONE, 0, 0 },
  { "application", N_("Application"), N_("Show the application/runtime ID"), 0, FLATPAK_ELLIPSIZE_MODE_NONE, 1, 1 },

app/flatpak-builtins-utils.c

@@ -80,7 +80,7 @@ looks_like_branch (const char *branch)
  return FALSE;
 
  /* Dots are allowed in branches, but not really used much, while
- app ids require at least two, so thats a good check to
+ app ids require at least two, so that's a good check to
  distinguish the two */
  dot = strchr (branch, '.');
  if (dot != NULL)

app/flatpak-builtins.h

@@ -46,7 +46,7 @@ G_BEGIN_DECLS
  *
  * Flags affecting the behavior of flatpak_option_context_parse().
  *
- * If the default system installation is among the returned diretories,
+ * If the default system installation is among the returned directories,
  * it will be returned first.
  */
 typedef enum {

app/flatpak-cli-transaction.c

@@ -122,7 +122,7 @@ add_new_remote (FlatpakTransaction *transaction,
  if (reason == FLATPAK_TRANSACTION_REMOTE_GENERIC_REPO)
  {
  if (flatpak_yes_no_prompt (TRUE, /* default to yes on Enter */
- _("The remote '%s', refered to by '%s' at location %s contains additional applications.\n"
+ _("The remote '%s', referred to by '%s' at location %s contains additional applications.\n"
  "Should the remote be kept for future installations?"),
  remote_name, from_id, url))
  return TRUE;

buildutil/tap-driver.sh

@@ -370,7 +370,7 @@ function setup_result_obj(line)
  sub("^(not )?ok[ \t]*", "", line)
 
  # If the result has an explicit number, get it and strip it; otherwise,
- # automatically assing the next progressive number to it.
+ # automatically assign the next progressive number to it.
  if (line ~ /^[0-9]+$/ || line ~ /^[0-9]+[^a-zA-Z0-9_]/)
  {
  match(line, "^[0-9]+")

common/flatpak-context.c

@@ -2108,7 +2108,7 @@ flatpak_context_append_bwrap_filesystem (FlatpakContext *context,
  flatpak_exports_append_bwrap_args (exports, bwrap);
 
  /* Special case subdirectories of the cache, config and data xdg
- * dirs. If these are accessible explicilty, then we bind-mount
+ * dirs. If these are accessible explicitly, then we bind-mount
  * these in the app-id dir. This allows applications to explicitly
  * opt out of keeping some config/cache/data in the app-specific
  * directory.

common/flatpak-dir.c

@@ -943,7 +943,7 @@ get_system_locations (GCancellable *cancellable,
  */
  locations = system_locations_from_configuration (cancellable, error);
 
- /* Only fill the details of the default directory if not overriden. */
+ /* Only fill the details of the default directory if not overridden. */
  if (!has_system_location (locations, SYSTEM_DIR_DEFAULT_ID))
  {
  append_new_system_location (locations,
@@ -2597,7 +2597,7 @@ _flatpak_dir_ensure_repo (FlatpakDir *self,
  }
  }
 
- /* Earlier flatpak used to reset min-free-space-percent to 0 everytime, but now we
+ /* Earlier flatpak used to reset min-free-space-percent to 0 every time, but now we
  * favor min-free-space-size instead of it (See below).
  */
  if (!flatpak_dir_use_system_helper (self, NULL))
@@ -7290,7 +7290,7 @@ flatpak_dir_deploy (FlatpakDir *self,
  return TRUE;
 }
 
-/* -origin remotes are deleted when the last ref refering to it is undeployed */
+/* -origin remotes are deleted when the last ref referring to it is undeployed */
 void
 flatpak_dir_prune_origin_remote (FlatpakDir *self,
  const char *remote)
@@ -10491,7 +10491,7 @@ filter_out_deployed_refs (FlatpakDir *self,
  * you should consider using flatpak_dir_prune() to do that.
  *
  * Since: 0.10.0
- * Returns: %TRUE if cleaning up the refs suceeded, %FALSE otherwise
+ * Returns: %TRUE if cleaning up the refs succeeded, %FALSE otherwise
  */
 gboolean
 flatpak_dir_cleanup_undeployed_refs (FlatpakDir *self,

common/flatpak-exports.c

@@ -49,7 +49,7 @@
 #include "flatpak-error.h"
 
 /* We don't want to export paths pointing into these, because they are readonly
- (so we can't create mountpoints there) and don't match whats on the host anyway */
+ (so we can't create mountpoints there) and don't match what's on the host anyway */
 const char *dont_export_in[] = {
  "/lib", "/lib32", "/lib64", "/bin", "/sbin", "/usr", "/etc", "/app", "/dev", "/proc", NULL
 };

common/flatpak-portal-error.h

@@ -34,7 +34,7 @@ G_BEGIN_DECLS
  * FlatpakPortalError:
  * @FLATPAK_PORTAL_ERROR_FAILED: General portal failure
  * @FLATPAK_PORTAL_ERROR_INVALID_ARGUMENT: An argument was invalid
- * @FLATPAK_PORTAL_ERROR_NOT_FOUND: The object was not fount
+ * @FLATPAK_PORTAL_ERROR_NOT_FOUND: The object was not found
  * @FLATPAK_PORTAL_ERROR_EXISTS: The object already exists
  * @FLATPAK_PORTAL_ERROR_NOT_ALLOWED: The call was not allowed
  * @FLATPAK_PORTAL_ERROR_CANCELLED: The call was cancelled by the user

common/flatpak-remote-ref.c

@@ -270,7 +270,7 @@ flatpak_remote_ref_get_download_size (FlatpakRemoteRef *self)
  * flatpak_remote_ref_get_metadata:
  * @self: a #FlatpakRemoteRef
  *
- * Returns the app metadata from the metadata cach of the ref.
+ * Returns the app metadata from the metadata cache of the ref.
  *
  * Returns: (transfer none) (nullable): a #GBytes with the metadata file
  * contents or %NULL

common/flatpak-run.c

@@ -1729,7 +1729,7 @@ flatpak_run_allocate_id (int *lock_fd_out)
  * file and take a write lock on .ref to ensure its not in
  * use. */
  lock_fd = open (lock_file, O_RDWR | O_CREAT | O_CLOEXEC, 0644);
- /* There is a tiny race here between the open creating the file and the lock suceeding.
+ /* There is a tiny race here between the open creating the file and the lock succeeding.
  We work around that by only gc:ing "old" .ref files */
  if (lock_fd != -1 && fcntl (lock_fd, F_SETLK, &l) == 0)
  {

common/flatpak-transaction.c

@@ -691,7 +691,7 @@ flatpak_transaction_operation_get_commit (FlatpakTransactionOperation *self)
  * Gets the maximum download size for the operation.
  *
  * Note that this does not include the size of dependencies, and
- * the acutal download may be smaller, if some of the data is already
+ * the actual download may be smaller, if some of the data is already
  * available locally.
  *
  * For uninstall operations, this returns 0.
@@ -715,7 +715,7 @@ flatpak_transaction_operation_get_download_size (FlatpakTransactionOperation *se
  * Gets the installed size for the operation.
  *
  * Note that even for a new install, the extra space required on
- * disk may be smaller than this numer, if some of the data is already
+ * disk may be smaller than this number, if some of the data is already
  * available locally.
  *
  * For uninstall operations, this returns 0.
@@ -2099,7 +2099,7 @@ resolve_ops (FlatpakTransaction *self,
 
  if (op->kind == FLATPAK_TRANSACTION_OPERATION_UNINSTALL)
  {
- /* We resolve to the deployed metadata, becasue we need it to uninstall related ops */
+ /* We resolve to the deployed metadata, because we need it to uninstall related ops */
 
  metadata_bytes = load_deployed_metadata (self, op->ref);
  mark_op_resolved (op, NULL, metadata_bytes, NULL);
@@ -2266,7 +2266,7 @@ sort_ops (FlatpakTransaction *self)
  sorted = g_list_concat (run, sorted); /* prepends, so reverse at the end */
 
  /* Then greedily run ops that become runnable, in run_after_prio order, so that
- related ops are run before depdendencies */
+ related ops are run before dependencies */
  run_op->run_before_ops = g_list_sort (run_op->run_before_ops, (GCompareFunc) compare_op_prio);
  for (l = run_op->run_before_ops; l != NULL; l = l->next)
  {

common/flatpak-utils.c

@@ -5747,7 +5747,7 @@ progress_cb (OstreeAsyncProgress *progress, gpointer user_data)
  * Fetches:
  * - fetched: sum of content + metadata fetches
  * - requested: sum of requested content and metadata fetches
- * - bytes_transferred: every and all tranferred data (in bytes)
+ * - bytes_transferred: every and all transferred data (in bytes)
  * - metadata_fetched: the number of fetched metadata objects
  * - outstanding_fetches: missing fetches (metadata + content + deltas)
  * - outstanding_delta_fetches: missing delta-only fetches

common/valgrind-private.h

@@ -1673,7 +1673,7 @@ typedef
 /* NB 9 Sept 07. There is a nasty kludge here in all these CALL_FN_
  macros. In order not to trash the stack redzone, we need to drop
  %rsp by 128 before the hidden call, and restore afterwards. The
- nastyness is that it is only by luck that the stack still appears
+ nastiness is that it is only by luck that the stack still appears
  to be unwindable during the hidden call - since then the behaviour
  of any routine using this macro does not match what the CFI data
  says. Sigh.

doc/flatpak-create-usb.xml

@@ -45,14 +45,14 @@
  media mounted at <arg choice="plain">MOUNT-PATH</arg>, along with all the dependencies and
  metadata needed for installing them. This is one way of transferring flatpaks
  between computers that doesn't require an Internet connection. After using
- this comand, the USB drive can be connected to another computer and
+ this command, the USB drive can be connected to another computer and
  <command>flatpak install</command> will prefer to install from it rather than
  the Internet if the refs are the newest available. For this process to work a
  collection ID must be configured on the relevant remotes on both the source
  and destination computers, and on the remote server.
  </para>
  <para>
- Each <arg choice="plain">REF</arg> argument is a full or partial indentifier in the
+ Each <arg choice="plain">REF</arg> argument is a full or partial identifier in the
  flatpak ref format, which looks like "(app|runtime)/ID/ARCH/BRANCH". All elements
  except ID are optional and can be left out, including the slashes,
  so most of the time you need only specify ID. Any part left out will be matched

doc/flatpak-install.xml

@@ -55,7 +55,7 @@
  and the user is asked to confirm the resulting choice.
  </para>
  <para>
- Each <arg choice="plain">REF</arg> argument is a full or partial indentifier in the
+ Each <arg choice="plain">REF</arg> argument is a full or partial identifier in the
  flatpak ref format, which looks like "(app|runtime)/ID/ARCH/BRANCH".
  All elements except ID are optional and can be left out, including the slashes,
  so most of the time you need only specify ID. Any part left out will be matched

doc/flatpak-remote-ls.xml

@@ -148,7 +148,7 @@
  <term><option>--arch=ARCH</option></term>
 
  <listitem><para>
- Show only those matching the specied architecture. By default, only
+ Show only those matching the specified architecture. By default, only
  supported architectures are shown. Use <option>--arch=*</option> to show all architectures.
  </para></listitem>
  </varlistentry>

doc/flatpak-spawn.xml

@@ -140,7 +140,7 @@
  the instance directory (i.e. <filename>~/.var/app/$APP_ID/sandbox</filename>).
  <para></para>
  This option is useful in combination with <option>--sandbox</option> (otherwise the
- instance diretory is accessible anyway).
+ instance directory is accessible anyway).
  </para></listitem>
  </varlistentry>
 
@@ -155,7 +155,7 @@
  the instance directory (i.e. <filename>~/.var/app/$APP_ID/sandbox</filename>).
  <para></para>
  This option is useful in combination with <option>--sandbox</option> (otherwise the
- instance diretory is accessible anyway).
+ instance directory is accessible anyway).
  </para></listitem>
  </varlistentry>
 

doc/flatpak-uninstall.xml

@@ -44,7 +44,7 @@
  application or runtime to uninstall.
  </para>
  <para>
- Each <arg choice="plain">REF</arg> argument is a full or partial indentifier in the
+ Each <arg choice="plain">REF</arg> argument is a full or partial identifier in the
  flatpak ref format, which looks like "(app|runtime)/ID/ARCH/BRANCH". All elements
  except ID are optional and can be left out, including the slashes,
  so most of the time you need only specify ID. Any part left out will be matched

doc/flatpak-update.xml

@@ -51,7 +51,7 @@
  is updated, as well as appstream info for all remotes.
  </para>
  <para>
- Each <arg choice="plain">REF</arg> argument is a full or partial indentifier in the
+ Each <arg choice="plain">REF</arg> argument is a full or partial identifier in the
  flatpak ref format, which looks like "(app|runtime)/ID/ARCH/BRANCH". All elements
  except ID are optional and can be left out, including the slashes,
  so most of the time you need only specify ID. Any part left out will be matched

doc/flatpak.xml

@@ -82,7 +82,7 @@
  </para>
 
  <para>
- Basic commands for buiding flatpaks such as build-init, build and build-finish
+ Basic commands for building flatpaks such as build-init, build and build-finish
  are included in the flatpak utility. For higher-level build support, see
  the separate 
  <citerefentry><refentrytitle>flatpak-builder</refentrytitle><manvolnum>1</manvolnum></citerefentry> tool.

portal/flatpak-portal.c

@@ -200,7 +200,7 @@ child_setup_func (gpointer user_data)
  }
  }
 
- /* Second pass in case we needed an inbetween fd value to avoid conflicts */
+ /* Second pass in case we needed an in-between fd value to avoid conflicts */
  for (i = 0; i < data->fd_map_len; i++)
  {
  if (fd_map[i].to != fd_map[i].final)

session-helper/flatpak-session-helper.c

@@ -158,7 +158,7 @@ child_setup_func (gpointer user_data)
  }
  }
 
- /* Second pass in case we needed an inbetween fd value to avoid conflicts */
+ /* Second pass in case we needed an in-between fd value to avoid conflicts */
  for (i = 0; i < data->fd_map_len; i++)
  {
  if (fd_map[i].to != fd_map[i].final)