diff --git a/src/main/java/net/szum123321/textile_backup/core/Cleanup.java b/src/main/java/net/szum123321/textile_backup/core/Cleanup.java
index bb80c89..0894ce4 100644
--- a/src/main/java/net/szum123321/textile_backup/core/Cleanup.java
+++ b/src/main/java/net/szum123321/textile_backup/core/Cleanup.java
@@ -34,7 +34,7 @@ import java.util.Objects;
 import java.util.stream.Stream;
 
 /**
- * Set of utility used for removing old backups
+ * Utility used for removing old backups
  */
 public class Cleanup {
 	private final static TextileLogger log = new TextileLogger(TextileBackup.MOD_NAME);
diff --git a/src/main/java/net/szum123321/textile_backup/core/create/BackupScheduler.java b/src/main/java/net/szum123321/textile_backup/core/create/BackupScheduler.java
index 82d8bbe..fb54d37 100644
--- a/src/main/java/net/szum123321/textile_backup/core/create/BackupScheduler.java
+++ b/src/main/java/net/szum123321/textile_backup/core/create/BackupScheduler.java
@@ -31,7 +31,7 @@ import java.time.Instant;
  * The important thing to note: <br>
  * The decision of whether to do a backup or not is made at the time of scheduling, that is, whenever the <code>nextBackup</code>
  * flag is set. This means that even if doBackupsOnEmptyServer=false, the backup that was scheduled with players online will
- * still go thorough. <br>
+ * still go through. <br>
  * It might appear as though there has been made a backup with no players online despite the config. This is the expected behaviour
  * <br><br>
  * Furthermore, it uses system time
@@ -90,4 +90,4 @@ public class BackupScheduler {
             }
         }
     }
-}
\ No newline at end of file
+}