diff --git a/content/docs/architecture/index.md b/content/docs/architecture/index.md
index c246695..7bfa300 100644
--- a/content/docs/architecture/index.md
+++ b/content/docs/architecture/index.md
@@ -23,7 +23,7 @@ links: https://github.com/TeamPiped/Piped\, https://github.com/TeamPiped/Piped-B
 
 -   Uses Java 11
 -   Uses the native HTTP client introduced in Java 9
--   Uses netty-reactor to acheive maximum performance and a low footprint.
+-   Uses netty-reactor to achieve maximum performance and a low footprint.
 -   Supports OpenJ9
 -   Each running instance should configure their own proxy, thus allowing multi-gigabit content delivery.
 -   Uses ~70-130 MB of ram. (on OpenJ9)
diff --git a/content/docs/why/index.md b/content/docs/why/index.md
index 4220939..e0dd236 100644
--- a/content/docs/why/index.md
+++ b/content/docs/why/index.md
@@ -36,7 +36,7 @@ I created Piped to fix issues in NewPipe and Invidious which are architectural i
 ### NewPipe
 
 -   Your IP is exposed to YouTube.
--   Feeds are slow to load/update in comparion to YouTube.
+-   Feeds are slow to load/update in comparison to YouTube.
 
 ### Invidious
 
@@ -46,7 +46,7 @@ I created Piped to fix issues in NewPipe and Invidious which are architectural i
 -   Caching is done at a backend level.
 -   Invidious was a learning project.
 -   Invidious crashes all the time.
--   Various hacks are required to keep an instance running at a reasonable stablity.
+-   Various hacks are required to keep an instance running at a reasonable stability.
 
 However, there are some drawbacks of Piped: