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

---
 chat/element/addmembers.markdown              |  4 ++--
 chat/element/e2ee.markdown                    |  2 +-
 chat/element/index.markdown                   | 24 +++++++++----------
 chat/element/spaces.markdown                  |  2 +-
 chat/matrix/api.markdown                      |  6 ++---
 chat/matrix/bots.markdown                     | 10 ++++----
 chat/matrix/bridges.markdown                  | 12 +++++-----
 chat/matrix/index.markdown                    | 10 ++++----
 chat/matrix/why.markdown                      |  2 +-
 index.markdown                                |  2 +-
 linux/workstation/debian.markdown             | 10 ++++----
 linux/workstation/firefox_profile.markdown    |  2 +-
 linux/workstation/nodejs.markdown             |  2 +-
 linux/workstation/nvidia_cuda.markdown        |  6 ++---
 linux/workstation/resource_control.markdown   | 10 ++++----
 linux/workstation/user_privileges.markdown    |  4 ++--
 mail/mailman/index.markdown                   |  2 +-
 mail/mailman/moderation.markdown              |  2 +-
 ...ange_display_or_keyboard_language.markdown |  4 ++--
 windows/windows10/edit_lockscreen.markdown    |  2 +-
 20 files changed, 59 insertions(+), 59 deletions(-)

diff --git a/chat/element/addmembers.markdown b/chat/element/addmembers.markdown
index 78ba9e78..61e1d618 100644
--- a/chat/element/addmembers.markdown
+++ b/chat/element/addmembers.markdown
@@ -14,13 +14,13 @@ If you want to invite a large number of users into rooms or a space, the fastest
 
 You can then copy paste that list into the invite field.
 
-If you want to generate such a Matrix ID userlist based on an LDAP group (groupshare), you can use the following command on any D-PHYS managed Linux workstation (for example `login.phys.ethz.ch`):
+If you want to generate such a Matrix ID user list based on an LDAP group (groupshare), you can use the following command on any D-PHYS managed Linux workstation (for example `login.phys.ethz.ch`):
 
 ```bash
 members <groupname> | sed "s,\ ,\n,g" | awk '{print "@" $1 ":phys.ethz.ch"}'
 ```
 
-Juste replace `groupname` with the LDAP group
+Just replace `groupname` with the LDAP group
 
 How to generate a member list from an existing room
 ---------------------------------------------------
