diff --git a/content/docs/overview.mdx b/content/docs/overview.mdx
index 9bc4229..bb51ee3 100644
--- a/content/docs/overview.mdx
+++ b/content/docs/overview.mdx
@@ -52,7 +52,7 @@ You can easily work in a single branch at a time, but GitButler can handle sever
 
 Each virtual branch is kept in a vertical lane, similar to a kanban board, and every file and difference is similar to a card that you can drag between the lanes until they are committed there.
 
-Each time you commit on a virtual branch, GitButler calculates what that branch would have looked like if the changes you dragged onto it were the only things in your working directory and commits a file tree that reresents that work. If you push that commit and inspect it on GitHub (or whatever upstream service you use to collaborate), it should look like that was the only change you made, even though you could potentially still have multiple branches applied in your working directory.
+Each time you commit on a virtual branch, GitButler calculates what that branch would have looked like if the changes you dragged onto it were the only things in your working directory and commits a file tree that represents that work. If you push that commit and inspect it on GitHub (or whatever upstream service you use to collaborate), it should look like that was the only change you made, even though you could potentially still have multiple branches applied in your working directory.
 
 ## Applying and Unapplying Branches