Reword NAS FAQ entry

faq.md

@@ -129,15 +129,18 @@ DuckDB can also run in [in-memory mode]({% link docs/connect/overview.md %}#in-m
 
 <div class="qa-wrap" markdown="1">
 
-### What disk should I run DuckDB on?
+### What type of storage should I run DuckDB on (e.g., local disks, network-attached storage)?
 
 <div class="answer" markdown="1">
 
-The type of storage used by DuckDB has a [big performance impact]({% link docs/guides/performance/environment.md %}#disk) on read-write workloads.
-To achieve optimal performance on these workloads, we recommend run DuckDB on SSD or NVMe disks.
-In the cloud, instance-attached storage (with local SSD or NVMe disks) yields better performance but network-attached cloud disks such as [AWS EBS](https://aws.amazon.com/ebs/) also work.
-Based on our experience, we **advise against running DuckDB workloads on on-premises network-attached storage (NAS).**
-Such setups are often slow and result in spurious failures that are difficult to troubleshoot.
+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.
+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.
+Network-attached cloud storage such as [AWS EBS](https://aws.amazon.com/ebs/) also works and its performance can be fine-tuned with the guaranteed IOPS settings.
+Based on our experience, we **advise against running read-write DuckDB workloads on on-premises [network-attached storage (NAS)](https://en.wikipedia.org/wiki/Network-attached_storage).**
+These setups are often slow and result in spurious failures that are difficult to troubleshoot.
 
 </div>