diff --git a/chat/element/e2ee.markdown b/chat/element/e2ee.markdown
index 7f69eef2..aba2c79f 100644
--- a/chat/element/e2ee.markdown
+++ b/chat/element/e2ee.markdown
@@ -127,7 +127,7 @@ See also [[How to verify a device via QR-Code|/chat/element/android/#verifying-t
 Using end-to-end encryption
 ---------------------------
 
-End-to-end ecryption (e2ee) is enabled by default for new direct messages (DMs) and suggested (by default on) for new group conversations (rooms).
+End-to-end encryption (e2ee) is enabled by default for new direct messages (DMs) and suggested (by default on) for new group conversations (rooms).
 Encryption on existing DMs or rooms will not be enabled automatically. To enable it go to **Room Settings** > **Security & Privacy** > **Encryption** and enable **Encryption**:
 
 [[!img /media/chat/riot_e2ee_encrypt1.png size="450x"]]
diff --git a/chat/element/index.markdown b/chat/element/index.markdown
index 8f9215e4..47abab35 100644
--- a/chat/element/index.markdown
+++ b/chat/element/index.markdown
@@ -3,14 +3,14 @@ Element
 
 While there are many [clients](https://matrix.org/clients/) available free to use to connect to our Matrix homeserver,
 we recommend to use the flagship app [Element](https://element.io/) which has the most [features](https://element.io/features).
-Please read on below to get startet connecting with Element or refer to the official [help](https://element.io/help).
+Please read on below to get started connecting with Element or refer to the official [help](https://element.io/help).
 
 [[!img media/chat/element_full_example.png size="450x"]]
 
 First steps
 -----------
 
-- Customise your [[notification|/chat/element#notifications]] levels across the app and per room
+- Customize your [[notification|/chat/element#notifications]] levels across the app and per room
 - Reduce the notification level of chatty rooms like the Helpdesk to 'Mentions & Keywords'.
 - Keep level 'Use default' for the News and Status room, where only moderators are allowed to send messages.
 - Explore more public rooms in the [public room directory](https://element.phys.ethz.ch/#/directory) via the 'Explore rooms' button next to the search field.
@@ -47,12 +47,12 @@ Documentation
 Notifications
 -------------
 
-Element has intelligent notifications. Customise notifications to suit your priorities.
+Element has intelligent notifications. Customize notifications to suit your priorities.
 Receive notifications whenever anyone mentions your name, and define keywords to trigger if you're following a specific topic.
 
-Element allows you to customise your notifications at two levels: across the app and per room.
+Element allows you to customize your notifications at two levels: across the app and per room.
 You can configure how you will be notified for given events by default in the Notifications section of your Settings
-(accessible from the drop down menu next to your name in the top left cornerof the web/desktop app).
+(accessible from the drop down menu next to your name in the top left corner of the web/desktop app).
 
 The per room notification settings can be:
 
@@ -65,8 +65,8 @@ The per room notification settings can be:
 
 ### How to mention someone
 
-If you have an important message for someone or simply whant them to know that your message in a room is for them, you can mention them by name.
-Just start typing their name and use tab-comletion or alternatively start typing the `@` symbol, followed by their name and select the corresponding user.
+If you have an important message for someone or simply want them to know that your message in a room is for them, you can mention them by name.
+Just start typing their name and use tab-completion or alternatively start typing the `@` symbol, followed by their name and select the corresponding user.
 The special `@room` notification target can by used by room moderators to send a notification to all members.
 
 Keyboard shortcuts
@@ -88,7 +88,7 @@ To send emojis in Element (Web, Desktop), type a colon `:` followed by the name
 :thumbsup:
 ```
 
-Hint: If you hover over a message in a room, choose **React** (smilie icon), which will present an emoji keyboard with their names.
+Hint: If you hover over a message in a room, choose **React** (smiley icon), which will present an emoji keyboard with their names.
 
 Text formatting (Markdown)
 --------------------------
@@ -127,7 +127,7 @@ In encrypted rooms newly joined users cannot decrypt past messages.
 
 ### Roles & Permissions
 
-Every action in a room (like sending messages or inviting users) requires a permission level. Permission levels are represented by a number between `0-100`. By default 3 named roles are defined with the follwoing permission levels:
+Every action in a room (like sending messages or inviting users) requires a permission level. Permission levels are represented by a number between `0-100`. By default 3 named roles are defined with the following permission levels:
 
 - Default: `0`
 - Moderator: `50`
@@ -156,12 +156,12 @@ To make it easier to share the room with others or link to it on a website, we c
 #group-roomalias:phys.ethz.ch
 ```
 
-Create an alias in **Room Settings** > **General** > **Local Adresses**:
+Create an alias in **Room Settings** > **General** > **Local Addresses**:
 
 [[!img /media/chat/riot_room_alias_create.png size="450x"]]
 
 To make the room discoverable we can publish it in the public room directory.
-Go to **Published Adresses**, select your new address as the **Main address** and publish it:
+Go to **Published Addresses**, select your new address as the **Main address** and publish it:
 
 [[!img /media/chat/riot_room_alias_publish.png size="450x"]]
 
@@ -173,6 +173,6 @@ Since rooms are decentralized, this is not entirely possible. However, you can s
 
 - Make the room private (invite only)
 - Unpublish the room (if it was published)
-- Remove all local addesses (aliases)
+- Remove all local addresses (aliases)
 - Kick all users or ask them nicely to leave
 - Leave the room
diff --git a/chat/element/spaces.markdown b/chat/element/spaces.markdown
index 80854e4d..210d086d 100644
--- a/chat/element/spaces.markdown
+++ b/chat/element/spaces.markdown
@@ -5,7 +5,7 @@ Read more in the [Spaces blast out of beta](https://element.io/blog/spaces-blast
 
 [[!img /media/chat/element_spaces1.png alt="Element spaces" size="300x"]]
 
-Forming hierachies of spaces as shown above is still in beta test with some features missing.
+Forming hierarchies of spaces as shown above is still in beta test with some features missing.
 We recommend sticking with top-level spaces for now.
 
 Read more about [[spaces|/chat/matrix#spaces]].
diff --git a/chat/matrix/api.markdown b/chat/matrix/api.markdown
index 9c55b7e2..44953733 100644
--- a/chat/matrix/api.markdown
+++ b/chat/matrix/api.markdown
@@ -3,7 +3,7 @@ How to use the Matrix API
 
 You can use the Matrix [Client-Server API](https://matrix.org/docs/spec/client_server/latest) to send messages, control rooms or anything else. It uses standard HTTP + JSON objects.
 
-To get started you need an access token. The simplest way to get that is to open Element in a private (incognito) window in your webbrowser or just use your currently open Element.
+To get started you need an access token. The simplest way to get that is to open Element in a private (incognito) window in your web browser or just use your currently open Element.
 Go to **Settings** > **Help & About** > **Advanced** > **Access Token `<click to reveal>`** and copy your access token:
 
 [[!img /media/chat/matrix_access_token.png size="450x"]]
@@ -51,7 +51,7 @@ or a media upload:
 http POST 'https://matrix.phys.ethz.ch/_matrix/media/r0/upload?filename=morpheus.png' Authorization:"Bearer ${token}" Content-Type:"image/png" < Pictures/avatars/morpheus.png
 ```
 
-or to post json data:
+or to post JSON data:
 
 ```bash
 http POST 'https://matrix.phys.ethz.ch/_matrix/client/r0/rooms/!ZkngAyfszzfCqwNZUd:phys.ethz.ch/invite' Authorization:"Bearer ${token}" <<<'{"user_id":"@rda:phys.ethz.ch"}'
@@ -78,7 +78,7 @@ data = {
 r = requests.post(url, json=data, headers=headers)
 ```
 
-where `format` and `formatted_body` can be omitted to send plaintext only messages.
+where `format` and `formatted_body` can be omitted to send plain-text only messages.
 
 Get a list of room members
 --------------------------
diff --git a/chat/matrix/bots.markdown b/chat/matrix/bots.markdown
index eee05005..53c47fd5 100644
--- a/chat/matrix/bots.markdown
+++ b/chat/matrix/bots.markdown
@@ -12,7 +12,7 @@ It is probably a bad idea anyway to include a bot in your encrypted conversation
 
 ## Maubot
 
-Most of them are documented on the [maubot github page](https://github.com/maubot/maubot)
+Most of them are documented on the [maubot GitHub page](https://github.com/maubot/maubot)
 or on [t2bot.io](https://t2bot.io/) (a public integration network for Matrix).
 
 
@@ -83,10 +83,10 @@ For details see:
 - `!lunch help`
 
 
-## Arxiv
+## arXiv
 
 A [maubot](https://github.com/maubot/maubot) plugin that gives arXiv summaries
-([ETH gitlab](https://gitlab.ethz.ch/iyanmv/arxivbot), [github](https://github.com/iyanmv/arxivbot)).
+([ETH gitlab](https://gitlab.ethz.ch/iyanmv/arxivbot), [GitHub](https://github.com/iyanmv/arxivbot)).
 
 - Invite [arxiv](https://m.ethz.ch/#/@arxiv:phys.ethz.ch) (`@arxiv:phys.ethz.ch`) to your room
 - Paste URLs of arXiv abstracts (https://arxiv.org/abs/XXX) to your room
@@ -105,8 +105,8 @@ This requires an [[integration manager|/chat/element/integrations]] which suppor
 - Invite [stickers](https://m.ethz.ch/#/@stickers:mbot.ethz.ch) (`@stickers:mbot.ethz.ch`) to a private chat.
 - Say `!stickers newpack` and follow the directions.
 - Open the [[integration manager|/chat/element/integrations]]  and edit your sticker packs.
-- Paste the URL the bot gave you into the "Add Sitcker Packs" box.
-- Click "Add Stickerpack"
+- Paste the URL the bot gave you into the "Add Sticker Packs" box.
+- Click "Add Sticker pack"
 
 ## Emailbot
 
diff --git a/chat/matrix/bridges.markdown b/chat/matrix/bridges.markdown
index 8ad03667..a7ccd27d 100644
--- a/chat/matrix/bridges.markdown
+++ b/chat/matrix/bridges.markdown
@@ -6,7 +6,7 @@ New bridges and updates will be posted in this room.
 
 ## Hookshot
 
-The source code for the bridge is available at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) on Github.
+The source code for the bridge is available at [matrix-hookshot](https://github.com/matrix-org/matrix-hookshot) on GitHub.
 Currently enabled features:
 
 - Webhooks (inbound, outbound)
@@ -19,7 +19,7 @@ For a list of commands see the help:
 
 ### Inbound webhooks
 
-This section covers inbound webhhoks.
+This section covers inbound webhooks.
 
 Base URL: `https://hookshot.mbot.ethz.ch/webhook/<hook>`
 
@@ -32,7 +32,7 @@ The bridge accepts POST or PUT requests. See [docs](https://matrix-org.github.io
 
 #### Example usage
 
-Example json payloads:
+Example JSON payloads:
 
 ```json
 {"text":"Hello world!"}
@@ -60,7 +60,7 @@ In the room where webhooks were configured (not admin room):
 - List webhooks: `!hookshot webhook list`
 - Remove webhook: `!hookshot webhook remove <name>`
 
-### Outbound webhhoks
+### Outbound webhooks
 
 **Experimental, deleting outbound hooks is not implemented. Use it wisely!**
 
@@ -72,7 +72,7 @@ In the room where webhooks were configured (not admin room):
 
 Base URL: `https://webhooks.mbot.ethz.ch/webhook/<api>/<hook>`
 
-This API translates incoming webhooks into generic webhooks (hookshot). The source code is available on [ETH Gitlab](https://gitlab.ethz.ch/isgphys/webhook-to-matrix-hookshot) or on [Github](https://github.com/rda0/webhook-to-matrix-hookshot).
+This API translates incoming webhooks into generic webhooks (hookshot). The source code is available on [ETH Gitlab](https://gitlab.ethz.ch/isgphys/webhook-to-matrix-hookshot) or on [GitHub](https://github.com/rda0/webhook-to-matrix-hookshot).
 
 1. Create a generic webhook using hookshot (see above)
 2. Use the `<hook>` URL part from hookshot with the base URLs listed below
@@ -110,7 +110,7 @@ Base URL: `https://webhooks.mbot.ethz.ch/webhook/slack/<hook>`
 
 A bouncer-style Matrix IRC bridge. Can be used as an alternative to existing bridges using [matrix-appservice-irc](https://github.com/matrix-org/matrix-appservice-irc) which already bridge many [IRC networks](https://matrix-org.github.io/matrix-appservice-irc/latest/bridged_networks.html) to Matrix.
 
-The source code is available at [hifi/heisenbridge](https://github.com/hifi/heisenbridge) on Github.
+The source code is available at [hifi/heisenbridge](https://github.com/hifi/heisenbridge) on GitHub.
 
 1. Start a DM with [heisenbridge](https://m.ethz.ch/#/@heisenbridge:mbot.ethz.ch) (`@heisenbridge:mbot.ethz.ch`)
 2. Type `help` or `<command> -h` to get started
diff --git a/chat/matrix/index.markdown b/chat/matrix/index.markdown
index 701387fa..cb816c8d 100644
--- a/chat/matrix/index.markdown
+++ b/chat/matrix/index.markdown
@@ -1,13 +1,13 @@
 Matrix
 ======
 
-**Matrix** is an **open standard** for interoperable, decentralised, real-time communication over IP. It can be used to power Instant Messaging, VoIP/WebRTC signalling, Internet of Things communication - or anywhere you need a [standard HTTP API](https://matrix.org/docs/spec/client_server/latest) for publishing and subscribing to data whilst tracking the conversation history.
+**Matrix** is an **open standard** for interoperable, decentralized, real-time communication over IP. It can be used to power Instant Messaging, VoIP/WebRTC signaling, Internet of Things communication - or anywhere you need a [standard HTTP API](https://matrix.org/docs/spec/client_server/latest) for publishing and subscribing to data whilst tracking the conversation history.
 
 Matrix defines [the standard](https://matrix.org/docs/spec), and provides [open source](https://github.com/matrix-org) reference implementations of Matrix-compatible Servers, [Client SDKs](https://matrix.org/sdks/) and [Application Services](https://matrix.org/docs/guides/application-services) to help you create new communication solutions or [extend the capabilities](https://matrix.org/bots/) and [reach of existing ones](https://matrix.org/bridges/).
 
 [[!img /media/chat/bridges.png size="450x"]]
 
-Want to know who is behind it and why they create such a useful project for the public for free? Read on in the offical [matrix.org FAQ](https://matrix.org/faq).
+Want to know who is behind it and why they create such a useful project for the public for free? Read on in the official [matrix.org FAQ](https://matrix.org/faq).
 
 Documentation
 -------------
@@ -34,7 +34,7 @@ Terms
 
 A few important [terms](https://matrix.org/faq/#definitions) to know are:
 
-- **homeserver**: Each account in the Matrix federation is associated with a single homeserver. The software running at this server stores the history and account information for that user. Homeservers synchronise message history with other homeservers.
+- **homeserver**: Each account in the Matrix federation is associated with a single homeserver. The software running at this server stores the history and account information for that user. Homeservers synchronize message history with other homeservers.
 - **federation**: Federation means that separate instances of a service communicate - the best example of this is email servers, in which it's possible to send mail between difference service providers. For Matrix, this means that data about rooms and message history is shared between servers of participating users.
 - **Element**: Element is a popular matrix client developed by the core matrix.org team.
 - **MXID**: Matrix user IDs (MXID) are unique user IDs. They are in the format `@username:phys.ethz.ch`.
@@ -97,7 +97,7 @@ Each room can also have multiple **Room Aliases**, which look like:
 #room_alias:domain
 ```
 
-A room alias "points" to a room ID and is the human-readable label by which rooms are publicised and discovered.
+A room alias "points" to a room ID and is the human-readable label by which rooms are publicized and discovered.
 
 Spaces
 ------
@@ -106,7 +106,7 @@ Spaces are a new feature in Matrix to group rooms.
 Under the hood spaces are rooms with a special type `m.space` to distinguish them from regular messaging rooms.
 This means spaces (unlike the old communities) are fully decentralized like rooms.
 
-Spaces can contain rooms and members. Since spaces are just rooms, spaces can also contain subspaces.
+Spaces can contain rooms and members. Since spaces are just rooms, spaces can also contain sub-spaces.
 This allows to organize rooms in a tree structure.
 
 The details are outlined in [MSC1772](https://github.com/matrix-org/matrix-doc/pull/1772).
diff --git a/chat/matrix/why.markdown b/chat/matrix/why.markdown
index d2980301..d7596856 100644
--- a/chat/matrix/why.markdown
+++ b/chat/matrix/why.markdown
@@ -19,7 +19,7 @@ There are many services and programs for instant electronic communication. Matri
 - Active further development
 - Up-and-coming use by other scientific institutions (e.g. lots of German universities)
 
-Further informationen: https://matrix.org/docs/chat_basics/
+Further information: https://matrix.org/docs/chat_basics/
 
 Detailed explanation of technical terms: https://matrix.org/docs/older/faq/#definitions
 
diff --git a/index.markdown b/index.markdown
index 8c659e19..17f4295b 100644
--- a/index.markdown
+++ b/index.markdown
@@ -1,7 +1,7 @@
 D-PHYS IT Documentation
 =======================
 
-Use the subnavigation on the side to navigate by topic, or the links below for different target audiences and frequently asked questions. A search box can be found on the bottom of the page.
+Use the sub-navigation on the side to navigate by topic, or the links below for different target audiences and frequently asked questions. A search box can be found on the bottom of the page.
 
 ### I'm a
 
diff --git a/linux/workstation/debian.markdown b/linux/workstation/debian.markdown
index c574b433..9bf28b28 100644
--- a/linux/workstation/debian.markdown
+++ b/linux/workstation/debian.markdown
@@ -32,7 +32,7 @@ Some old or underdimensioned hardware might not be compatible with the new OS/se
 You may want to replace the affected hardware. Please order replacements in time for the migration.
 This affects the following hardware components:
 
-- **Legacy Nvidia cards** requiring `470` or `390` legacy drivers, see changes: **Nvidia**
+- **Legacy NVidia cards** requiring `470` or `390` legacy drivers, see changes: **NVidia**
 - **System disks** <256GiB will result in no `/scratch` space (1GiB only), see changes: **System disk**, **Scratch**
 
 ### Preparation steps for users
@@ -52,7 +52,7 @@ The migration includes the following notable (breaking) changes to be aware of:
   which is used for future announcements and support. Important announcements will be sent with `@room` ping,
   so for best experience set the room notification level to `Mentions & keywords` to reduce noise.
 - **Ansible**: 100% reproducible automated installation and setup
-- **Installer**: custom debian installer component which allows fast reinstallation (~15min downtime with SSD).
+- **Installer**: custom debian installer component which allows fast re-installation (~15min downtime with SSD).
   This and our new LVM setup allows us to keep the local data (`/scratch*`) and just wipe the OS parts in the future.
   Due to size and filesystem changes **the whole system disk needs to be wiped during the initial migration to debian**
 - **System disk**: we require a minimum 256GiB (SSD) as the system disk for new workstations
@@ -71,16 +71,16 @@ The migration includes the following notable (breaking) changes to be aware of:
   In addition we opted for a single Python installation shared across all workstations, with a variety of
   packages pre-installed. Note that you must activate the Python in your shell in order to use it, so please
   have a look at our detailed [[Python]] readme.
-- **Firefox**: Due to the switch from Ubuntu to Debian all Firefox profiles need to be migrated once. This is a manual process and ideally happens during the workstation reinstallation. We will assist in the process. Read [[firefox_profile]] for instructions on how to migrate your profile in order to preserve your history and settings if you'd like to give it a go yourself.
+- **Firefox**: Due to the switch from Ubuntu to Debian all Firefox profiles need to be migrated once. This is a manual process and ideally happens during the workstation re-installation. We will assist in the process. Read [[firefox_profile]] for instructions on how to migrate your profile in order to preserve your history and settings if you'd like to give it a go yourself.
   By default only Firefox ESR (Extended Support Release) is installed now.
   Previously (with Ubuntu) there were two versions of Firefox installed (ESR and Rapid Release).
-- **NFS**: Local filesystems (such as `/scratch`) will no longer be exported via NFS by default, due to the lack
+- **NFS**: Local file systems (such as `/scratch`) will no longer be exported via NFS by default, due to the lack
   of access restrictions for NFS exports (all D-PHYS users may write to it from anywhere).
   This is only available on request by the hardware/storage-device owner, if they agree with the limitations.
 - **Nvidia**: the latest version `5xx` (`550+`) driver is the only official installable driver for Debian 12 bookworm.
   Support for older GPUs (about 10 years, requiring `470` or `390` legacy drivers) was dropped by Nvidia for Debian 12.
   If your nvidia GPU does not support the latest driver version, we will install the Debian packaged `470` Tesla driver
-  for supported GPUs and for everything older we will install the opensource `nouveau` driver,
+  for supported GPUs and for everything older we will install the open-source `nouveau` driver,
   which may lead to degraded performance or instability. To avoid that, a GPU upgrade is required.
   Refer to the list of supported GPUs on the [nvidia unix drivers](https://www.nvidia.com/en-us/drivers/unix/)
   page and navigate to: Latest Production Branch Version: `5xx.xx.xx` > Supported Products.
diff --git a/linux/workstation/firefox_profile.markdown b/linux/workstation/firefox_profile.markdown
index 56db7fef..f13f0966 100644
--- a/linux/workstation/firefox_profile.markdown
+++ b/linux/workstation/firefox_profile.markdown
@@ -1,7 +1,7 @@
 Firefox profile
 ===============
 
-Due to the switch from Ubuntu to Debian all Firefox profiles need to be migrated once. This is a manual process and ideally happens during the workstation reinstallation. We will assist in the process. Read this page for instructions on how to migrate your profile in order to preserve your history and settings if you'd like to give it a go yourself.
+Due to the switch from Ubuntu to Debian all Firefox profiles need to be migrated once. This is a manual process and ideally happens during the workstation re-installation. We will assist in the process. Read this page for instructions on how to migrate your profile in order to preserve your history and settings if you'd like to give it a go yourself.
 
 By default only Firefox ESR (Extended Support Release) is installed now.
 Previously (with Ubuntu) there were two versions of Firefox installed:
diff --git a/linux/workstation/nodejs.markdown b/linux/workstation/nodejs.markdown
index 154cf83a..76da83ca 100644
--- a/linux/workstation/nodejs.markdown
+++ b/linux/workstation/nodejs.markdown
@@ -7,7 +7,7 @@ Installation
 ------------
 
 You can install `node`, `npm` and `yarn` as user on any linux workstation.
-Get the current stable [node version](https://nodejs.org/en) and install a prebuilt release using `nodeenv`:
+Get the current stable [node version](https://nodejs.org/en) and install a pre-built release using `nodeenv`:
 
 ```sh
 mkdir -p "/scratch/${USER}"
diff --git a/linux/workstation/nvidia_cuda.markdown b/linux/workstation/nvidia_cuda.markdown
index 1f35092c..64399540 100644
--- a/linux/workstation/nvidia_cuda.markdown
+++ b/linux/workstation/nvidia_cuda.markdown
@@ -31,7 +31,7 @@ A driver update always requires a reboot, which will be announced in the Matrix
 [#linux:phys.ethz.ch](https://m.ethz.ch/#/#linux:phys.ethz.ch) some days in advance.
 Note that security updates may require an immediate reboot without time for announcements in advance.
 
-Refer to the [data center driver lifecycle](https://docs.nvidia.com/datacenter/tesla/drivers/index.html#lifecycle)
+Refer to the [data center driver life-cycle](https://docs.nvidia.com/datacenter/tesla/drivers/index.html#lifecycle)
 for details.
 
 
@@ -39,7 +39,7 @@ for details.
 
 Support for older GPUs (about 10 years, requiring `470` or `390` legacy drivers) was dropped by Nvidia for Debian 12.
 If your Nvidia GPU does not support the latest driver version, we will install the Debian packaged `470` Tesla driver
-for supported GPUs and for everything older we will install the opensource `nouveau` driver,
+for supported GPUs and for everything older we will install the open-source `nouveau` driver,
 which may lead to degraded performance or instability. To avoid that a GPU upgrade is required.
 
 Please refer to the list of supported GPUs on the [Nvidia unix drivers](https://www.nvidia.com/en-us/drivers/unix/)
@@ -93,7 +93,7 @@ CUDA version compatibility
 --------------------------
 
 There is currently only a selection of a few CUDA library versions inside `/opt/software/cuda/`,
-which should be enough for most usecases due to CUDA backwards compatibility.
+which should be enough for most use-cases due to CUDA backwards compatibility.
 
 `X.Y` CUDA version are binary backwards compatible but source compatibility might be broken.
 We encourage you to keep your sources up to date with recent CUDA changes, but we are also ready to install other
diff --git a/linux/workstation/resource_control.markdown b/linux/workstation/resource_control.markdown
index b903008f..12e818bb 100644
--- a/linux/workstation/resource_control.markdown
+++ b/linux/workstation/resource_control.markdown
@@ -239,7 +239,7 @@ getfattr: Removing leading '/' from absolute path names
 user.delegate="1"
 ```
 
-Refer to https://systemd.io/CGROUP_DELEGATION/ for details (TLDR: better don't touch it).
+Refer to https://systemd.io/CGROUP_DELEGATION/ for details (TL'DR: better don't touch it).
 
 ### Locating the cgroup a process belongs to
 
@@ -427,7 +427,7 @@ The service is automatically started when you log in, see `systemctl --user stat
 It will show a notification on your desktop when a certain resource pressure limit was reached,
 and produce a log entry in your journal (`journalctl --user`).
 
-For custom or default configuration settings refer to the [github page](https://github.com/cdown/psi-notify#config).
+For custom or default configuration settings refer to the [GitHub page](https://github.com/cdown/psi-notify#config).
 
 
 ### psitop
@@ -436,7 +436,7 @@ For custom or default configuration settings refer to the [github page](https://
 Allows you to see resource contention for CPU, IO and memory separately, with high-resolution 10 second load averages.
 Use the keybindings shown in the interface.
 
-See also [github page](https://github.com/jamespwilliams/psitop).
+See also [GitHub page](https://github.com/jamespwilliams/psitop).
 
 
 Memory types
@@ -444,7 +444,7 @@ Memory types
 
 There are different kinds of memory in Linux. Some of them and their corresponding color in `htop` are:
 
-- anonymous pages (green): unreclaimable, not backed by a backing store
+- anonymous pages (green): irreclaimable, not backed by a backing store
 - page cache (yellow): maybe reclaimable, (file cache and code pages)
 - other memory (blue/purple): buffers, shared, socket, kernel slab, stack
 
@@ -455,7 +455,7 @@ explanation of terms like page cache, anonymous pages or reclaim.
 Swap
 ----
 
-Swap provides a backing store for otherwise unreclaimable memory (anonymous pages). This usually is memory allocated
+Swap provides a backing store for otherwise irreclaimable memory (anonymous pages). This usually is memory allocated
 using `malloc` or `mmap MAP_ANONYMOUS`, where the only copy of the data resides in memory (it is locked in memory).
 Swap allows the Kernel to reclaim those kinds of pages. Under memory pressure the Kernel can swap out pages to free
 up memory. If a program accesses a swapped out memory page, it will result in a page fault and the Kernel has to
diff --git a/linux/workstation/user_privileges.markdown b/linux/workstation/user_privileges.markdown
index e0d981f8..09f16767 100644
--- a/linux/workstation/user_privileges.markdown
+++ b/linux/workstation/user_privileges.markdown
@@ -1,9 +1,9 @@
-User priviliges on managed Linux workstations
+User privileges on managed Linux workstations
 =============================================
 
 Like file access is controlled by [permissions](https://compenv.phys.ethz.ch/linux/basics_1/30_file_permissions/),
 there are other actions on Linux such as `reboot`, which require even more elevated privileges.
-These are usually only available to the `root` user or using `sudo` (ISG personell only for security reasons).
+These are usually only available to the `root` user or using `sudo` (ISG personnel only for security reasons).
 
 
 Polkit
diff --git a/mail/mailman/index.markdown b/mail/mailman/index.markdown
index e42c9e55..7a852857 100644
--- a/mail/mailman/index.markdown
+++ b/mail/mailman/index.markdown
@@ -44,7 +44,7 @@ Some terms used on the [lists.phys.ethz.ch](https://lists.phys.ethz.ch) web page
 * Owners have full admin rights on a mailing list. They can change the settings, manage members and moderate new messages.
 * Moderators have restricted rights on a mailing list and can only moderate new messages.
 * Administrators are the people that are either owner or moderator of a mailing list.
-* Members are the people that have been suscribed to a mailing list and receive its messages.
+* Members are the people that have been subscribed to a mailing list and receive its messages.
 * Non-members are the people that require some special settings, without necessarily being a member of the mailing list. The typical example is to allow someone to send messages, without being moderated.
 
 ### Accept, Discard, Ban, Reject
diff --git a/mail/mailman/moderation.markdown b/mail/mailman/moderation.markdown
index 9aadce74..847cb645 100644
--- a/mail/mailman/moderation.markdown
+++ b/mail/mailman/moderation.markdown
@@ -28,7 +28,7 @@ Consider the example of a mailing list for a research group. You typically want
 
 [[!img /media/mail/mailman/moderation_2.png size="550x"]]
 
-### Defaut action for specific non-members
+### Default action for specific non-members
 
 Another common scenario is to have a mailing list, where someone who is not a member of that list, should still be able to post without being moderated. You then need to add a new `non-member` with `default processing` as moderation action, to automatically accept postings from this sender address.
 
diff --git a/windows/windows10/change_display_or_keyboard_language.markdown b/windows/windows10/change_display_or_keyboard_language.markdown
index 9b18c1d8..968db814 100644
--- a/windows/windows10/change_display_or_keyboard_language.markdown
+++ b/windows/windows10/change_display_or_keyboard_language.markdown
@@ -2,7 +2,7 @@ Change Display or Keyboard language in Windows 10
 =================================================
 
 The default user interface for our managed workstations is German with the Swiss German Keyboard layout.
-You can change the **display language**, this is the userinterface language in Windows to english.
+You can change the **display language**, this is the user interface language in Windows to English.
 There is also the possibility to change the **keyboard layout** to English-US or German-Switzerland depending on your personal preference. Please follow this steps to change the settings:
 
 ## 1. Change the display language
@@ -26,7 +26,7 @@ Now you should **logoff or restart** your computer for activate the new settings
 You can change your keyboard layout in the Systray menu in the right corner
 [[!img media/windows/windows10/change_language/2.1.png size="300x"]]
 
-When the keyboard layout is not persistent US-Layout, remove the swiss german layout under Language Preferences
+When the keyboard layout is not persistent US-Layout, remove the Swiss German layout under Language Preferences
 [[!img media/windows/windows10/change_language/2.2.png size="300x"]]
 
 ## 3. Change regional Format
diff --git a/windows/windows10/edit_lockscreen.markdown b/windows/windows10/edit_lockscreen.markdown
index ec42600a..d61aa305 100644
--- a/windows/windows10/edit_lockscreen.markdown
+++ b/windows/windows10/edit_lockscreen.markdown
@@ -21,7 +21,7 @@ At the bottom of this page, click on **Screen saver settings**
 
 To enable the Lockscreen. Enable the checkbox **"On resume, display logon screen"** and define the wait minutes.
 
-Recomment is **20 minutes**, because the display go to sleep at this time.
+Recommended is **20 minutes**, because the display go to sleep at this time.
 
 [[!img media/windows/windows10/edit_lockscreen4.png size="300x"]]
 
-- 
GitLab