From aff3801fe8d5dee92a26bc29ae6c8e692c269318 Mon Sep 17 00:00:00 2001
From: samwiseg0 <2241731+samwiseg0@users.noreply.github.com>
Date: Fri, 18 Dec 2020 23:17:13 -0500
Subject: [PATCH] Updated Installation (markdown)

---
 Installation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Installation.md b/Installation.md
index f21df66..a58ba1f 100644
--- a/Installation.md
+++ b/Installation.md
@@ -44,7 +44,7 @@ Please refer to the [docker for windows documentation](https://docs.docker.com/d
 ```
 docker run -d -e LOG_LEVEL=info -e TZ=Asia/Tokyo -p 5055:5055 -v "/your/path/here:/app/config" --restart unless-stopped sctx/overseerr
 ```
-_Detail: Docker on Windows works differently than it does on Linux; it uses a VM to run a stripped-down Linux and then runs docker within that. The volume mounts are exposed to the docker in this VM via SMB mounts. While this is fine for media, it is unacceptable for the /config directory because SMB does not support file locking. This will eventually corrupt your database which can lead to slow behavior and crashes. If you must run in docker on Windows, you should put the /config directory mount inside the VM and not on the Windows host. It's worth noting that this warning also extends to other containers which use SQLite databases._
+_Detail: Docker on Windows works differently than it does on Linux; it uses a VM to run a stripped-down Linux and then runs docker within that. The volume mounts are exposed to the docker in this VM via SMB mounts. While this is fine for media, it is unacceptable for the /app/config directory because SMB does not support file locking. This will eventually corrupt your database which can lead to slow behavior and crashes. If you must run in docker on Windows, you should put the /config directory mount inside the VM and not on the Windows host. It's worth noting that this warning also extends to other containers which use SQLite databases._
 
 
 ## ArchLinux (Third party)