diff --git a/README.md b/README.md
index 28f5ee8..b5d4483 100644
--- a/README.md
+++ b/README.md
@@ -86,7 +86,7 @@ be compatible with Folia. However, there are plans to add API that
 would allow Folia plugins to be compatible with Paper.
 
 For example, the Bukkit Scheduler. The Bukkit Scheduler inherently
-relies on a single main thread. Folia's RegionisedScheduler and Folia's
+relies on a single main thread. Folia's RegionScheduler and Folia's
 EntityScheduler allow scheduling of tasks to the "next tick" of whatever
 region "owns" either a location or an entity. These could be implemented
 on regular Paper, except they schedule to the main thread - in both cases,
@@ -121,11 +121,11 @@ prevent and find these bugs is to make bad accesses fail _hard_ at the
 source of the bad access.
 
 This means that Folia compatible plugins need to take advantage of 
-API like the RegionisedScheduler and the EntityScheduler to ensure 
+API like the RegionScheduler and the EntityScheduler to ensure 
 their code is running on the correct thread context.
 
 In general, it is safe to assume that a region owns chunk data
-in an approximate 8 chunks from the source of an event (i.e player
+in an approximate 8 chunks from the source of an event (i.e. player
 breaks block, can probably access 8 chunks around that block). But,
 this is not guaranteed - plugins should take advantage of upcoming
 thread-check API to ensure correct behavior.
@@ -137,7 +137,7 @@ specifically entity/chunk/poi data, and is entirely unrelated
 to **ANY** plugin data.
 
 Normal multithreading rules apply to data that plugins store/access
-their own data or another plugin's - events/commands/etc are called 
+their own data or another plugin's - events/commands/etc. are called 
 in _parallel_ because regions are ticking in _parallel_ (we CANNOT 
 call them in a synchronous fashion, as this opens up deadlock issues 
 and would handicap performance). There are no easy ways out of this,