diff --git a/docsite/docs/core-setup.md b/docsite/docs/core-setup.md
index d6aa7a611..dd549aff3 100644
--- a/docsite/docs/core-setup.md
+++ b/docsite/docs/core-setup.md
@@ -22,6 +22,14 @@ docker run --name monitor-mongo \
 You should replace the username and password with your own.
 See [the image docs](https://hub.docker.com/_/mongo) for more details.
 
+:::note
+The disk space requirements of Monitor are dominated by the storage of system stats.
+This depends on the number of connected servers (more system stats being produces / stored), stats collection frequency, and your stats pruning configuration.
+If you need to save on space, you can configure these fields in your core config:
+	- Stats poll frequency can be reduced using, for example, `monitoring_interval = "15-sec"`
+	- Pruning can be tuned more aggresively using, for example, `keep_stats_for_days = 7`.
+:::
+
 ## 1. Create the configuration file
 
 Create a configuration file on the system, for example at `~/.config/monitor/core.config.toml`, and copy the [example config](https://github.com/mbecker20/monitor/blob/main/config_example/core.config.example.toml). Fill in all the necessary information before continuing.
diff --git a/docsite/docs/sync-resources.md b/docsite/docs/sync-resources.md
index 2a7f47758..49e6051fe 100644
--- a/docsite/docs/sync-resources.md
+++ b/docsite/docs/sync-resources.md
@@ -5,7 +5,7 @@ and apply updates based on the diffs. Simply use a Github repo to manage the fil
 and the core backend will poll for any updates (you can also manually trigger an update poll / execution in the UI).
 
 File detection is additive and recursive, so you can spread out your resource declarations across any number of files
-and use any nesting of folders (they should all be under one root folder). Additionally, you can create multiple `ResourceSyncs`
+and use any nesting of folders to organize resources inside a root folder. Additionally, you can create multiple `ResourceSyncs`
 and each sync will be handled independently. This allows different syncs to manage resources on a "per-project" basis.
 
 The UI will display the computed sync actions and only execute them upon manual confirmation.