chore(website): fix some typos (#28795)

* lightweight

* publicly

* individual

* will

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 overwritten 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 individual 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:
 

docs/fundamentals/mining.md

@@ -121,7 +121,7 @@ Like with GPU mining, an etherbase account must be set. This defaults to the pri
 geth --miner.etherbase '0xC95767AC46EA2A9162F0734651d6cF17e5BfcF10' --mine
 ```
 
-If there is no account available an account wil be created and automatically configured to be the coinbase. The Javascript console can be used to reset the etherbase account at runtime:
+If there is no account available an account will be created and automatically configured to be the coinbase. The Javascript console can be used to reset the etherbase account at runtime:
 
 ```sh
 miner.setEtherbase(eth.accounts[2])

docs/fundamentals/security.md

@@ -26,7 +26,7 @@ Exposing API endpoints towards "the internet", or any untrusted/hostile network,
 - Increase the risk of not keeping up with chain progression, due to resource starvation (IO or CPU),
 - Increase the risk of attempts to steal funds via spurious signing-requests (depending on what namespaces are exposed).
 
-We do not recommend exposing API endpoints publically, and any user who wishes to do so should carefully consider setting up  
+We do not recommend exposing API endpoints publicly, and any user who wishes to do so should carefully consider setting up  
 proxies, WAFs, application level filtering, rate limiting, logging, tls terminator and monitoring to improve resilience. 
 
 

docs/monitoring/understanding-dashboards.md

@@ -39,7 +39,7 @@ Disk tracks the rate that data is written to (plotted as `write`) or read from (
 
 #### Goroutines
 
-Tracks the total number of active goroutines being used by Geth. Goroutines are lighweight threads managed by the Go runtime, they allow processes to
+Tracks the total number of active goroutines being used by Geth. Goroutines are lightweight threads managed by the Go runtime, they allow processes to
 execute concurrently.
 
 ![The goroutine panel](/images/docs/grafana/goroutines.png)