From 0a2c2f173996cb35611ab09b5b9165c15a38c6b0 Mon Sep 17 00:00:00 2001
From: Claude Becker <becker@phys.ethz.ch>
Date: Fri, 7 Feb 2025 10:57:41 +0100
Subject: [PATCH] spellcheck

---
 ...rough_a_pci_network_card_into_a_xen_domu.markdown |  6 +++---
 .../how_to_setup_the_serial_console.markdown         |  4 ++--
 documentation/katex.markdown                         | 10 +++++-----
 documentation/locales.markdown                       |  2 +-
 ..._software_package_with_the_gnu_autotools.markdown | 10 +++++-----
 documentation/managing_perl_code.markdown            |  6 +++---
 documentation/microsoft365.markdown                  |  2 +-
 .../notes_on_linux_package_management.markdown       |  2 +-
 documentation/podman.markdown                        |  6 +++---
 ...tting_up_a_x_server_for_diskless_clients.markdown |  4 ++--
 ...d-phys_workstation_to_d-phys_workstation.markdown |  6 +++---
 documentation/subversion.markdown                    | 10 +++++-----
 documentation/testing_hardware.markdown              |  6 +++---
 documentation/transfer_browser_bookmarks.markdown    |  4 ++--
 documentation/troubleshooting_ntp.markdown           | 10 +++++-----
 documentation/vaultwarden.markdown                   |  6 +++---
 documentation/vim.markdown                           |  2 +-
 documentation/weechat.markdown                       |  8 ++++----
 documentation/zoom.markdown                          |  2 +-
 ..._over_linux_at_the_department_of_physics.markdown |  2 +-
 ..._to_use_usb_harddisk_or_usb_memorysticks.markdown |  4 ++--
 linux/personal_groups.markdown                       |  2 +-
 .../software_on_the_d-phys_linux_computers.markdown  | 12 ++++++------
 linux/using_your_cd_writer_under_linux.markdown      |  6 +++---
 linux/vpn_with_linux.markdown                        |  2 +-
 mail/how_to_use_email_with_mutt_imap.markdown        |  2 +-
 mail/how_to_use_email_with_outlook.markdown          |  2 +-
 mail/how_to_use_email_with_outlook_on_mac.markdown   |  2 +-
 mail/how_to_use_email_with_thunderbird.markdown      |  2 +-
 mail/outlook-problems.markdown                       |  2 +-
 30 files changed, 72 insertions(+), 72 deletions(-)

diff --git a/documentation/how_to_loopthrough_a_pci_network_card_into_a_xen_domu.markdown b/documentation/how_to_loopthrough_a_pci_network_card_into_a_xen_domu.markdown
index ba56887f..b15813e6 100644
--- a/documentation/how_to_loopthrough_a_pci_network_card_into_a_xen_domu.markdown
+++ b/documentation/how_to_loopthrough_a_pci_network_card_into_a_xen_domu.markdown
@@ -30,13 +30,13 @@ If you have two network cards in your Xen Dom0 and want to use one inside a DomU
 
 ### Adapt network configuration inside the DomU
 
