diff --git a/CHANGELOG.md b/CHANGELOG.md
index 9ef44af9e..b8cb57f2b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2874,8 +2874,7 @@ Details
    an exclusive lock through a filesystem snapshot. Restic was unable to backup those files
    before. This update enables backing up these files.
 
-   This needs to be enabled explicitly using the --use-fs-snapshot option of the backup
-   command.
+   This needs to be enabled explicitly using the --use-fs-snapshot option of the backup command.
 
    https://github.com/restic/restic/issues/340
    https://github.com/restic/restic/pull/2274
@@ -4537,8 +4536,8 @@ Details
  * Bugfix #1595: Backup: Remove bandwidth display
 
    This commit removes the bandwidth displayed during backup process. It is misleading and
-   seldom correct, because it's neither the "read bandwidth" (only for the very first backup)
-   nor the "upload bandwidth". Many users are confused about (and rightly so), c.f. #1581, #1033,
+   seldom correct, because it's neither the "read bandwidth" (only for the very first backup) nor
+   the "upload bandwidth". Many users are confused about (and rightly so), c.f. #1581, #1033,
    #1591
 
    We'll eventually replace this display with something more relevant when the new archiver code
diff --git a/changelog/0.10.0_2020-09-19/pull-2195 b/changelog/0.10.0_2020-09-19/pull-2195
index 7898568fa..a139aa4e1 100644
--- a/changelog/0.10.0_2020-09-19/pull-2195
+++ b/changelog/0.10.0_2020-09-19/pull-2195
@@ -10,7 +10,7 @@ https://github.com/restic/restic/issues/2244
 
 NOTE: This new implementation does not guarantee order in which blobs
 are written to the target files and, for example, the last blob of a
-file can be written to the file before any of the preceding file blobs.
+file can be written to the file before any of the preceeding file blobs.
 It is therefore possible to have gaps in the data written to the target
 files if restore fails or interrupted by the user.
 
diff --git a/changelog/0.11.0_2020-11-05/issue-1756 b/changelog/0.11.0_2020-11-05/issue-1756
index f735cf1f9..c182c1a6c 100644
--- a/changelog/0.11.0_2020-11-05/issue-1756
+++ b/changelog/0.11.0_2020-11-05/issue-1756
@@ -1,6 +1,6 @@
 Bugfix: Mark repository files as read-only when using the local backend
 
-Files stored in a local repository were marked as writeable on the
+Files stored in a local repository were marked as writable on the
 filesystem for non-Windows systems, which did not prevent accidental file
 modifications outside of restic. In addition, the local backend did not work
 with certain filesystems and network mounts which do not permit modifications
diff --git a/changelog/0.11.0_2020-11-05/issue-340 b/changelog/0.11.0_2020-11-05/issue-340
index 84c67f145..d688ee0db 100644
--- a/changelog/0.11.0_2020-11-05/issue-340
+++ b/changelog/0.11.0_2020-11-05/issue-340
@@ -5,7 +5,7 @@ another process using an exclusive lock through a filesystem snapshot. Restic
 was unable to backup those files before. This update enables backing up these
 files.
 
-This needs to be enabled explicitely using the --use-fs-snapshot option of the
+This needs to be enabled explicitly using the --use-fs-snapshot option of the
 backup command.
 
 https://github.com/restic/restic/issues/340
diff --git a/changelog/0.8.2_2018-02-17/pull-1595 b/changelog/0.8.2_2018-02-17/pull-1595
index 81e0a8748..3dbea73ce 100644
--- a/changelog/0.8.2_2018-02-17/pull-1595
+++ b/changelog/0.8.2_2018-02-17/pull-1595
@@ -1,7 +1,7 @@
 Bugfix: backup: Remove bandwidth display
 
 This commit removes the bandwidth displayed during backup process. It is
-misleading and seldomly correct, because it's neither the "read
+misleading and seldom correct, because it's neither the "read
 bandwidth" (only for the very first backup) nor the "upload bandwidth".
 Many users are confused about (and rightly so), c.f. #1581, #1033, #1591
 
diff --git a/doc/faq.rst b/doc/faq.rst
index 8e56b5d9e..e8ef2de5e 100644
--- a/doc/faq.rst
+++ b/doc/faq.rst
@@ -74,7 +74,7 @@ $ restic backup --exclude "~/documents" ~
 This command will result in a complete backup of the current logged in user's home directory and it won't exclude the folder ``~/documents/`` - which is not what the user wanted to achieve.
 The problem is how the path to ``~/documents`` is passed to restic.
 
-In order to spot an issue like this, you can make use of the following ruby command preceding your restic command.
+In order to spot an issue like this, you can make use of the following ruby command preceeding your restic command.
 
 ::
 
diff --git a/internal/restorer/doc.go b/internal/restorer/doc.go
index e230f23f0..8d68d7161 100644
--- a/internal/restorer/doc.go
+++ b/internal/restorer/doc.go
@@ -18,7 +18,7 @@
 //
 // Implementation does not guarantee order in which blobs are written to the
 // target files and, for example, the last blob of a file can be written to the
-// file before any of the preceding file blobs. It is therefore possible to
+// file before any of the preceeding file blobs. It is therefore possible to
 // have gaps in the data written to the target files if restore fails or
 // interrupted by the user.
 package restorer