diff --git a/docs/docs/auth/faq/privacy-disclosure/index.md b/docs/docs/auth/faq/privacy-disclosure/index.md
index 5b1a990836..7ed0bc05a8 100644
--- a/docs/docs/auth/faq/privacy-disclosure/index.md
+++ b/docs/docs/auth/faq/privacy-disclosure/index.md
@@ -18,29 +18,33 @@ AppStore](appstore-privacy-disclosure.png){width=620px}
 ## Data Linked to You
 
 > [!NOTE]
-> 
+>
 > Only if you choose to create an account to backup your codes are the following
 > details collected.
 
 ### Contact Info
+
 This is your email address, used for account creation and communication.
 
 ### User Content
+
 This are your 2FA secrets, end-to-end encrypted with a key that only you have
 access to.
 
 ### Identifiers
+
 This is your user ID generated by our server during sign up.
 
 ## Data Not Linked to You
 
 > [!NOTE]
-> 
+>
 > Only if you opt-in to **Crash reporting** are the following details collected.
 
 ### Diagnostics
-These are anonymized error reports and other diagnostics data that make it easier
-for us to detect and fix any issues.
+
+These are anonymized error reports and other diagnostics data that make it
+easier for us to detect and fix any issues.
 
 ---
 
@@ -48,5 +52,5 @@ for us to detect and fix any issues.
 
 Ente Auth collects no data by default.
 
-For more details, please refer to our [full privacy
-policy](https://ente.io/privacy).
+For more details, please refer to our
+[full privacy policy](https://ente.io/privacy).
diff --git a/docs/docs/photos/troubleshooting/thumbnails.md b/docs/docs/photos/troubleshooting/thumbnails.md
index 81c8ff8227..f26319c2e5 100644
--- a/docs/docs/photos/troubleshooting/thumbnails.md
+++ b/docs/docs/photos/troubleshooting/thumbnails.md
@@ -23,10 +23,12 @@ canvas.
 ## Desktop
 
 The only known case where thumbnails might be missing on desktop is when
-uploading **videos** during a Google Takeout or folder sync on **Intel macOS**
-machines. This is because the bundled ffmpeg that we use does not work with
-Rosetta. For images, we are able to fallback to other mechanisms for generating
-the thumbnails, but for videos because of their potentially huge size, the app
+uploading **videos** during a Google Takeout or watched folder sync on **Intel
+macOS** machines. This is because the bundled ffmpeg that we use does not work
+on Intel machines.
+
+For images, we are able to fallback to other mechanisms for generating the
+thumbnails, but for videos because of their potentially huge size, the app
 doesn't try the fallback to avoid running out of memory.
 
 In such cases, you will need to use the following workaround:
@@ -39,10 +41,11 @@ In such cases, you will need to use the following workaround:
 2.  Copy or symlink it to
     `/Applications/ente.app/Contents/Resources/app.asar.unpacked/node_modules/ffmpeg-static/ffmpeg`.
 
-Even without the workaround, thumbnail generation during video uploads via the
-normal folder selection or drag and drop will work fine (since in this case we
-have access to the video's data directly without reading it from a zip and can
-thus use the fallback).
+Alternatively, you can drag and drop the videos. Even without the above
+workaround, thumbnail generation during video uploads via the normal folder
+selection or drag and drop will work fine, since in those case we have access to
+the video's data directly without reading it from a zip and can thus use the
+fallback.
 
 ## Regenerating thumbnails
 
@@ -50,6 +53,5 @@ There is currently no functionality to regenerate thumbnails in the above cases.
 You will need to upload the affected files again.
 
 Ente skips over files that have already been uploaded, so you can drag and drop
-the original folder or zip again after removing the files without thumbnails
-(and fixing the issue on web or adding the workaround on Intel macOS), and it'll
-only upload the files that are necessary.
+the original folder or zip again after removing the files without thumbnails,
+and it'll only upload the files that are necessary.
diff --git a/docs/docs/self-hosting/guides/configuring-s3.md b/docs/docs/self-hosting/guides/configuring-s3.md
index 56e922f02d..3ab3828dae 100644
--- a/docs/docs/self-hosting/guides/configuring-s3.md
+++ b/docs/docs/self-hosting/guides/configuring-s3.md
@@ -45,8 +45,10 @@ By default, you only need to configure the endpoint for the first bucket.
 > instance uses these to perform replication.
 >
 > However, in a self hosted setup replication is off by default (you can turn it
-> on if you want). When replication is turned off, only the first bucket is
-> used, and you can remove the other two if you wish or just ignore them.
+> on if you want). When replication is turned off, only the first bucket (it
+> must be named `b2-eu-cen`) is used, and you can ignore the other two. Use the
+> `hot_bucket` option if you'd like to set one of the other predefined buckets
+> as the "first" bucket.
 
 The `endpoint` for the first bucket in the starter `credentials.yaml` is
 `localhost:3200`. The way this works then is that both museum (`2`) and minio