diff --git a/apps/mobile-app/android/fdroid/README.md b/apps/mobile-app/android/fdroid/README.md
index c3a0a1948..3bfb7a772 100644
--- a/apps/mobile-app/android/fdroid/README.md
+++ b/apps/mobile-app/android/fdroid/README.md
@@ -42,7 +42,7 @@ BUILD SUCCESSFUL in 30m 25s
 2025-11-03 16:40:56,157 INFO: Successfully built version 0.99.0-test1 of net.aliasvault.app from 97d8d4d15df88cd759b62489368e857291a27078
 ```
 
-This is the important part to know whether the build was succesful:
+This is the important part to know whether the build was successful:
 > BUILD SUCCESSFUL in 30m 25s
 
 Other warnings can be ignored as they are most likely about versions not matching, but that is to be expected as we have hardcoded the version to 0.1.0 while the actual version extracted from the Android build.gradle file will be different.
@@ -63,4 +63,4 @@ to include a specific commit:
     commit: 4010631d7380fc4ca5538a43afd21527287fd913
 ```
 
-Then run the above build again, which will now checkout this specific commit and try to build it.
\ No newline at end of file
+Then run the above build again, which will now checkout this specific commit and try to build it.
diff --git a/docs/installation/script/index.md b/docs/installation/script/index.md
index b32fa0d4c..e93c46adb 100644
--- a/docs/installation/script/index.md
+++ b/docs/installation/script/index.md
@@ -212,7 +212,7 @@ Disabling public registration means the ability to create new accounts in the Al
 
 ## 5. Configure IP logging
 
-By default, AliasVault is configured to log (anonymized) IP addressses for all authentication attempts. This is used to monitor and combat potential abuse. However for privacy reasons the last octet of the IP address is anonymized, e.g. the IP address `127.0.0.1` is logged as `127.0.0.xxx`. This is to prevent an IP address directly being linked to an individual person or household.
+By default, AliasVault is configured to log (anonymized) IP addresses for all authentication attempts. This is used to monitor and combat potential abuse. However for privacy reasons the last octet of the IP address is anonymized, e.g. the IP address `127.0.0.1` is logged as `127.0.0.xxx`. This is to prevent an IP address directly being linked to an individual person or household.
 
 If you want to entirely disable IP logging, you can do so by running the install script with the `configure-ip-logging` option and then choosing option 2.
 
diff --git a/docs/misc/dev/release/index.md b/docs/misc/dev/release/index.md
index 8d2cac64f..0962a7d69 100644
--- a/docs/misc/dev/release/index.md
+++ b/docs/misc/dev/release/index.md
@@ -18,7 +18,7 @@ Follow the steps in the checklist below to prepare a new release.
 # Release preparation checklist
 
 ## Bump versions
-All clients and server apps contain a version definition that needs to be updated with every release. This version is used for communication between components to ensure they are compatible with eachother. Versions are also used for official publication on the app stores.
+All clients and server apps contain a version definition that needs to be updated with every release. This version is used for communication between components to ensure they are compatible with each other. Versions are also used for official publication on the app stores.
 
 For bumping the version for all projects in one go, you can use the interactive script located in:
 ```bash
@@ -37,7 +37,7 @@ When a new version of the mobile apps and/or browser extensions is released, wri
     > Filename should equal the semver of the release (e.g. `0.20.0`).
 
 ## Update documentation
-- [ ] Update /docs instructions for any relevant changes to functionality or self-host installaton process
+- [ ] Update /docs instructions for any relevant changes to functionality or self-host installation process
 - [ ] Update README screenshots if applicable
 - [ ] Update README current/upcoming features
 
@@ -124,4 +124,4 @@ The AliasVault Android app build is configured by the following file which is pa
 If any changes were made to the Android app build process or if any new third party (expo) packages have been installed, make sure it still
 works with the F-Droid build process. This can be tested either locally via `fdroid build`, or it can be done by creating a new test commit in
 a forked `fdroiddata` repo on GitLab and making the `net.aliasvault.app.yml` point to the latest main branch. This way you can test whether
-the build itself works properly with the latest version before actually publishing a new release.
\ No newline at end of file
+the build itself works properly with the latest version before actually publishing a new release.
diff --git a/install.sh b/install.sh
index e2b375f1c..147874074 100755
--- a/install.sh
+++ b/install.sh
@@ -2319,14 +2319,14 @@ configure_letsencrypt() {
     # Check if hostname is localhost
     if [ "$CURRENT_HOSTNAME" = "localhost" ]; then
         printf "${RED}Error: Let's Encrypt certificates cannot be issued for 'localhost'.${NC}\n"
-        printf "${YELLOW}Please configure a valid publically resolvable domain name (e.g. mydomain.com) before setting up Let's Encrypt.${NC}\n"
+        printf "${YELLOW}Please configure a valid publicly resolvable domain name (e.g. mydomain.com) before setting up Let's Encrypt.${NC}\n"
         exit 1
     fi
 
     # Check if hostname is a valid domain
     if ! [[ "$CURRENT_HOSTNAME" =~ \.[a-zA-Z]{2,}$ ]]; then
         printf "${RED}Error: Invalid hostname '${CURRENT_HOSTNAME}'.${NC}\n"
-        printf "${YELLOW}Please configure a valid publically resolvable domain name (e.g. mydomain.com) before setting up Let's Encrypt.${NC}\n"
+        printf "${YELLOW}Please configure a valid publicly resolvable domain name (e.g. mydomain.com) before setting up Let's Encrypt.${NC}\n"
         exit 1
     fi