From 3c485eb3537eae26ae15162a67747671513ff9e9 Mon Sep 17 00:00:00 2001
From: Paul Leydier <75126792+paul-leydier@users.noreply.github.com>
Date: Tue, 18 Apr 2023 02:44:35 -0400
Subject: [PATCH] [website]: fix typo (#27108)

fix databases "overwritten" typo
---
 docs/fundamentals/databases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/fundamentals/databases.md b/docs/fundamentals/databases.md
index 5146252b1e..7fe5ec144e 100644
--- a/docs/fundamentals/databases.md
+++ b/docs/fundamentals/databases.md
@@ -8,7 +8,7 @@ Since v1.9.0, Geth has divided its database into two parts. Recent blocks and st
 # Recent blocks
 
 Geth stores recent blocks in a LevelDB database. This is a persistent key-value store that can be queried very quickly. The LevelDB database is supposed to be run on top of a fast SSD hard disk so that the disk IO is not bottlenecked by the underlying hardware. In addition to basic storage, the LevelDB database supports batch writes and iterations over the keyspace in binary-alphabetical order.
-The database is periodically compacted to reduce the operational cost of accessing indivdual items. This is achieved by flattening the underlying data store for a given range of keys. Any deleted or overwritte items in that key range are removed and the surviving data is reorganized for efficiency.
+The database is periodically compacted to reduce the operational cost of accessing indivdual items. This is achieved by flattening the underlying data store for a given range of keys. Any deleted or overwritten items in that key range are removed and the surviving data is reorganized for efficiency.
 
 Geth also tracks several performance metrics for the LevelDB database that can be monitored via the metrics subsystem. These are: