pkg: fix typos found by codespell

pkg/lib/cockpit-components-dynamic-list.jsx

@@ -25,7 +25,7 @@ import './cockpit-components-dynamic-list.scss';
  * [
  * { name: "Name must not be empty }, // first row
  * { }, // second row
- * { name: "Name cannot containt number", email: "Email must contain '@'" } // third row
+ * { name: "Name cannot contain a number", email: "Email must contain '@'" } // third row
  * ]
  */
 export class DynamicListForm extends React.Component {

pkg/lib/cockpit-connect-ssh.tsx

@@ -549,7 +549,7 @@ const error_dialogs = {
  * @host: Same `[user@]host[:port]` format as the channel option; must be
  * *exactly* the same as for opening the channel afterwards
  * @user: Same as the channel option; overrides `user@` portion of @host
- * Returns: Nothing on success. Afterwards the SSH conection is established and
+ * Returns: Nothing on success. Afterwards the SSH connection is established and
  * you can use the `host` option in channels. Throws a "cancel"
  * exception if the user cancelled the dialog. Most SSH errors are
  * handled in the dialogs, but you still have to expect and check for

pkg/lib/dialogs.tsx

@@ -98,7 +98,7 @@
  *
  * - Dialogs.run(component, {... props})
  *
- * Shows a dialog and asyncronously waits for it to close. This creates and
+ * Shows a dialog and asynchronously waits for it to close. This creates and
  * shows a MyDialog with the given properties, plus a special "dialogResult"
  * property which has .resolve() and .reject() methods on it. Calling either
  * of those will resolve the promise returned by Dialogs.run() accordingly,

pkg/metrics/metrics.scss

@@ -30,7 +30,7 @@ html {
  --resource-icon-color-middle: var(--pf-v5-global--palette--orange-500);
  --resource-icon-color-full: var(--pf-v5-global--palette--orange-200);
 
- // Adjust alert color to seperate itself from the history section background
+ // Adjust alert color to separate itself from the history section background
  .pf-v5-c-alert {
  --pf-v5-c-alert--m-inline--m-info--BackgroundColor: var(--pf-v5-global--BackgroundColor--dark-400);
  }

pkg/networkmanager/interfaces.js

@@ -590,7 +590,7 @@ export function NetworkManagerModel() {
  listen_port: get("wireguard", "listen-port", 0),
  peers: get("wireguard", "peers", []).map(peer => ({
  publicKey: peer['public-key'].v,
- endpoint: peer.endpoint?.v, // enpoint of a peer is optional
+ endpoint: peer.endpoint?.v, // endpoint of a peer is optional
  allowedIps: peer['allowed-ips']?.v
  })),
  };

pkg/networkmanager/networking.scss

@@ -115,8 +115,8 @@ th {
  margin-inline-start: var(--pf-v5-global--spacer--sm);
 }
 
-// The modal body, by default, overflows to accomodate extra content. This is
-// normall good. However, it also can trim things that flow outside, such as
+// The modal body, by default, overflows to accommodate extra content. This is
+// normally good. However, it also can trim things that flow outside, such as
 // the focus ring of the MTU custom input. Since we know the modal won't have
 // much vertical content, we can disable the overflow to let the focus ring be
 // fully visible. (Otherwise the bottommost pixels are removed.)

pkg/shell/machines/machines.js

@@ -606,7 +606,7 @@ function Loader(machines, session_only) {
  interface: "org.freedesktop.DBus.Properties",
  member: "PropertiesChanged"
  },
- function (path, iface, mamber, args) {
+ function (path, iface, member, args) {
  if (args[0] == "cockpit.Packages") {
  if (args[1].Manifests) {
  const manifests = JSON.parse(args[1].Manifests.v);

pkg/shell/nav.jsx

@@ -18,7 +18,7 @@ export const SidebarToggle = () => {
  /* This is a HACK for catching lost clicks on the pages which live in iframes so as to close dropdown menus on the shell.
  * Note: Clicks on an <iframe> element won't trigger document.documentElement listeners, because it's literally different page with different security domain.
  * However, when clicking on an iframe moves focus to its content's window that triggers the main window.blur event.
- * Addionally, when clicking on an element in the same iframe make sure to unset the 'active' state of the 'System' dropdown selector.
+ * Additionally, when clicking on an element in the same iframe make sure to unset the 'active' state of the 'System' dropdown selector.
  */
  const handleClickOutside = (ev) => {
  if (ev.target.id == "nav-system-item")

pkg/shell/nav.scss

@@ -471,7 +471,7 @@ $desktop: $phone + 1px;
  // PF uses margin for non-first elements; it really should use gap in the
  // parent instead; fixing it with a local override, specific for our menu, as
  // we really need it for mobile. It changes desktop too, but does the right
- // thing there (but it's not visabily noticable in desktop).
+ // thing there (but it's not visibly noticeable in desktop).
  .nav-item {
  --pf-v5-c-nav__item--MarginTop: 0;
  }

pkg/storaged/btrfs/utils.jsx

@@ -41,7 +41,7 @@ export function btrfs_device_usage(client, uuid, path) {
 }
 
 /**
- * Calculate the overal btrfs "volume" usage. UDisks only knows the usage per block.
+ * Calculate the overall btrfs "volume" usage. UDisks only knows the usage per block.
  */
 export function btrfs_usage(client, volume) {
  const block_fsys = client.blocks_fsys[volume.path];

pkg/storaged/client.js

@@ -338,7 +338,7 @@ function btrfs_findmnt_poll() {
  btrfs_mounts[fs.uuid] = { };
  }
 
- // We need to handle multiple mounts, they are listed seperate.
+ // We need to handle multiple mounts, they are listed separate.
  if (subvolid in btrfs_mounts[fs.uuid]) {
  btrfs_mounts[fs.uuid][subvolid].mount_points.push(fs.target);
  } else {

pkg/storaged/lvm2/block-logical-volume.jsx

@@ -124,7 +124,7 @@ function repair(lvol) {
 
  dialog_open({
  Title: cockpit.format(_("Repair logical volume $0"), lvol.Name),
- Body: <div><p>{cockpit.format(_("Select the physical volumes that should be used to repair the logical volume. At leat $0 are needed."),
+ Body: <div><p>{cockpit.format(_("Select the physical volumes that should be used to repair the logical volume. At least $0 are needed."),
  fmt_size(missing))}</p><br /></div>,
  Fields: [
  SelectSpaces("pvs", _("Physical Volumes"),

pkg/storaged/lvm2/create-logical-volume-dialog.jsx

@@ -155,7 +155,7 @@ export function create_logical_volume(client, vgroup) {
 
  function min_pvs_explanation(pvs, min) {
  if (pvs.length <= min)
- return cockpit.format(_("All $0 selected physical volumes are needed for the choosen layout."),
+ return cockpit.format(_("All $0 selected physical volumes are needed for the chosen layout."),
  pvs.length);
  return null;
  }

pkg/storaged/mdraid/mdraid.jsx

@@ -281,7 +281,7 @@ const MDRaidCard = ({ card, mdraid, block }) => {
  if (missing_bitmap(mdraid)) {
  alerts.push(
  <Alert isInline variant="warning" key="bitmap"
- title={_("This MDRAID device has no write-intent bitmap. Such a bitmap can reduce sychronization times significantly.")}>
+ title={_("This MDRAID device has no write-intent bitmap. Such a bitmap can reduce synchronization times significantly.")}>
  <div className="storage-alert-actions">
  <StorageButton onClick={fix_bitmap}>{_("Add a bitmap")}</StorageButton>
  </div>

pkg/storaged/pages.jsx

@@ -127,7 +127,7 @@ const _ = cockpit.gettext;
 
  When a page appears in such a crossref table, it has dedicated
  actions, a dedicated size, and generally looks different from when
- it appears in a "normal" childrens table. This is another source of
+ it appears in a "normal" children's table. This is another source of
  complication of how cards and pages interact.
 */
 

pkg/storaged/storage.scss

@@ -228,7 +228,7 @@ a.disabled {
  var(--bg-light) 50%
  ) top left;
  background-size: var(--pf-v5-global--spacer--sm) var(--pf-v5-global--spacer--sm);
- // Overlay at 1/3 to mix the light and dark against the trough color
+ // Overlay at 1/3 to mix the light and dark against the through color
  opacity: 0.333;
  }
 

pkg/storaged/utils.js

@@ -679,7 +679,7 @@ export function should_ignore(client, path) {
 /* GET_CHILDREN gets the direct children of the storage object at
  PATH, like the partitions of a partitioned block device, or the
  volume group of a physical volume. By calling GET_CHILDREN
- recursively, you can traverse the whole storage hierachy from
+ recursively, you can traverse the whole storage hierarchy from
  hardware drives at the bottom to filesystems at the top.
 
  GET_CHILDREN_FOR_TEARDOWN is similar but doesn't consider things