From d9d672322bbb1326bc73fa507d485f0285c5045d Mon Sep 17 00:00:00 2001
From: et304383 <2693414+et304383@users.noreply.github.com>
Date: Mon, 12 Sep 2022 21:16:30 -0300
Subject: [PATCH] Update locking.mdx

---
 website/docs/language/state/locking.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/language/state/locking.mdx b/website/docs/language/state/locking.mdx
index 970c14f2fe..0c6a69db7d 100644
--- a/website/docs/language/state/locking.mdx
+++ b/website/docs/language/state/locking.mdx
@@ -14,7 +14,7 @@ others from acquiring the lock and potentially corrupting your state.
 State locking happens automatically on all operations that could write
 state. You won't see any message that it is happening. If state locking fails,
 Terraform will not continue. You can disable state locking for most commands
-with the `-lock` flag but it is not recommended.
+with the `-lock=false` flag but it is not recommended.
 
 If acquiring the lock is taking longer than expected, Terraform will output
 a status message. If Terraform doesn't output a message, state locking is