From bfadfdfc245ffda148ab6852a78a809309fc017a Mon Sep 17 00:00:00 2001 From: Sean Stavropoulos Date: Mon, 18 Nov 2024 21:09:56 -0800 Subject: [PATCH] Fix typo in FAQ --- faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/faq.md b/faq.md index eff1d00668a..2aa5f99386d 100644 --- a/faq.md +++ b/faq.md @@ -134,7 +134,7 @@ DuckDB can also run in [in-memory mode]({% link docs/connect/overview.md %}#in-m
The type of storage used to run DuckDB has a [significant performance impact]({% link docs/guides/performance/environment.md %}#disk). -In general, using SSDs (SATA or NVMe SSDs) leadst to superior performance compared to HDDs. +In general, using SSDs (SATA or NVMe SSDs) leads to superior performance compared to HDDs. The location of the storage varies greatly depending the workload. _For read-only workloads,_ the DuckDB database can be stored on local disks and remote endpoints such as [HTTPS]({% link docs/extensions/httpfs/https.md %}) and cloud object storage such as [AWS S3]({% link docs/extensions/httpfs/s3api.md %}) and similar providers. _For read-write workloads,_ storing the database on instance-attached storage yields the best performance.