diff --git a/docs/contributing/server/migrations.md b/docs/contributing/server/migrations.md
index 627ba08..cd9481b 100644
--- a/docs/contributing/server/migrations.md
+++ b/docs/contributing/server/migrations.md
@@ -17,7 +17,7 @@ To generate a database migration in fosscord-server:
     npm run generate:migration -- src/util/migrations/:dbms:/:migrationName:
     ```
     where `:dbms:` is the db you use, and `:migrationName:` is whatever you wish to call it.
-	The migration must be named a valid Javascript class name.
+    The migration must be named a valid Javascript class name.
 3. The generated file is what TypeORM will do if you were to run `npm run sync:db`.
    Obviously, this is not always what you want. Edit it to preserve as much of the original data as possible.
 
diff --git a/docs/setup/server/configuration/imagor.md b/docs/setup/server/configuration/imagor.md
index f8aa5e9..27b5371 100644
--- a/docs/setup/server/configuration/imagor.md
+++ b/docs/setup/server/configuration/imagor.md
@@ -14,7 +14,7 @@ privacy concerns, as an attacker may be able to learn users IP addresses.
 
 To setup Imagor for Fosscord, first grab the `security_requestSignature` config value from Fosscord's database,
 and create a `imagor.env` file somewhere safe, with the following content.
-**Make sure to edit the file with the correct information**. Your requestSignture should *not* start or end with `"`.
+**Make sure to edit the file with the correct information**. Your requestSignture should _not_ start or end with `"`.
 
 ```
 IMAGOR_SECRET=security_requestSignature value from your Fosscord config
diff --git a/docs/setup/server/maintenance/index.md b/docs/setup/server/maintenance/index.md
index 3f29726..4fc2b3c 100644
--- a/docs/setup/server/maintenance/index.md
+++ b/docs/setup/server/maintenance/index.md
@@ -2,4 +2,4 @@
 
 ## [When do I have to restart the server?](restart.md)
 
-## [Updating Fosscord-server](updating.md)
\ No newline at end of file
+## [Updating Fosscord-server](updating.md)
diff --git a/docs/setup/server/maintenance/restart.md b/docs/setup/server/maintenance/restart.md
index e9bdbd9..87c658e 100644
--- a/docs/setup/server/maintenance/restart.md
+++ b/docs/setup/server/maintenance/restart.md
@@ -2,17 +2,17 @@
 
 Fosscord-server must restart in the following cases:
 
-* The .env file or config (database or [CONFIG_PATH](/setup/server/configuration) has changed.
-* Files in the `client_test`, `preload-plugins` folders of inside `assets` have changed.
-* Files inside `src` have changed (*remember to `npm run build`*).
-* The `assets/schemas.json` file has changed.
-* The [RabbitMQ](/setup/server/configuration/rabbitmq) connection has been lost.
+-   The .env file or config (database or [CONFIG_PATH](/setup/server/configuration) has changed.
+-   Files in the `client_test`, `preload-plugins` folders of inside `assets` have changed.
+-   Files inside `src` have changed (_remember to `npm run build`_).
+-   The `assets/schemas.json` file has changed.
+-   The [RabbitMQ](/setup/server/configuration/rabbitmq) connection has been lost.
 
 For all other cases, you do not need to restart the server. For example:
 
-* Running `npm run generate:client`
-* Running `npm run generate:changelog`
-* Editing any table in the database other than `config`. For example, to edit a `users` [`rights`](/setup/server/configuration/rabbitmq)
-* Database connection was lost (this should auto reconnect)
+-   Running `npm run generate:client`
+-   Running `npm run generate:changelog`
+-   Editing any table in the database other than `config`. For example, to edit a `users` [`rights`](/setup/server/configuration/rabbitmq)
+-   Database connection was lost (this should auto reconnect)
 
-This is not an exhaustive list. If a change you made is not applied, the first thing you should try is restarting.
\ No newline at end of file
+This is not an exhaustive list. If a change you made is not applied, the first thing you should try is restarting.