-* Edit `/etc/network/interfaces` and add the same configuration as for the to be replaced network interface und a new interface name with a number one higher than highest one ever used until then. See [[#Footnotes]] below.
+* Edit `/etc/network/interfaces` and add the same configuration as for the to be replaced network interface and a new interface name with a number one higher than highest one ever used until then. See [[#Footnotes]] below.
 
-### Shutdown the DomU to which the PCI card should be loopthroughed
+### Shutdown the DomU to which the PCI card should be loopthrough-ed
 
 ### Edit /etc/xen/$DOMU.cfg
 
-* Comment out any former network configuration (calling of bridging scripts, MAC addresses, IP addresses, DHCP, etc.) for the connection you want to replace by the loopthroughed network card.
+* Comment out any former network configuration (calling of bridging scripts, MAC addresses, IP addresses, DHCP, etc.) for the connection you want to replace by the loopthrough-ed network card.
 * Add `pci = [ '$PCIBUSID' ]`
 
 ```
diff --git a/documentation/how_to_setup_the_serial_console.markdown b/documentation/how_to_setup_the_serial_console.markdown
index f0ef6df8..49c96ad1 100644
--- a/documentation/how_to_setup_the_serial_console.markdown
+++ b/documentation/how_to_setup_the_serial_console.markdown
@@ -9,7 +9,7 @@ It is not strictly necessary to have each component fully functional, but it can
 Serial Console BIOS configuration
 ---------------------------------
 
-Refer to your Hardware vendor's documentaion for capabilities and procedures to enable BIOS serial redirection.
+Refer to your Hardware vendor's documentation for capabilities and procedures to enable BIOS serial redirection.
 
 We will use the serial port **com1**.
 
@@ -59,6 +59,6 @@ To automatically start a login prompt over the serial port, add the line:
 T0:23:respawn:/sbin/getty ttyS0 57600 vt100
 ```
 
-to `/etc/inittab`. Run **telinit q** to force a reload of your inttab and start getty.
+to `/etc/inittab`. Run **telinit q** to force a reload of your inittab and start getty.
 
 To enable root logins, add **ttyS0** to `/etc/securetty` if not already present.
diff --git a/documentation/katex.markdown b/documentation/katex.markdown
index d3e8d9a0..0be00c0e 100644
--- a/documentation/katex.markdown
+++ b/documentation/katex.markdown
@@ -1,6 +1,6 @@
 # KaTeX
 
-[KaTeX](https://khan.github.io/KaTeX/) is a fast math typesetting library for the web. It uses javascript for client-side rendering.
+[KaTeX](https://khan.github.io/KaTeX/) is a fast math typesetting library for the web. It uses JavaScript for client-side rendering.
 
 This guide shows how to include KaTeX from a CDN and automatically render all latex content on your page. This is done using the `auto-render.js` script [included in KaTeX](https://github.com/Khan/KaTeX/tree/master/contrib/auto-render).
 
@@ -45,7 +45,7 @@ $$f(x) = \int_{-\infty}^\infty \hat f(\xi)\,e^{2 \pi i \xi x} \,d\xi$$
 
 ## How to use KaTex on your page
 
-Add the following inside the html `<head></head>` section:
+Add the following inside the HTML `<head></head>` section:
 
 ```html
 <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/katex@0.10.0-beta/dist/katex.min.css" integrity="sha384-9tPv11A+glH/on/wEu99NVwDPwkMQESOocs/ZGXPoIiLE8MU/qkqUcZ3zzL+6DuH" crossorigin="anonymous">
@@ -53,7 +53,7 @@ Add the following inside the html `<head></head>` section:
 <script src="https://cdn.jsdelivr.net/npm/katex@0.10.0-beta/dist/contrib/auto-render.min.js" integrity="sha384-aGfk5kvhIq5x1x5YdvCp4upKZYnA8ckafviDpmWEKp4afOZEqOli7gqSnh8I6enH" crossorigin="anonymous"></script>
 ```
 
-Add the following (to the end) inside the html `<body></body>` section:
+Add the following (to the end) inside the HTML `<body></body>` section:
 
 ```html
 <script>
@@ -72,8 +72,8 @@ Add the following (to the end) inside the html `<body></body>` section:
 </script>
 ```
 
-This script will parse the whole html body and render everything enclosed in the defined delimiters. It also defines some custom delimiters.
+This script will parse the whole HTML body and render everything enclosed in the defined delimiters. It also defines some custom delimiters.
 
-### Example html files
+### Example HTML files
 
 You can find some examples [here](https://people.phys.ethz.ch/~rda/katex/)
diff --git a/documentation/locales.markdown b/documentation/locales.markdown
index f96219a6..5c7d0139 100644
--- a/documentation/locales.markdown
+++ b/documentation/locales.markdown
@@ -28,7 +28,7 @@ Check whether the default locale is already set to a reasonable value
 cat /etc/default/locale
 ```
 
-If necessary, set the default locale (`en_US.UTF-8` is a resonable value)
+If necessary, set the default locale (`en_US.UTF-8` is a reasonable value)
 
 ```
 echo 'LANG="en_US.UTF-8"' > /etc/default/locale
diff --git a/documentation/managing_a_software_package_with_the_gnu_autotools.markdown b/documentation/managing_a_software_package_with_the_gnu_autotools.markdown
index 814e3773..5b4cd4af 100644
--- a/documentation/managing_a_software_package_with_the_gnu_autotools.markdown
+++ b/documentation/managing_a_software_package_with_the_gnu_autotools.markdown
@@ -9,13 +9,13 @@ make
 make install
 ```
 
-If the `configure` script follows the [GNU coding standards](http://www.gnu.org/prep/standards/html_node/Configuration.html) you can choose some parameters like `./configure --prefix=/opt/local` to change the behavior in a consistent way.  This particular example is how the [MacPorts](http://macports.org/) people like to configure their packages.  In general, using configure will make it easy to create software packages for a variety of systems (like Debian, Redhat, MacPorts, etc.).
+If the `configure` script follows the [GNU coding standards](http://www.gnu.org/prep/standards/html_node/Configuration.html) you can choose some parameters like `./configure --prefix=/opt/local` to change the behavior in a consistent way.  This particular example is how the [MacPorts](http://macports.org/) people like to configure their packages.  In general, using configure will make it easy to create software packages for a variety of systems (like Debian, RedHat, MacPorts, etc.).
 
 Writing a `configure` script that works in all circumstances can be a challenge.  For this reason software has been written to help with the task.  This collection of tools has grown over time and is generally known as the [GNU build system](http://en.wikipedia.org/wiki/GNU_build_system) or shorter as autotools.  Its main components are autoconf and automake.
 
-Learning the autotools can be hard if you dive into the comprehensive manuals (for [autoconf](http://www.gnu.org/software/autoconf/manual/index.html), [automake](http://www.gnu.org/software/automake/manual/automake.html), etc.) or if you use an existing software package as an example.  There are so many details pertaining to the particular case that you quickly loose sight of the forrest for the trees.
+Learning the autotools can be hard if you dive into the comprehensive manuals (for [autoconf](http://www.gnu.org/software/autoconf/manual/index.html), [automake](http://www.gnu.org/software/automake/manual/automake.html), etc.) or if you use an existing software package as an example.  There are so many details pertaining to the particular case that you quickly loose sight of the forest for the trees.
 
-So let us just use the most simple example we can think of.  This allows us to see the structure of an autoconfiscated package.  It will be overkill for the example but if your package starts to grow it will be a good thing if you started small.
+So let us just use the most simple example we can think of.  This allows us to see the structure of an autoconf package.  It will be overkill for the example but if your package starts to grow it will be a good thing if you started small.
 
 The Example Program
 -------------------
@@ -47,7 +47,7 @@ AC_CONFIG_FILES([Makefile])
 AC_OUTPUT
 ```
 
-This file is written in the [M4 preprocessor language](http://www.gnu.org/software/m4/).  It has function calls (or macros) that consistently use two levels of parentheses.  The macro itself uses round parentheses `()` and each argument is surrounded by square brackets `[]`.  Arguments are separated by commas `,` and the square brackets protect the arguments against macro expansion should one word be the same as a known macro.  Also inside brackets a comma will not separate two arguments.
+This file is written in the [M4 pre-processor language](http://www.gnu.org/software/m4/).  It has function calls (or macros) that consistently use two levels of parentheses.  The macro itself uses round parentheses `()` and each argument is surrounded by square brackets `[]`.  Arguments are separated by commas `,` and the square brackets protect the arguments against macro expansion should one word be the same as a known macro.  Also inside brackets a comma will not separate two arguments.
 
 `AC_INIT` sets some parameters for the package.  The package name `myfoobar` does not need to be the same as the name of the program although often it is.  The other two parameters is the version number and the e-mail address of the author.  `AC_INIT` can have more parameters which you can find in the manual.
 
@@ -110,7 +110,7 @@ make distclean
 A more Complicated Example
 --------------------------
 
-If you want to see how to use the autotools to build a program that needs to be compiled you can look at the amhello programm [in the automake manual](http://www.gnu.org/software/automake/manual/html_node/Hello-World.html).
+If you want to see how to use the autotools to build a program that needs to be compiled you can look at the amhello program [in the automake manual](http://www.gnu.org/software/automake/manual/html_node/Hello-World.html).
 
 Integration with Git
 --------------------
diff --git a/documentation/managing_perl_code.markdown b/documentation/managing_perl_code.markdown
index b9cea779..95bc23f8 100644
--- a/documentation/managing_perl_code.markdown
+++ b/documentation/managing_perl_code.markdown
@@ -10,7 +10,7 @@ If you maintain Perl code you probably want to manage your software as packages.
 
 True to their motto _There is more than one way to do it_ ([TIMTOWTDI](https://en.wikipedia.org/wiki/There's_more_than_one_way_to_do_it)) the Perl community has over the years developed several tools for the task.  As you browse the available literature you may get confused as to when to use one or the other tool.  Depending on when an article was written it may even be that some of the issues mentioned do not apply anymore.
 
-The goal of this writeup is to show how the most frequently used Perl packaging tools relate to each other.  This may help you decide how you want to package your own code.
+The goal of this write-up is to show how the most frequently used Perl packaging tools relate to each other.  This may help you decide how you want to package your own code.
 
 ExtUtils::MakeMaker
 -------------------
@@ -77,8 +77,8 @@ perl Build.PL
 
 Or if you want to submit to CPAN you will use the `.tar.gz` file generated by `dzil build` directly or even use `dzil` to upload to CPAN automatically.
 
-All of the files `dzil` generates are put in a target directory and none of your source files are changed by `dzil`.  This allows you to keep generated files strictly separate from the files you edit.  It also enables consistent builds.  `dzil build` will allways generate all boilerplate and keep the distribution of your package consistent.
+All of the files `dzil` generates are put in a target directory and none of your source files are changed by `dzil`.  This allows you to keep generated files strictly separate from the files you edit.  It also enables consistent builds.  `dzil build` will always generate all boilerplate and keep the distribution of your package consistent.
 
-`Dist::Zilla` supports both `Module::Build` and `ExtUtils::MakeMaker` as backends.  So you continue to profit from the work that went into them and avoid the burden of updating all the boilerplate.  It also allows you switch between `ExtUtils::MakeMaker` and `Module::Build` by substituting one plugin for the other.  See, you can have it both ways :-)
+`Dist::Zilla` supports both `Module::Build` and `ExtUtils::MakeMaker` as back-ends.  So you continue to profit from the work that went into them and avoid the burden of updating all the boilerplate.  It also allows you switch between `ExtUtils::MakeMaker` and `Module::Build` by substituting one plugin for the other.  See, you can have it both ways :-)
 
 For most typical projects `Dist::Zilla` is the ideal package maintenance tool.  Once your project becomes more complex you may encounter some limitations.  You can then either dig into the internals of `ExtUtils::MakeMaker` or write your own `Dist::Zilla::Plugin::`.  Writing your own plugin may well turn out to be the better choice.
diff --git a/documentation/microsoft365.markdown b/documentation/microsoft365.markdown
index f07992f3..696b0938 100644
--- a/documentation/microsoft365.markdown
+++ b/documentation/microsoft365.markdown
@@ -37,7 +37,7 @@ Setup
 * Please DO READ the license agreement and ponder its implications.
 * After submitting the request, wait for the confirmation mail.
 
-Please refer to the [pdf](https://unlimited.ethz.ch/download/attachments/36254186/CSC_Anleitung_Bestellung_M365_Cloud_Subscription.pdf?version=1&modificationDate=1678277413689&api=v2) of Informatikdienste for detailed instructions and screenshots.
+Please refer to the [PDF](https://unlimited.ethz.ch/download/attachments/36254186/CSC_Anleitung_Bestellung_M365_Cloud_Subscription.pdf?version=1&modificationDate=1678277413689&api=v2) of Informatikdienste for detailed instructions and screenshots.
 
 
 ### Install Office on macOS
diff --git a/documentation/notes_on_linux_package_management.markdown b/documentation/notes_on_linux_package_management.markdown
index 0a2075ac..4427139a 100644
--- a/documentation/notes_on_linux_package_management.markdown
+++ b/documentation/notes_on_linux_package_management.markdown
@@ -22,7 +22,7 @@ apt-file search /usr/bin/htop    # list all packages providing the given file
 apt-file list htop               # list all files contained in the given package
 ```
 
-For installed packages one can also use `dpkg -S <filename>` to show wich package installed a given file.
+For installed packages one can also use `dpkg -S <filename>` to show which package installed a given file.
 
 apt-cache policy : list priorities of available package versions
 ----------------------------------------------------------------
diff --git a/documentation/podman.markdown b/documentation/podman.markdown
index 1ab94fc0..e4ee0b4e 100644
--- a/documentation/podman.markdown
+++ b/documentation/podman.markdown
@@ -1,7 +1,7 @@
 Podman
 ======
 
-The Pod Manager tool, [podman](https://podman.io) is a daemonless container engine. It is similar to docker, but relies on the fork/exec model instead. It can therefore be used without root rights.
+The Pod Manager tool, [podman](https://podman.io) is a daemon-less container engine. It is similar to docker, but relies on the fork/exec model instead. It can therefore be used without root rights.
 
 
 Basic usage
@@ -40,9 +40,9 @@ podman system reset
 
 If you need advanced features, like multiple users inside the container, please get in touch, as we may have to enable the subuid mappings for you.
 
-### Nvidia GPU support
+### NVidia GPU support
 
-Upon request, we can configure the container support for Nvidia GPUs. An additional `--device` parameter then automatically enables `nvidia-smi` and other commands inside any container.
+Upon request, we can configure the container support for NVidia GPUs. An additional `--device` parameter then automatically enables `nvidia-smi` and other commands inside any container.
 
 ```sh
 podman run -ti --rm --device=nvidia.com/gpu=all docker.io/library/debian nvidia-smi
diff --git a/documentation/setting_up_a_x_server_for_diskless_clients.markdown b/documentation/setting_up_a_x_server_for_diskless_clients.markdown
index 50c27e7e..0a03c26b 100644
--- a/documentation/setting_up_a_x_server_for_diskless_clients.markdown
+++ b/documentation/setting_up_a_x_server_for_diskless_clients.markdown
@@ -19,7 +19,7 @@ DEFAULT vmlinuz ro initrd=initrd.img root=/dev/nfs ip=dhcp nfsroot=192.33.96.202
 
 Changes to a standard Debian (etch) in `/opt/alixboot`:
 
-Create tmpfs dirs
+Create tmpfs directories
 
 ```
 mkdir /tmp.rmdsk /etc.rmdsk /var.rmdsk
@@ -44,7 +44,7 @@ unionfs         /var        unionfs dirs=/var.rmdsk=rw:/var=nfsro           0 0
 unionfs         /tmp        unionfs dirs=/tmp.rmdsk=rw:/tmp=nfsro           0 0
 ```
 
-this mounts writable tmpfs overlays onto the ro NFS export
+this mounts writable tmpfs overlays onto the read-only NFS export
 
 `/etc/mtab`:
 
diff --git a/documentation/ssh_samples_d-phys_workstation_to_d-phys_workstation.markdown b/documentation/ssh_samples_d-phys_workstation_to_d-phys_workstation.markdown
index f8052fb0..4b576459 100644
--- a/documentation/ssh_samples_d-phys_workstation_to_d-phys_workstation.markdown
+++ b/documentation/ssh_samples_d-phys_workstation_to_d-phys_workstation.markdown
@@ -27,7 +27,7 @@ Are you sure you want to continue connecting (yes/no)? yes
 Warning: Permanently added 'paris,129.132.189.68' (RSA1)
 ```
 
-to the list of known hosts. The first time we login to another machine, ssh asks us if the machine specific key should be added to your _known_hosts_. Every time you login to this machine, ssh will check, if the hostkey of paris has changed and would warn you if this happens. This ensures, that you are connecting to the right machine and that no one has replaced it.
+to the list of known hosts. The first time we login to another machine, ssh asks us if the machine specific key should be added to your _known_hosts_. Every time you login to this machine, ssh will check, if the host key of paris has changed and would warn you if this happens. This ensures, that you are connecting to the right machine and that no one has replaced it.
 
 ## Tunneling X11
 
@@ -90,7 +90,7 @@ sftp> quit
 beat@berlin:~$
 ```
 
-## Pipeing data
+## Piping data
 
 Users familiar with the concept of UNIX Pipes will love ssh. ssh forwards STDIN, STDOUT and STDERR from and to the target machine. You may use ssh to execute a command on the remote machine and process the output on the local workstation. But see the examples:
 
@@ -98,7 +98,7 @@ Users familiar with the concept of UNIX Pipes will love ssh. ssh forwards STDIN,
 beat@berlin:~$ ssh paris ls > filelist
 ```
 
-Output of ls is written to the file filelist.
+Output of ls is written to the file file list.
 Or copy a bunch of files:
 
 ```
diff --git a/documentation/subversion.markdown b/documentation/subversion.markdown
index fe6903ab..1db5c1c4 100644
--- a/documentation/subversion.markdown
+++ b/documentation/subversion.markdown
@@ -15,7 +15,7 @@ Differences to CVS
 
 While CVS is file based and sees no relationship between files except in which directory they reside, Subversion (SVN) sees a project as a whole thing with one global state and not the states of many single files. So revision numbers are global for a whole project. One revision means a consistent state over all files. Another revision number specific difference is that revision numbers are integers and start with revision 1 at import.
 
-Another effect of Subversion's global view is, that also directories have revisions, that files can be moved around or copied with theirt whole history without fiddling around in the repository itself. Then also file properties (MIME type, svn:ignore for directories, arbitary, project-specific properties, etc.) are versioned in the repository, too.
+Another effect of Subversion's global view is, that also directories have revisions, that files can be moved around or copied with their whole history without fiddling around in the repository itself. Then also file properties (MIME type, svn:ignore for directories, arbitrary, project-specific properties, etc.) are versioned in the repository, too.
 
 Create a repository for your project
 ------------------------------------
@@ -172,7 +172,7 @@ svn delete <file or directory>
 
 (Shortcuts: `rm` or `del`)
 
-Note: the project still keeps informations about a removed file or directory in case you want to check out an old version.
+Note: the project still keeps information about a removed file or directory in case you want to check out an old version.
 
 ### Create a Directory
 
@@ -180,7 +180,7 @@ Note: the project still keeps informations about a removed file or directory in
 svn mkdir <directory>
 ```
 
-In comparision to CVS which cares only about files, Subversion also cares about directories, so if you want to create a new directory in you project, can either create it on the filesystem and then add it (see above) or just let Subversion create and add it at once.
+In comparison to CVS which cares only about files, Subversion also cares about directories, so if you want to create a new directory in you project, can either create it on the filesystem and then add it (see above) or just let Subversion create and add it at once.
 
 ### Copy or Move Files
 
@@ -194,13 +194,13 @@ svn move <source> <target>
 More information
 ----------------
 
-If you need a quick reference for one Subversion subcommand, e.g. update, use
+If you need a quick reference for one Subversion sub-command, e.g. update, use
 
 ```
 svn help update
 ```
 
-The same counts for svnadmin:
+The same counts for `svnadmin`:
 
 ```
 svnadmin help create
diff --git a/documentation/testing_hardware.markdown b/documentation/testing_hardware.markdown
index ad01cce7..360a79b4 100644
--- a/documentation/testing_hardware.markdown
+++ b/documentation/testing_hardware.markdown
@@ -7,15 +7,15 @@ There are a few things you can do to test your hardware.
 
 A rather thorough test is possible with [Memtest86](http://www.memtest86.com/).  For ISG administrators this test is available via the net-boot menu.
 
-#### Testing Harddisks
+#### Testing Hard-disks
 
 First of all you have to find out what type of harddisk you are using.  When running Linux (e.g., Knoppix if you don't have a running Linux installation on the box) you can look it up in the /proc filesystem.  E.g., for first IDE harddisk (hda, master on the first IDE port) look at the file /proc/ide/hda/model .  You will find something like `IC35L040AVVN07-0`.  Enter this model name in a [Google search](http://www.google.com/) to find some data sheets and testing software made by the manufacturer (in the example mentioned, a [IBM/Hitachi Deskstar 120GXP with 40GB](http://www.hgst.com/hdd/desk/ds120gxp.htm)).
 
-Some often used test programs for harddisks:
+Some often used test programs for hard-disks:
 
 * [Drive Fitness Test](http://www.hgst.com/hdd/support/download.htm#DFT) by IBM/Hitachi Global Storage Technologies.  ISG administrators find it under ~isg/tests/Hardware-Tests or in the net-boot menu
 * [SeaTools Diagnostic Suite](https://www.seagate.com/support/downloads/seatools/) by Seagate Technology.  ISG administrators find it under ~isg/Hardware-Tests or in the net-boot menu
-* some drive infos: `smartctl -a -d ata /dev/discs/disc0/disc` (ide=ata, scsi, 3ware)
+* some drive info: `smartctl -a -d ata /dev/discs/disc0/disc` (ide=ata, scsi, 3ware)
 * You can also use the tool [badblocks](https://manpages.debian.org/stable/e2fsprogs/badblocks.8.en.html) to do either read-only or read-write checks.
 
 #### Testing CPUs
diff --git a/documentation/transfer_browser_bookmarks.markdown b/documentation/transfer_browser_bookmarks.markdown
index 7a694015..dc251c46 100644
--- a/documentation/transfer_browser_bookmarks.markdown
+++ b/documentation/transfer_browser_bookmarks.markdown
@@ -1,7 +1,7 @@
-Transfer Browser Booksmarks
+Transfer Browser Bookmarks
 ===========================
 
-Many people use bookmarks in their browser to keep track of all the pages they need to visit. When switching computers or working remotely, it may be important to transfer the bookmarks. This can easily be achieved by exporting them to HTML on one computer, transfering the file, and importing them on the other machine. Please refer to the detailed instructions, depending on your browser.
+Many people use bookmarks in their browser to keep track of all the pages they need to visit. When switching computers or working remotely, it may be important to transfer the bookmarks. This can easily be achieved by exporting them to HTML on one computer, transferring the file, and importing them on the other machine. Please refer to the detailed instructions, depending on your browser.
 
 * [Firefox](https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer)
 * [Chrome](https://support.google.com/chrome/answer/96816?hl=en)
diff --git a/documentation/troubleshooting_ntp.markdown b/documentation/troubleshooting_ntp.markdown
index 328ab05c..be08bfcf 100644
--- a/documentation/troubleshooting_ntp.markdown
+++ b/documentation/troubleshooting_ntp.markdown
@@ -3,7 +3,7 @@ Troubleshooting NTP
 
 On our workstations we use ntpd to synchronize time with our time servers.  Normally, ntpd automatically adjusts for small inaccuracies of the system clock.  This is mainly done through the drift parameter which is recorded in /var/lib/ntp/ntp.drift
 
-Occasionally, a system clock may perform so badly that ntpd cannot find an appropriate drift paramter.  In such a case we can help with altering the tick/frequency settings.  Here are some hints to find appropriate values.
+Occasionally, a system clock may perform so badly that ntpd cannot find an appropriate drift parameter.  In such a case we can help with altering the tick/frequency settings.  Here are some hints to find appropriate values.
 
 Tweaking the Clock on a Workstation
 -----------------------------------
@@ -43,7 +43,7 @@ Now that we have a calibrated hardware clock we can calibrate the system clock a
 rm /etc/cron.d/adjust-clock
 ```
 
-The simplest way to find the right calibration parameters for system clock might be to run adjtimexconfig (again, as last time it was called when adjtimex was installed)
+The simplest way to find the right calibration parameters for system clock might be to run `adjtimexconfig` (again, as last time it was called when `adjtimex` was installed)
 
 ```
 /usr/sbin/adjtimexconfig
@@ -58,7 +58,7 @@ Alternatively, you can get an estimate for TICK/FREQ from the syslog entries col
 
 The latter might be more accurate if you ran the hardware clock calibration over the period of a few hours or days.
 
-You can then start the ntp daemon making sure to start with prestine defaults:
+You can then start the ntp daemon making sure to start with pristine defaults:
 
 ```
 /etc/init.d/ntp stop
@@ -73,9 +73,9 @@ Then watch the offset to the time servers converge or drift apart:
 watch ntpq -p
 ```
 
-If the offset still drifts too much you can play around with adjtimex and calculate some numbers by yourself according to the adjtimex(8) man page at the end.  You may also find it convenient to use the Javascript form on http://www.ep.ph.bham.ac.uk/general/support/adjtimex.html
+If the offset still drifts too much you can play around with `adjtimex` and calculate some numbers by yourself according to the adjtimex(8) man page at the end.  You may also find it convenient to use the JavaScript form on http://www.ep.ph.bham.ac.uk/general/support/adjtimex.html
 
-If you find good values for adjtimex you should write them to `/etc/default/adjtimex`
+If you find good values for `adjtimex` you should write them to `/etc/default/adjtimex`
 
 Also have a look at the ntp drift file `/var/lib/ntp/ntp.drift`
 
diff --git a/documentation/vaultwarden.markdown b/documentation/vaultwarden.markdown
index c87a2e08..98e2548f 100644
--- a/documentation/vaultwarden.markdown
+++ b/documentation/vaultwarden.markdown
@@ -20,13 +20,13 @@ If you'd just like to use Vaultwarden to manage your personal passwords, follow
 
 ### Create your Vaultwarden account
 
-- go to the Vaultwarden [web frontend](https://vault.phys.ethz.ch).
+- go to the Vaultwarden [web front-end](https://vault.phys.ethz.ch).
 - click `Create account`.
 - provide your **D-PHYS** email (we limit registrations to `@phys.ethz.ch` addresses) and name.
 - choose your master password. The longer the better.
 - click `Create account`.
 - verify your email.
-- you can now use the Vaultwarden [web frontend](https://vault.phys.ethz.ch) or
+- you can now use the Vaultwarden [web front-end](https://vault.phys.ethz.ch) or
 
 ### Install clients
 
@@ -80,7 +80,7 @@ Adding someone to an organization has to be initiated by the organization owner.
 
 ### Managing an organization
 
-If you're the owner of an organization and would like to add users, log in to the Vaultwarden [web frontend](https://vault.phys.ethz.ch) and go to `Organizations`. You can then use the `Members` tab to invite, confirm and kick users. Some notes:
+If you're the owner of an organization and would like to add users, log in to the Vaultwarden [web front-end](https://vault.phys.ethz.ch) and go to `Organizations`. You can then use the `Members` tab to invite, confirm and kick users. Some notes:
 
 - invite new users via their `@phys` email address. Note that if they've already created a Vaultwarden login, you need to invite the same email address they've used (not some alias).
 - check the 'Collections` tab to control the new user's access rights to your vaults.
diff --git a/documentation/vim.markdown b/documentation/vim.markdown
index e7cf1503..899f5276 100644
--- a/documentation/vim.markdown
+++ b/documentation/vim.markdown
@@ -65,7 +65,7 @@ Vim is one of the most powerful text editors. It is at the same time light and h
 ##### Advanced commands
 
 * `:set invnu` toggle line numbers
-* `ctrl-x ctrl-f` autocomplete filename (when in insert mode)
+* `ctrl-x ctrl-f` auto-complete filename (when in insert mode)
 * `:%s/old/new/g` replace old by new in current document
 * `:g/pattern/d` delete all lines matching pattern
 * `:g!/pattern/d` delete all lines not matching pattern (same as `:v/pattern/d`)
diff --git a/documentation/weechat.markdown b/documentation/weechat.markdown
index 4882bfef..59f8bb6d 100644
--- a/documentation/weechat.markdown
+++ b/documentation/weechat.markdown
@@ -84,7 +84,7 @@ which you can then detach with **Ctrl+A** -> **Ctrl+D**, and re-attach later `sc
 Relay / Proxy
 -------------
 
-Weechat can act as small irc server to which other clients can connect. This allows to connect GUI and mobile clients to the same weechat backend to access all irc channels under the same username. When using this you should ensure that the relay is encrypted with an SSL certificate to avoid plaintext traffic over the internet. As this is an advanced topic we only sketch the important steps for the power users.
+Weechat can act as small irc server to which other clients can connect. This allows to connect GUI and mobile clients to the same weechat back-end to access all irc channels under the same username. When using this you should ensure that the relay is encrypted with an SSL certificate to avoid plain-text traffic over the internet. As this is an advanced topic we only sketch the important steps for the power users.
 
 The following weechat commands activate the IRC proxy
 
@@ -107,9 +107,9 @@ printf '%b' '*/relay sslcertkey\n' > /home/johndoe/.weechat/weechat_fifo_*
 
 ## Notifications
 
-This example shows how to configure separate notification rules per channel. It will set the follwoing notification settings:
+This example shows how to configure separate notification rules per channel. It will set the following notification settings:
 
-- notify about messages in all channes (global server setting)
+- notify about messages in all channels (global server setting)
 - always notify in `#important-channel`
 - never notify in `#crowded-channel`
 
@@ -121,7 +121,7 @@ This example shows how to configure separate notification rules per channel. It
 
 Possible options:
 
-Notify level | Level of messages added to hotlist
+Notify level | Level of messages added to hot-list
 ------------ | ----------------------------------
 `none`       | (none)
 `highlight`  | highlight + private
diff --git a/documentation/zoom.markdown b/documentation/zoom.markdown
index 5cf86675..4e9a0410 100644
--- a/documentation/zoom.markdown
+++ b/documentation/zoom.markdown
@@ -1,7 +1,7 @@
 Zoom Video Conferencing
 =======================
 
-ETH users have acess to the [Zoom](https://ethz.ch/services/de/it-services/katalog/multimedia/video-konferenz/zoom.html) software for virtual meetings and video conferences.
+ETH users have access to the [Zoom](https://ethz.ch/services/de/it-services/katalog/multimedia/video-konferenz/zoom.html) software for virtual meetings and video conferences.
 
 Log in on [ethz.zoom.us](https://ethz.zoom.us) using the `username@ethz.ch` address. The participants can use the web browser or [download](https://ethz.zoom.us/download) the zoom client.
 
diff --git a/linux/general_overview_over_linux_at_the_department_of_physics.markdown b/linux/general_overview_over_linux_at_the_department_of_physics.markdown
index 44e58d04..df460131 100644
--- a/linux/general_overview_over_linux_at_the_department_of_physics.markdown
+++ b/linux/general_overview_over_linux_at_the_department_of_physics.markdown
@@ -68,7 +68,7 @@ Strengths and Weaknesses of the Distribution
 Debian strengths:
 
 * fine-grained package management with good package/version dependency system supported by policy
-* upgrades (without reinstallations) go smooth over several generations of releases
+* upgrades (without re-installations) go smooth over several generations of releases
 * responsive community
 
 Debian weaknesses:
diff --git a/linux/how_to_use_usb_harddisk_or_usb_memorysticks.markdown b/linux/how_to_use_usb_harddisk_or_usb_memorysticks.markdown
index 1371e359..87a9e048 100644
--- a/linux/how_to_use_usb_harddisk_or_usb_memorysticks.markdown
+++ b/linux/how_to_use_usb_harddisk_or_usb_memorysticks.markdown
@@ -1,7 +1,7 @@
 How to use USB Harddisk or USB Memorysticks
 ===========================================
 
-On our managed D-PHYS Linux workstations you can just plug in an USB harddisk or memory stick and the system will mount the filesystem automatically.  If you pull it out again it will be automatically unmounted.  If you wrote something on the filesystem please make sure to allow the system to write all data to the device before pulling it out.  I.e., you should either wait 30 seconds or force synchronisation with the command `sync`
-If you only read from the device there is no need to synchronise before removal of the device.
+On our managed D-PHYS Linux workstations you can just plug in an USB harddisk or memory stick and the system will mount the filesystem automatically.  If you pull it out again it will be automatically unmounted.  If you wrote something on the filesystem please make sure to allow the system to write all data to the device before pulling it out.  I.e., you should either wait 30 seconds or force synchronization with the command `sync`
+If you only read from the device there is no need to synchronize before removal of the device.
 
 The device will be mounted somewhere in `/media`
diff --git a/linux/personal_groups.markdown b/linux/personal_groups.markdown
index 7fcf2af5..b3c10c9e 100644
--- a/linux/personal_groups.markdown
+++ b/linux/personal_groups.markdown
@@ -1,7 +1,7 @@
 Personal Groups
 ===============
 
-We use _personal groups_ to enable a clear-cut distinction between the user's personal files and those shared with others, for instance on a groupdrive. In practice this means that any D-Phys user's primary group (gid) has the same name as the username, while the secondary groups reflect his permissions to access ressources shared with other members of a group.
+We use _personal groups_ to enable a clear-cut distinction between the user's personal files and those shared with others, for instance on a groupshare. In practice this means that any D-Phys user's primary group (gid) has the same name as the username, while the secondary groups reflect his permissions to access resources shared with other members of a group.
 
 Unix permissions
 ----------------
diff --git a/linux/software_on_the_d-phys_linux_computers.markdown b/linux/software_on_the_d-phys_linux_computers.markdown
index a5970618..893501a3 100644
--- a/linux/software_on_the_d-phys_linux_computers.markdown
+++ b/linux/software_on_the_d-phys_linux_computers.markdown
@@ -20,8 +20,8 @@ Notes on the system configuration
 
 We also mostly have and use [zRAM](https://en.wikipedia.org/wiki/Zram), `swapon` gives you an overview about it, as well as `cat /sys/block/zram*/comp_algorithm` on the used compression. Generally it's lzo-rle since 20.04.
 
-For a long time we used to have XFS for /scratch* filesystems, around 2015, we switched to [btrfs](https://www.kernel.org/doc/html/latest/filesystems/btrfs.html) and thus can support live file system
-compression. (There was a time when btrfs did not support swapfiles). It's [ext4](https://en.wikipedia.org/wiki/Ext4) as of 2024.
+For a long time we used to have XFS for /scratch* file systems, around 2015, we switched to [btrfs](https://www.kernel.org/doc/html/latest/filesystems/btrfs.html) and thus can support live file system
+compression. (There was a time when btrfs did not support swap files). It's [ext4](https://en.wikipedia.org/wiki/Ext4) as of 2024.
 
 [exfat](https://github.com/exfatprogs/exfatprogs) support has been switched to the Samsung implementation for 20.04.
 
@@ -150,7 +150,7 @@ Plotting Software
 Graphics Tools
 --------------
 
-* [The GIMP](https://gimp.org/tutorials/): tool to create and manipulate pixel oriented graphics files (e.g., JPEG, PNG, PPM, etc.), useful for working with photos, web graphics and more.  Similar uses as Adobe PhotoShop
+* [The GIMP](https://gimp.org/tutorials/): tool to create and manipulate pixel oriented graphics files (e.g., JPEG, PNG, PPM, etc.), useful for working with photos, web graphics and more.  Similar uses as Adobe Photoshop
 * [inkscape](https://inkscape.org/): Vector drawing software.
 * [Scribus](https://www.scribus.net/): WYSIWYG desktop publishing
 * xmgr, grace: an XY plotting tool
@@ -273,13 +273,13 @@ PF machines have
 
 * `rload | grep pf-pc`
 
-GUENTHER cluster also has
+The guenther cluster also has
 
 * `rload | grep guenther`
 * `pestat`
-* [SLURM](https://scicomp.ethz.ch/wiki/Using_the_batch_system) batch queueing system
+* [SLURM](https://scicomp.ethz.ch/wiki/Using_the_batch_system) batch queuing system
 
-You can use `nice` to run jobs niced, or `cpulimit -l 50 -- yourjob` to limit cpu usage on your job to 50 %.
+You can use `nice` to run jobs reniced, or `cpulimit -l 50 -- yourjob` to limit cpu usage on your job to 50 %.
 
 Debugging
 ---------
diff --git a/linux/using_your_cd_writer_under_linux.markdown b/linux/using_your_cd_writer_under_linux.markdown
index 0d21c142..abad0cb5 100644
--- a/linux/using_your_cd_writer_under_linux.markdown
+++ b/linux/using_your_cd_writer_under_linux.markdown
@@ -48,7 +48,7 @@ Read the man page for `cdrecord` for more options and examples.
 
 ##### Section 3: Making ISO images
 
-You may want to generate a CD image containing data. You can do this with the comand `mkisofs`.
+You may want to generate a CD image containing data. You can do this with the command `mkisofs`.
 
 ```
 mkisofs  -r   -o  cdimage.iso  private_collection/
@@ -59,7 +59,7 @@ mkisofs  -r   -o  cdimage.iso  private_collection/
 
 You can then use `cdrecord` to write cdimage.iso to a CD.
 
-More information The [CD-Writing Howto](http://www.ibiblio.org/pub/Linux/docs/HOWTO/CD-Writing-HOWTO) is a good place to find more information about writing CDs under linux.
+More information The [CD-Writing How-to](http://www.ibiblio.org/pub/Linux/docs/HOWTO/CD-Writing-HOWTO) is a good place to find more information about writing CDs under linux.
 
 ##### Section 4: Reading a CD image
 
@@ -77,7 +77,7 @@ dd if=/dev/cdrom of=cdimage.iso bs=2048 count=<volume-size>
 
 ##### Section 5: Tips and Tricks
 
-If you want to make sure that your CDs can be read on all possible CD drives it is recommended that you **pad** your CDs.  This goes for makeing the CD with `mkisofs` and burning them with `cdrecord`.  Just add the option `-pad` to both commands.  It will take up a bit more space on the CD but then any CD drive should read the very same bytes.
+If you want to make sure that your CDs can be read on all possible CD drives it is recommended that you **pad** your CDs.  This goes for making the CD with `mkisofs` and burning them with `cdrecord`.  Just add the option `-pad` to both commands.  It will take up a bit more space on the CD but then any CD drive should read the very same bytes.
 
 You can find out a lot of information about the CD drive and the media you are burning on by issuing the command`
 
diff --git a/linux/vpn_with_linux.markdown b/linux/vpn_with_linux.markdown
index 34a6a815..d5b9bd15 100644
--- a/linux/vpn_with_linux.markdown
+++ b/linux/vpn_with_linux.markdown
@@ -1,7 +1,7 @@
 VPN with Linux
 ==============
 
-The central Informatikdienste [recommend](https://unlimited.ethz.ch/display/itkb/VPN) to use the Cisco Secure Client (formerly known as Cisco AnyConnect), but you can also use the native, opensource tools.
+The central Informatikdienste [recommend](https://unlimited.ethz.ch/display/itkb/VPN) to use the Cisco Secure Client (formerly known as Cisco AnyConnect), but you can also use the native, open-source tools.
 
 ### Using the command line
 
diff --git a/mail/how_to_use_email_with_mutt_imap.markdown b/mail/how_to_use_email_with_mutt_imap.markdown
index 9dedad0c..47ee72e2 100644
--- a/mail/how_to_use_email_with_mutt_imap.markdown
+++ b/mail/how_to_use_email_with_mutt_imap.markdown
@@ -20,7 +20,7 @@ set folder="imaps://$USER@imap.phys.ethz.ch"
 set spoolfile="imaps://$USER@imap.phys.ethz.ch/INBOX"
 ```
 
-You need to replace `$USER` by a hardcoded value representing your D-PHYS username.
+You need to replace `$USER` by a hard-coded value representing your D-PHYS username.
 
 #### Optimizing your mutt configuration
 
diff --git a/mail/how_to_use_email_with_outlook.markdown b/mail/how_to_use_email_with_outlook.markdown
index 9020823a..c49de11f 100644
--- a/mail/how_to_use_email_with_outlook.markdown
+++ b/mail/how_to_use_email_with_outlook.markdown
@@ -18,7 +18,7 @@ Under **E-mail Accounts** can you add an Mail account.
 
 [[!img /media/how_to_use_email_with_outlook/mail7.png size="450x"]]
 
-This will be configured only by entering your First- and Lastname (Displayname), D-PHYS E-mail Address and Password. Outlook checks automatically for the correct servernames and encryption settings.
+This will be configured only by entering your First- and Lastname (Displayname), D-PHYS E-mail Address and Password. Outlook checks automatically for the correct server names and encryption settings.
 
 [[!img /media/how_to_use_email_with_outlook/mail3.png size="450x"]]
 
diff --git a/mail/how_to_use_email_with_outlook_on_mac.markdown b/mail/how_to_use_email_with_outlook_on_mac.markdown
index e729f324..e8191b32 100644
--- a/mail/how_to_use_email_with_outlook_on_mac.markdown
+++ b/mail/how_to_use_email_with_outlook_on_mac.markdown
@@ -13,7 +13,7 @@ We strongly recommend our users to stick to the "Old Outlook" for the time being
 Do not use "Sync with Microsoft Cloud"
 --------------------------------------
 
-Together with the "New Outlook" interface, Microsoft is prompting users to sync their messages and contacts to the Microsoft Cloud. When enabled, what happens under the hood is a privacy nightmare forbidden by ETH usage policy. In particular the emails (for instance of your D-PHYS account) will not longer be fetched with IMAP by your computer, but directly from hosts in the "Microsoft Cloud" - using your personal username and password. So Microsoft will have access to your cleartext password and all your emails.
+Together with the "New Outlook" interface, Microsoft is prompting users to sync their messages and contacts to the Microsoft Cloud. When enabled, what happens under the hood is a privacy nightmare forbidden by ETH usage policy. In particular the emails (for instance of your D-PHYS account) will not longer be fetched with IMAP by your computer, but directly from hosts in the "Microsoft Cloud" - using your personal username and password. So Microsoft will have access to your clear-text password and all your emails.
 
 When adding new accounts, always uncheck "Sync with Microsoft Cloud". And whenever prompted to enhance the experience with "Microsoft Cloud" click "Sync directly with IMAP" instead. (Beware that the cloud sync can not be disabled for some other email providers, like Gmail. So when you add your Google account to Outlook on Mac, all your Gmail data will be synced to the Microsoft cloud.)
 
diff --git a/mail/how_to_use_email_with_thunderbird.markdown b/mail/how_to_use_email_with_thunderbird.markdown
index 6a174c71..618d7d74 100644
--- a/mail/how_to_use_email_with_thunderbird.markdown
+++ b/mail/how_to_use_email_with_thunderbird.markdown
@@ -5,7 +5,7 @@ How to Use Email with Thunderbird
 Automatic configuration
 -----------------------
 
-If you start Thunderbird for the first time, it will be automatically configured  only with entering your D-PHYS username and emailadress. Thunderbird will check for the correct servernames and encryption.
+If you start Thunderbird for the first time, it will be automatically configured  only with entering your D-PHYS username and emailadress. Thunderbird will check for the correct server names and encryption.
 
 [[!img /media/how_to_use_email_with_thunderbird/tb2.png size="450x"]]
 
diff --git a/mail/outlook-problems.markdown b/mail/outlook-problems.markdown
index f2109f8d..dcda27c8 100644
--- a/mail/outlook-problems.markdown
+++ b/mail/outlook-problems.markdown
@@ -60,7 +60,7 @@ In Outlook go to the settings in **File** > **Options** > **Mail** and change th
 
 [[!img /media/windows/outlook/outlook_disable_rtf_2.png size="450x"]]
 
-The preferred setting should be `plain text` because email is only standardised for plain text.
+The preferred setting should be `plain text` because email is only standardized for plain text.
 HTML formatting may look different in every client because it is not standardized.
 Rich text format (RTF) is Outlook specific and should never be used.
 
-- 
GitLab