From 1f35e683a2622c9973cf9b77ed2d8bd96e6e339c Mon Sep 17 00:00:00 2001
From: Luc <59910153+lschober-bw@users.noreply.github.com>
Date: Wed, 11 Nov 2020 17:38:12 -0800
Subject: [PATCH] Update vault-timeout.md (#271)

---
 _articles/account/vault-timeout.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_articles/account/vault-timeout.md b/_articles/account/vault-timeout.md
index adecd522..e0e2357f 100644
--- a/_articles/account/vault-timeout.md
+++ b/_articles/account/vault-timeout.md
@@ -27,7 +27,7 @@ There are **two options** available to configure what occurs when those time lim
 
 ## Lock
 
-Locking your vault is the default behavior. This will maintain vault data on the device and will only prompt for your master password to decrypt and re-allow access to your vault.
+Locking your vault is the default behavior. This will maintain vault data on the device and will only prompt for your master password to decrypt and re-allow access to your vault. Two-factor authentication (2FA) is **not** required when unlocking.
 
 This is the option most users prefer, as it is usually the fastest and does **not** require the Bitwarden client to be online or able to connect to a Bitwarden server.