3 files changed, 15 insertions, 11 deletions
diff --git a/docs/API/admin_api.md b/docs/API/admin_api.md
index 07aa7ec3f..e445583cb 100644
--- a/docs/API/admin_api.md
+++ b/docs/API/admin_api.md
@@ -665,11 +665,9 @@ Note: Available `:permission_group` is currently moderator and admin. 404 is ret
     - 404 Not Found `"Not found"`
   - On success: 200 OK `{}`
 
-## `GET /api/pleroma/admin/config/migrate_from_db`
+## `GET /api/pleroma/admin/restart`
 
-### Run mix task pleroma.config migrate_from_db
-
-Copies all settings from database to `config/{env}.exported_from_db.secret.exs` with deletion from the table. Where `{env}` is the environment in which `pleroma` is running.
+### Restarts pleroma application
 
 - Params: none
 - Response:
diff --git a/docs/admin/config.md b/docs/admin/config.md
index 35e43b6a9..b39a73961 100644
--- a/docs/admin/config.md
+++ b/docs/admin/config.md
@@ -6,11 +6,7 @@ config :pleroma, configurable_from_database: true
 ```
 
 ## How it works
-Settings are stored in database and are applied in `runtime` after each change. Most of the settings take effect immediately, except some, which need instance reboot. These settings are needed in `compile time`, that's why settings are duplicated to the file.
-
-File with duplicated settings is located in `config/{env}.exported_from_db.exs` if pleroma is runned from source. For prod env it will be `config/prod.exported_from_db.exs`.
-
-For releases: `/etc/pleroma/prod.exported_from_db.secret.exs` or `PLEROMA_CONFIG_PATH/prod.exported_from_db.exs`.
+Settings are stored in database and are applied in `runtime` after each change. Most of the settings take effect immediately, except some, which need instance reboot.
 
 ## How to set it up
 You need to migrate your existing settings to the database. This task will migrate only added by user settings.
@@ -25,7 +21,7 @@ You can do this with mix task (all config files will remain untouched):
 mix pleroma.config migrate_to_db
 ```
 
-Now you can change settings in admin interface. After each save, settings from database are duplicated to the `config/{env}.exported_from_db.exs` file.
+Now you can change settings in admin interface. If `reboot time` settings were changed, pleroma must be rebooted.
 
 <span style="color:red">**ATTENTION**</span>
 
@@ -35,10 +31,19 @@ Now you can change settings in admin interface. After each save, settings from d
 - all settings inside these keys:
   - `:hackney_pools`
   - `:chat`
+  - `Oban`
+  - `:rate_limit`
+  - `:markup`
+  - `:streamer`
 - partially settings inside these keys:
   - `:seconds_valid` in `Pleroma.Captcha`
   - `:proxy_remote` in `Pleroma.Upload`
   - `:upload_limit` in `:instance`
+  - `:digest` in `:email_notifications`
+  - `:clean_expired_tokens` in `:oauth2`
+  - `:enabled` in `Pleroma.ActivityExpiration`
+  - `:enabled` in `Pleroma.ScheduledActivity`
+  - `:enabled` in `:gopher`
 
 ## How to dump settings from database to file
 
@@ -59,7 +64,7 @@ mix pleroma.config migrate_from_db [-d]
 ```sql
 TRUNCATE TABLE config;
 ```
-2. Delete `config/{env}.exported_from_db.exs`.
+2. If migrate_from_db task was runned, backup and delete `config/{env}.exported_from_db.exs`.
 
 For `prod` env:
 ```bash
diff --git a/docs/configuration/cheatsheet.md b/docs/configuration/cheatsheet.md
index a81bfa29d..ed9049a8d 100644
--- a/docs/configuration/cheatsheet.md
+++ b/docs/configuration/cheatsheet.md
@@ -69,6 +69,7 @@ You shouldn't edit the base config directly to avoid breakages and merge conflic
 * `account_field_name_length`: An account field name maximum length (default: `512`).
 * `account_field_value_length`: An account field value maximum length (default: `2048`).
 * `external_user_synchronization`: Enabling following/followers counters synchronization for external users.
+* `cleanup_attachments`: Remove attachments along with statuses. Does not affect duplicate files and attachments without status. Enabling this will increase load to database when deleting statuses on larger instances.
 
 ## Federation
 ### MRF policies